Skip to content

SCS-0123-v2: Clarify mandatory service types#1093

Draft
toothstone wants to merge 5 commits intomainfrom
1004-mandatory-service-types
Draft

SCS-0123-v2: Clarify mandatory service types#1093
toothstone wants to merge 5 commits intomainfrom
1004-mandatory-service-types

Conversation

@toothstone
Copy link
Contributor

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've dropped the s3 credentials testing, since I couldn't find any language in the standards that mandates the tested behavior.

Fixes #1004.

- `scs-0123-service-X` (with varying `X`) ensures that a service of type X can be found in the service catalog,
- `scs-0123-storage-apis` ensures that a service of one of the following types can be found: "volume", "volumev3", "block-storage",
- `scs-0123-swift-s3` ensures that S3 can be used to access object storage using EC2 credentials from the identity API.
- `scs-0123-service-<service type>` ensures that a service with the given type can be found in the service catalog
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you must change the variable, please use a shorter one. I think <type> would be sufficient.
Also, the testcase scs-0123-swift-s3 should still be mentioned, because it is still in use -- the Supplement applies to both versions of the standard.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll create a new supplement version along with the new standard version later. I think it's worth it if we indeed drop the s3 credentials test.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's actually not how this works. The supplement is supposed to cover all versions, except if the change is really massive. But that's not the case here. You can just add a parenthetical "only for v1" behind the one testcase.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file needs to be saved under a different name: Standards/scs-0123-v2-mandatory-and-supported-iaas-services.md (importantly, with v2). Feel free to shorten the slug, though!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry I had the notice in the commit message, but it didn't make it to the PR description - I did not create a new file for now to keep the diff easier to read.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Understood. Not the worst move, to be honest :)

- scs-0123-swift-s3
- id: scs-0123-v2
name: Mandatory and Supported IaaS Services
url: https://docs.scs.community/standards/scs-0123-v2-mandatory-and-supported-IaaS-services
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you shorten the slug (as I invited you to do), then this needs to be adjusted.

Signed-off-by: toothstone <f.zahn@mailbox.org>
@toothstone toothstone force-pushed the 1004-mandatory-service-types branch from d2d27fa to c25b82b Compare February 19, 2026 16:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] SCS-IaaS mandatory "s3" service type is ambiguous, untested and not aligned with the OS Service Type Authority

2 participants