Replace yaml scopes by regular standards

mbuechse · mbuechse · commit 1cbfb7d31f49 · 2026-06-06T15:10:37.000+02:00
Signed-off-by: Matthias Büchse &lt;matthias.buechse@alasca.cloud&gt;
diff --git a/Standards/scs-0001-v1-sovereign-cloud-standards.md b/Standards/scs-0001-v1-sovereign-cloud-standards.md
@@ -100,6 +100,7 @@ The second digit in `XXXX` describes the track where the document belongs:
 | KaaS | 2 |
 | IAM | 3 |
 | Ops | 4 |
+| Scopes | 5 |
 
 In addition to the number, each document has the following metadata,
 embedded in the markdown header.
diff --git a/Standards/scs-0003-v1-sovereign-cloud-standards-yaml.md b/Standards/scs-0003-v1-sovereign-cloud-standards-yaml.md
@@ -1,7 +1,8 @@
 ---
 title: Sovereign Cloud Standards YAML
 type: Procedural
-status: Draft
+status: Deprecated
+deprecated_at: 2026-06-18
 track: Global
 description: |
   SCS-0003 outlines the standards and certification processes for interoperable and sovereign cloud offerings,
diff --git a/Standards/scs-0004-v1-achieving-certification.md b/Standards/scs-0004-v1-achieving-certification.md
@@ -26,12 +26,6 @@ As operator, I want to obtain a certificate with the scope SCS-compatible IaaS o
 
    For public clouds, the SCS certification assessment body can take on this task provided that suitable access to test subject is supplied.
 
-   The test suite is partitioned according to resource usage; the required test intervals depend on this classification:
-
-    - _light_: at least daily,
-    - _medium_: at least weekly,
-    - _heavy_: at least monthly.
-
 3. If the desired certificate requires manual checks, then the operator MUST offer suitable documentation to the SCS certification assessment body. The operator MUST ensure that these checks are repeated once every quarter. In addition, the SCS certification assessment body reserves the right to occasionally verify documentation on premises.
 
 4. Details on the standards achieved, as well as the current state and the history of all test and check results of the past 18 months will be displayed on a public webpage (henceforth, _certificate status page_) owned by SCS.
