WIP: try to define what an SCS release is#1157
Conversation
* this rework of the existing Release Policies Draft tries to address
the question of what an SCS Release is and why anybody should care
* the goal here is to use the SCS Release to communicate a certain level
of quality about individual parts or full software stacks when trying
to build an SCS certifiable cloud environment
* this rework should also reduce the amount of work required on the SCS
community side when creating an release by:
* moving away from re-releasing software or waiting for
individual software releases to happen
* reusing the work already done by the SCS certification process
as a quality control for viable software stacks to build SCS
compatible clouds
* reducing the release cycles from every 6 months to annually,
to also align with the validity of the certificates
* this rework additionally includes the wording "modular software stack"
to build a basis for marketing communications around this topic and
clearly answer the question what is included, what is not and why
AI-assisted: Claude Code
Signed-off-by: Jan Klare <klare@osism.tech>
|
@SovereignCloudStack/project-board based on the discussions we had, here some write-up of my current thoughts :) please let me know what you think! |
|
|
||
| An SCS Release is an annual attestation that a curated set of third-party | ||
| open-source modular software stacks have been validated as a reliable basis for | ||
| building and operating a "Certified SCS-compatible IaaS" environment. The SCS |
There was a problem hiding this comment.
| building and operating a "Certified SCS-compatible IaaS" environment. The SCS | |
| building and operating "SCS-compatible IaaS" or "SCS-compatible KaaS" environments. The SCS |
Since the Releases are more than just IaaS. Furthermore I would just stick to SCS-compatible without the certified, since the releases can also be used to build environments that are not meant to be certified that want to be compatible whatsoever.
|
|
||
| To be attested in an SCS Release, a modular software stack MUST be in active | ||
| production use in at least one provider environment that holds a valid | ||
| "Certified SCS-compatible IaaS" certification at the time of the release. This |
There was a problem hiding this comment.
| "Certified SCS-compatible IaaS" certification at the time of the release. This | |
| "Certified SCS-compatible IaaS" or "Certified SCS-compatible KaaS" certification at the time of the release. This |
|
|
||
| For each modular software stack included in an SCS Release, there SHOULD be | ||
| comprehensive documentation covering the implementation-specific configuration | ||
| necessary to achieve and maintain "Certified SCS-compatible IaaS" compliance. |
There was a problem hiding this comment.
| necessary to achieve and maintain "Certified SCS-compatible IaaS" compliance. | |
| necessary to achieve and maintain "Certified SCS-compatible IaaS" or "Certified SCS-compatible KaaS" compliance. |
| ### Pillar 3: Automated Integration Testing (SHOULD) | ||
|
|
||
| Automated testing pipelines that validate the full modular software stack used | ||
| to deliver a "Certified SCS-compatible IaaS" environment SHOULD exist at the |
There was a problem hiding this comment.
| to deliver a "Certified SCS-compatible IaaS" environment SHOULD exist at the | |
| to deliver a "Certified SCS-compatible IaaS" or "Certified SCS-compatible KaaS" environment SHOULD exist at the |
|
@jklare thanks for the initiative. I added it to the agenda of today's PB meeting as well! |
|
Since we are about to remove the Drafts/ folder from this repository, we should decide what to do with this PR here. Any opinions on how to proceed with this topic? @SovereignCloudStack/project-board |
|
@jklare We could use this as a starting point for a Standard in the Global-Track that defines what an SCS-Release is. The starting point would be an open PR with the draft that this PR here contains. This way we can go ahead with cleaning up the standards repo (and the Drafts/ folder) and follow up on the topic. |
2 participants
AI-assisted: Claude Code