Skip to content

Commit ac201ed

Browse files
committed
Replace yaml scopes by regular standards
Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>
1 parent 9089588 commit ac201ed

13 files changed

Lines changed: 280 additions & 9 deletions

Standards/scs-0001-v1-sovereign-cloud-standards.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -100,6 +100,7 @@ The second digit in `XXXX` describes the track where the document belongs:
100100
| KaaS | 2 |
101101
| IAM | 3 |
102102
| Ops | 4 |
103+
| Scopes | 5 |
103104

104105
In addition to the number, each document has the following metadata,
105106
embedded in the markdown header.

Standards/scs-0003-v1-sovereign-cloud-standards-yaml.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
11
---
22
title: Sovereign Cloud Standards YAML
33
type: Procedural
4-
status: Draft
4+
status: Deprecated
5+
deprecated_at: 2026-06-18
56
track: Global
67
description: |
78
SCS-0003 outlines the standards and certification processes for interoperable and sovereign cloud offerings,

Standards/scs-0004-v1-achieving-certification.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -26,12 +26,6 @@ As operator, I want to obtain a certificate with the scope SCS-compatible IaaS o
2626

2727
For public clouds, the SCS certification assessment body can take on this task provided that suitable access to test subject is supplied.
2828

29-
The test suite is partitioned according to resource usage; the required test intervals depend on this classification:
30-
31-
- _light_: at least daily,
32-
- _medium_: at least weekly,
33-
- _heavy_: at least monthly.
34-
3529
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.
3630

3731
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.