diff --git a/Standards/scs-0500-v1-scopes.md b/Standards/scs-0500-v1-scopes.md
@@ -0,0 +1,14 @@
+---
+title: SCS Certificate Scopes
+type: Standard
+track: Scopes
+status: Draft
+description: |
+  Basic definitions and regulations regarding SCS certificate scopes.
+---
+
+## Definition
+
+In essence, a certificate scope is a standard that has to be fulfilled in order for a certificate to be awarded.
+It usually refers to other standards in regards to actual subject matter -- what properties the subject
+has to satisfy --, and it contains regulations regarding the testing regime.
diff --git a/Standards/scs-0501-v5-scs-compatible-iaas.md b/Standards/scs-0501-v5-scs-compatible-iaas.md
@@ -0,0 +1,50 @@
+---
+title: SCS-compatible IaaS
+type: Standard
+track: Scopes
+status: Stable
+stabilized_at: 2024-12-19
+description: |
+  The certificate scope for level SCS-compatible and layer IaaS.
+---
+
+## Introduction
+
+This is v5.1 of the certificate scope _SCS-compatible IaaS_.
+
+## Subject Matter
+
+Standards that were already included in v4:
+
+- [scs-0128-v1: SCS end-to-end testing (formerly OpenStack-powered Compute)](https://docs.scs.community/standards/scs-0128-v1-e2e-testing)
+- [scs-0100-v3: Flavor naming (v3.1)](https://docs.scs.community/standards/scs-0100-v3-flavor-naming)
+- [scs-0101-v1: Entropy](https://docs.scs.community/standards/scs-0102-v1-image-metadata)
+- [scs-0102-v1: Image metadata](https://docs.scs.community/standards/scs-0102-v1-image-metadata)
+- [scs-0103-v1: Standard flavors](https://docs.scs.community/standards/scs-0103-v1-standard-flavors)
+- [scs-0104-v1: Standard images](https://docs.scs.community/standards/scs-0104-v1-standard-images) ([spec](https://raw.githubusercontent.com/SovereignCloudStack/standards/main/Tests/iaas/scs-0104-v1-images-v5.yaml))
+
+Standards new to v5:
+
+- [scs-0114-v1: Volume Types](https://docs.scs.community/standards/scs-0114-v1-volume-type-standard)
+- [scs-0115-v1: Default rules for security groups](https://docs.scs.community/standards/scs-0115-v1-default-rules-for-security-groups)
+- [scs-0116-v1: Key manager](https://docs.scs.community/standards/scs-0116-v1-key-manager-standard)
+- [scs-0117-v1: Volume backup](https://docs.scs.community/standards/scs-0117-v1-volume-backup-service)
+- [scs-0121-v1: Availability Zones](https://docs.scs.community/standards/scs-0121-v1-Availability-Zones-Standard)
+- [scs-0123-v1: Mandatory and Supported IaaS Services](https://docs.scs.community/standards/scs-0123-v1-mandatory-and-supported-IaaS-services)
+- [scs-0302-v1: Domain Manager Role](https://docs.scs.community/standards/scs-0302-v1-domain-manager-role)
+
+## Testing Regime
+
+The following regulations apply for those certifications where regular testing is required.
+
+In general, automated tests (where applicable) shall be performed at least weekly.
+
+- Tests for scs-0128-v1 may be performed less frequently, but no fewer than once a year.
+
+## Version history
+
+- v5.1 amends v5 by including the standard scs-0123-v1,
+  which was intended to be included (as witnessed by the meeting minutes),
+  but inadvertently omitted.
+- v5 extends v4 by including new standards as listed above,
+  and it changes the spec for scs-0104-v1, updating standard images.
diff --git a/Standards/scs-0501-w1-scs-compatible-iaas-testing.md b/Standards/scs-0501-w1-scs-compatible-iaas-testing.md
@@ -0,0 +1,11 @@
+---
+title: "SCS-compatible IaaS: Testing Notes"
+type: Supplement
+track: Scopes
+supplements:
+  - scs-0501-v5-scs-compatible-iaas.md
+---
+
+## Testing notes
+
+(refer to documentation of official test suite)
diff --git a/Standards/scs-0502-v1-scs-compatible-kaas.md b/Standards/scs-0502-v1-scs-compatible-kaas.md
@@ -0,0 +1,29 @@
+---
+title: SCS-compatible KaaS
+type: Standard
+track: Scopes
+status: Stable
+stabilized_at: 2024-11-26
+description: |
+  The certificate scope for level SCS-compatible and layer KaaS.
+---
+
+## Introduction
+
+This is v1 of the certificate scope _SCS-compatible KaaS_.
+
+## Subject Matter
+
+- [scs-0201-v1: CNCF Kubernetes conformance](https://docs.scs.community/standards/scs-0201-v1-cncf-conformance)
+- [scs-0210-v2: Kubernetes version policy](https://docs.scs.community/standards/scs-0210-v2-k8s-version-policy)
+- [scs-0214-v2: Kubernetes node distribution and availability](https://docs.scs.community/standards/scs-0214-v2-k8s-node-distribution)
+- [scs-0219-v1: KaaS networking](https://docs.scs.community/standards/scs-0219-v1-kaas-networking)
+
+## Testing Regime
+
+The following regulations apply for those certifications where regular testing is required.
+
+In general, automated tests (where applicable) shall be performed at least weekly.
+
+- Tests for scs-0210-v2 shall be performed daily.
+- Tests for scs-0201-v1 and scs-0219-v1 may be performed less frequently, but no fewer than once a year.
diff --git a/Standards/scs-0502-w1-scs-compatible-kaas-testing.md b/Standards/scs-0502-w1-scs-compatible-kaas-testing.md
@@ -0,0 +1,11 @@
+---
+title: "SCS-compatible KaaS: Testing Notes"
+type: Supplement
+track: Scopes
+supplements:
+  - scs-0502-v5-scs-compatible-kaas.md
+---
+
+## Testing notes
+
+(refer to documentation of official test suite)
diff --git a/Tests/chk_adrs.py b/Tests/chk_adrs.py
@@ -43,7 +43,7 @@ def iso_date(value):
 FRONT_MATTER_KEYS = {
     "type": ("Procedural", "Standard", "Decision Record").__contains__,
     "status": ("Proposal", "Draft", "Stable", "Deprecated", "Rejected").__contains__,
-    "track": ("Global", "IaaS", "KaaS", "IAM", "Ops").__contains__,
+    "track": ("Global", "IaaS", "KaaS", "IAM", "Ops", "Scopes").__contains__,
     "deprecated_at": optional(iso_date),
     "stabilized_at": optional(iso_date),
     "rejected_at": optional(iso_date),
