SCS-0123-v2: Clarify mandatory service types - #1093
Merged
Merged
Conversation
mbuechse
reviewed
Feb 17, 2026
toothstone
force-pushed
the
1004-mandatory-service-types
branch
from
February 19, 2026 16:49
d2d27fa to
c25b82b
Compare
This was referenced Mar 4, 2026
depressiveRobot
added
IaaS
toothstone
force-pushed
the
1004-mandatory-service-types
branch
4 times, most recently
from
June 2, 2026 13:34
acfe202 to
004b60a
Compare
toothstone
marked this pull request as ready for review
June 2, 2026 13:45
Contributor
|
This looks good. I think we can merge this once SIG Std/Cert is on board! |
Fixes #1004. ToDo: Move to v2. Signed-off-by: Friedrich Zahn <friedrich.zahn@alasca.cloud>
Signed-off-by: Friedrich Zahn <friedrich.zahn@alasca.cloud>
Signed-off-by: Friedrich Zahn <friedrich.zahn@alasca.cloud>
toothstone
force-pushed
the
1004-mandatory-service-types
branch
from
June 3, 2026 07:29
c41816e to
ce5a6fc
Compare
Contributor
Author
Good to hear. I've updated the s3 service type to "object-store-s3" after re-reading #1004, and updated the top-most comment here to make it easier for the SIG participants to understand what is happening. |
toothstone
force-pushed
the
1004-mandatory-service-types
branch
from
June 3, 2026 08:21
ce5a6fc to
4af7a97
Compare
Contributor
We can make it more succinct (which I support very much) in a separate PR. It's a draft after all. |
mbuechse
approved these changes
Jun 4, 2026
mbuechse
left a comment
mbuechse
left a comment
Contributor
There was a problem hiding this comment.
Let's merge this draft. And then let's make the (old parts of the) text way more succinct.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This updates SCS-0123 to align more closely with the OpenStack Service Type Authority, and unambiguously enforces s3 services to be advertised to users via the service catalog.
I don't have a strong opinion on the specific non-canonical service type to use for that, so far "object-store-s3" had the most supporters. Other options are "s3" or, to be more in line with the service type authority guidance, "scs:s3" (namespaced).
I tried to keep the diff vs v1 to a minimum, so I copied most of the (imho somewhat redundant) prose.
I've dropped the s3 credentials testing, since I couldn't find any language in the standards that mandates the tested behavior.
Fixes #1004.