Standards/scs-0500-v1-scopes.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
title: SCS Certificate Scopes
3+
type: Standard
4+
track: Scopes
5+
status: Draft
6+
description: |
7+
Basic definitions and regulations regarding SCS certificate scopes.
8+
---
9+
10+
## Definition
11+
12+
In essence, a certificate scope is a standard that has to be fulfilled in order for a certificate to be awarded.
13+
It usually refers to other standards in regards to actual subject matter — what properties the subject
14+
has to satisfy —, and it contains regulations regarding the testing regime.
Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
---
2+
title: SCS-compatible IaaS
3+
type: Standard
4+
track: Scopes
5+
status: Deprecated
6+
stabilized_at: 2021-01-01
7+
deprecated_at: 2023-10-31
8+
description: |
9+
The certificate scope for level SCS-compatible and layer IaaS.
10+
---
11+
12+
## Introduction
13+
14+
This is v1 of the certificate scope _SCS-compatible IaaS_.
15+
16+
## Subject Matter
17+
18+
The following standards are included:
19+
20+
- OpenStack-powered Compute v2020.11
21+
- [scs-0100-v1: Flavor naming](https://docs.scs.community/standards/scs-0100-v1-flavor-naming)
22+
- [scs-0102-v1: Image metadata](https://docs.scs.community/standards/scs-0102-v1-image-metadata)
23+
24+
## Testing Regime
25+
26+
The following regulations apply for those certifications where regular testing is required.
27+
28+
In general, automated tests (where applicable) shall be performed at least weekly.
29+
30+
- Tests for OpenStack-powered Compute may be performed less frequently, but no fewer than once a year.
31+
32+
## Version history
33+
34+
- v2 amends v1 in the way outlined under 'subject matter'.
Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
---
2+
title: SCS-compatible IaaS
3+
type: Standard
4+
track: Scopes
5+
status: Deprecated
6+
stabilized_at: 2023-03-23
7+
deprecated_at: 2023-11-30
8+
replaces:
9+
- scs-0501-v2-scs-compatible-iaas.md
10+
description: |
11+
The certificate scope for level SCS-compatible and layer IaaS.
12+
---
13+
14+
## Introduction
15+
16+
This is v2 of the certificate scope _SCS-compatible IaaS_.
17+
18+
## Subject Matter
19+
20+
Standards that were already included in v1:
21+
22+
- [scs-0102-v1: Image metadata](https://docs.scs.community/standards/scs-0102-v1-image-metadata)
23+
24+
Standards changed in v2:
25+
26+
- OpenStack-powered Compute v2022.11 (instead of v2020.11)
27+
- [scs-0100-v2: Flavor naming](https://docs.scs.community/standards/scs-0100-v2-flavor-naming) (instead of [v1](https://docs.scs.community/standards/scs-0100-v1-flavor-naming))
28+
29+
## Testing Regime
30+
31+
The following regulations apply for those certifications where regular testing is required.
32+
33+
In general, automated tests (where applicable) shall be performed at least weekly.
34+
35+
- Tests for OpenStack-powered Compute may be performed less frequently, but no fewer than once a year.
36+
37+
## Version history
38+
39+
- v2 amends v1 in the way outlined under 'subject matter'.
Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
---
2+
title: SCS-compatible IaaS
3+
type: Standard
4+
track: Scopes
5+
status: Deprecated
6+
stabilized_at: 2023-06-15
7+
deprecated_at: 2024-07-31
8+
replaces:
9+
- scs-0501-v2-scs-compatible-iaas.md
10+
description: |
11+
The certificate scope for level SCS-compatible and layer IaaS.
12+
---
13+
14+
## Introduction
15+
16+
This is v3.1 of the certificate scope _SCS-compatible IaaS_.
17+
18+
## Subject Matter
19+
20+
Standards that were already included in v2:
21+
22+
- OpenStack-powered Compute v2022.11
23+
- [scs-0102-v1: Image metadata](https://docs.scs.community/standards/scs-0102-v1-image-metadata)
24+
25+
Standards changed in v3.1:
26+
27+
- [scs-0100-v3: Flavor naming (v3.1)](https://docs.scs.community/standards/scs-0100-v3-flavor-naming) (instead of v3.0)
28+
29+
## Testing Regime
30+
31+
The following regulations apply for those certifications where regular testing is required.
32+
33+
In general, automated tests (where applicable) shall be performed at least weekly.
34+
35+
- Tests for OpenStack-powered Compute may be performed less frequently, but no fewer than once a year.
36+
37+
## Version history
38+
39+
- Compared to v3.0, v3.1 includes v3.1 of [scs-0100-v3](https://docs.scs.community/standards/scs-0100-v3-flavor-naming) instead of v3.0.
40+
- Compared to v2.0, v3.0 includes v3.0 [scs-0100-v3](https://docs.scs.community/standards/scs-0100-v3-flavor-naming) instead of [scs-0100-v2](https://docs.scs.community/standards/scs-0100-v2-flavor-naming).
Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
---
2+
title: SCS-compatible IaaS
3+
type: Standard
4+
track: Scopes
5+
status: Deprecated
6+
stabilized_at: 2024-02-28
7+
deprecated_at: 2025-07-01
8+
replaces:
9+
- scs-0501-v3-scs-compatible-iaas.md
10+
description: |
11+
The certificate scope for level SCS-compatible and layer IaaS.
12+
---
13+
14+
## Introduction
15+
16+
This is v4 of the certificate scope _SCS-compatible IaaS_.
17+
18+
## Subject Matter
19+
20+
Standards that were already included in v3.1:
21+
22+
- OpenStack-powered Compute v2022.11
23+
- [scs-0100-v3: Flavor naming (v3.1)](https://docs.scs.community/standards/scs-0100-v3-flavor-naming)
24+
- [scs-0102-v1: Image metadata](https://docs.scs.community/standards/scs-0102-v1-image-metadata)
25+
26+
Standards new to v4:
27+
28+
- [scs-0101-v1: Entropy](https://docs.scs.community/standards/scs-0102-v1-image-metadata)
29+
- [scs-0103-v1: Standard flavors](https://docs.scs.community/standards/scs-0103-v1-standard-flavors)
30+
- [scs-0104-v1: Standard images](https://docs.scs.community/standards/scs-0104-v1-standard-images) with [spec file](https://raw.githubusercontent.com/SovereignCloudStack/standards/main/Tests/iaas/scs-0104-v1-images.yaml)
31+
32+
## Testing Regime
33+
34+
The following regulations apply for those certifications where regular testing is required.
35+
36+
In general, automated tests (where applicable) shall be performed at least weekly.
37+
38+
- Tests for OpenStack-powered Compute may be performed less frequently, but no fewer than once a year.
39+
40+
## Version history
41+
42+
- v4 extends v3 by including new standards as listed above.
Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
---
2+
title: SCS-compatible IaaS
3+
type: Standard
4+
track: Scopes
5+
status: Stable
6+
stabilized_at: 2024-12-19
7+
replaces:
8+
- scs-0501-v4-scs-compatible-iaas.md
9+
description: |
10+
The certificate scope for level SCS-compatible and layer IaaS.
11+
---
12+
13+
## Introduction
14+
15+
This is v5.1 of the certificate scope _SCS-compatible IaaS_.
16+
17+
## Subject Matter
18+
19+
Standards that were already included in v4:
20+
21+
- [scs-0128-v1: SCS end-to-end testing (formerly OpenStack-powered Compute)](https://docs.scs.community/standards/scs-0128-v1-e2e-testing)
22+
- [scs-0100-v3: Flavor naming (v3.1)](https://docs.scs.community/standards/scs-0100-v3-flavor-naming)
23+
- [scs-0101-v1: Entropy](https://docs.scs.community/standards/scs-0102-v1-image-metadata)
24+
- [scs-0102-v1: Image metadata](https://docs.scs.community/standards/scs-0102-v1-image-metadata)
25+
- [scs-0103-v1: Standard flavors](https://docs.scs.community/standards/scs-0103-v1-standard-flavors)
26+
27+
Standards changed with v5:
28+
29+
- [scs-0104-v1: Standard images](https://docs.scs.community/standards/scs-0104-v1-standard-images) with [new spec file](https://raw.githubusercontent.com/SovereignCloudStack/standards/main/Tests/iaas/scs-0104-v1-images-v5.yaml) instead of [former spec file](https://raw.githubusercontent.com/SovereignCloudStack/standards/main/Tests/iaas/scs-0104-v1-images.yaml)
30+
31+
Standards new to v5:
32+
33+
- [scs-0114-v1: Volume Types](https://docs.scs.community/standards/scs-0114-v1-volume-type-standard)
34+
- [scs-0115-v1: Default rules for security groups](https://docs.scs.community/standards/scs-0115-v1-default-rules-for-security-groups)
35+
- [scs-0116-v1: Key manager](https://docs.scs.community/standards/scs-0116-v1-key-manager-standard)
36+
- [scs-0117-v1: Volume backup](https://docs.scs.community/standards/scs-0117-v1-volume-backup-service)
37+
- [scs-0121-v1: Availability Zones](https://docs.scs.community/standards/scs-0121-v1-Availability-Zones-Standard)
38+
- [scs-0123-v1: Mandatory and Supported IaaS Services](https://docs.scs.community/standards/scs-0123-v1-mandatory-and-supported-IaaS-services)
39+
- [scs-0302-v1: Domain Manager Role](https://docs.scs.community/standards/scs-0302-v1-domain-manager-role)
40+
41+
## Testing Regime
42+
43+
The following regulations apply for those certifications where regular testing is required.
44+
45+
In general, automated tests (where applicable) shall be performed at least weekly.
46+
47+
- Tests for scs-0128-v1 may be performed less frequently, but no fewer than once a year.
48+
49+
## Version history
50+
51+
- v5.1 amends v5 by including the standard scs-0123-v1,
52+
which was intended to be included (as witnessed by the meeting minutes),
53+
but inadvertently omitted.
54+
- v5 extends v4 by including new standards as listed above,
55+
and it changes the spec for scs-0104-v1, updating standard images.
Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
---
2+
title: "SCS-compatible IaaS: Testing Notes"
3+
type: Supplement
4+
track: Scopes
5+
supplements:
6+
- scs-0501-v5-scs-compatible-iaas.md
7+
---
8+
9+
## Testing notes
10+
11+
(refer to documentation of official test suite)

0 commit comments

Comments
 (0)