Introduce new oldgeneric os_purpose. Stabilize 0102-v2.#1172
Conversation
As discussed on SIG Std/Cert on 2026-05-07. This PR does three things: - Introduce a new os_purpose oldgeneric. As only the generic images have the uniqueness requirements, we don't need a catch-all "old" nor do we need oldXXXX at this point. - By consequence, change the standard to v2.1. - Stabilize it. Signed-off-by: Kurt Garloff <kurt@garloff.de>
garloff
added
enhancement
|
Obviously, every single aspect can be debated. If we need a significant amount of discussion, it will probably be better to split this into several PRs. Let me know ... |
|
Not sure we need to bump minor version as long as the standard is in Draft. |
depressiveRobot
left a comment
depressiveRobot
left a comment
There was a problem hiding this comment.
According to SCS-0001 Draft phase I would say a new version number is not necessary.
Co-authored-by: Marvin Frommhold <depressiveRobot@users.noreply.github.com> Signed-off-by: Kurt Garloff <kurt@garloff.de>
Co-authored-by: Marvin Frommhold <depressiveRobot@users.noreply.github.com> Signed-off-by: Marvin Frommhold <depressiveRobot@users.noreply.github.com>
depressiveRobot
left a comment
depressiveRobot
left a comment
There was a problem hiding this comment.
Still some open issues for me:
- field
stabilized_atmust be added - Are adjustments to the conformance tests needed?
- Do we also want to deprecate v1 with this PR?
| title: SCS Image Metadata | ||
| type: Standard | ||
| status: Draft | ||
| status: Stable |
There was a problem hiding this comment.
| status: Stable | |
| status: Stable | |
| stabilized_at: 2026-06-01 |
When we stabilize, stabilized_at must be added.
|
@depressiveRobot the conformance tests don't need further adjustments (besides those included here) However, I'm pretty sure we should work on the openstack-image-manager so that the purpose field can automatically changed to |
3 participants
As discussed on SIG Std/Cert on 2026-05-07.
This PR does three things: