Skip to content

Commit fc8103e

Browse files
depressiveRobotmbuechsefkr
authored
replace exception rule by Incubator status (#1026)
* replace exception rule by Incubator status * fix links * Reword to implement latest consensus by SIG Std/Cert * use "scoring system" instead of "criteria" * introduce certificate levels * update supplement with explanations on certification process * delete wrongly committed supplement * update scoring system * Bugfix: remove nonsensical distinction * Update Standards/scs-0007-v2-certification-integrators.md * Update Standards/scs-0007-v2-certification-integrators.md * Update Standards/scs-0007-v2-certification-integrators.md * fix tier vs level * add note for additional evidence * make score for public clouds IaaS-specific --------- Signed-off-by: Marvin Frommhold <depressiveRobot@users.noreply.github.com> Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud> Signed-off-by: Felix Kronlage-Dammers <fkr@hazardous.org> Co-authored-by: Matthias Büchse <matthias.buechse@alasca.cloud> Co-authored-by: Felix Kronlage-Dammers <fkr@hazardous.org>
1 parent 8c109ba commit fc8103e

File tree

2 files changed

+80
-26
lines changed

2 files changed

+80
-26
lines changed
Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
---
2+
title: Certification of integrators
3+
type: Procedural
4+
status: Draft
5+
#stabilized_at: YYYY-MM-DD # TODO when Stable
6+
replaces:
7+
- scs-0007-v1-certification-integrators.md
8+
track: Global
9+
description: |
10+
SCS-0007 defines the process and rules on how to become certified as SCS Integrator.
11+
---
12+
13+
## Introduction
14+
15+
The purpose of this document is to describe a concept for how an implementation partner (also referred to as an applicant) can obtain certification as SCS Integrator. In essence, this certificate is intended to express that an applicant has sufficient technical knowledge and experience to provide technical support to other organizations using SCS.
16+
By design, this certification demands to reach a certain score based on a predefined scoring system. As it may take some time for an aspiring applicant to become an SCS Integrator, a lesser variant of the certificate, called SCS Bronze Integrator, is also defined which can be achieved with a lower score.
17+
18+
## Motivation
19+
20+
As an implementation partner, I want to become certified as SCS Integrator in order to prove sufficient technical knowledge and experience to provide technical support for SCS.
21+
22+
## Regulations
23+
24+
The certificates are awarded for a period of one year based on the predefined scoring system below.
25+
The certification is done either by the Forum SCS-Standards or an attestation body nominated by the forum.
26+
27+
### Certificate tiers
28+
29+
Version 2 of this standard introduces tiers of certifications beginning with Silver and Bronze tiers. The tiers are awarded according to a target score to be reached based on a predefined scoring system (see below).
30+
31+
- Certified SCS IaaS Integrator (Silver): SCS IaaS (Infrastructure as a Service) implementation partner
32+
- Certified SCS KaaS Integrator (Silver): SCS KaaS (Kubernetes as a Service) implementation partner
33+
- Certified SCS IaaS Integrator (Bronze): aspiring SCS IaaS (Infrastructure as a Service) implementation partner
34+
- Certified SCS KaaS Integrator (Bronze): aspiring SCS KaaS (Kubernetes as a Service) implementation partner
35+
36+
As to remain backward compatibility with version 1 of this standard, the suffix for the "Silver" tier MAY be omitted. The tier _Certified SCS IaaS Integrator (Silver)_ and _Certified SCS KaaS Integrator (Silver)_ therefore corresponds to the previously existing certificates _Certified SCS IaaS Integrator_ and _Certified SCS KaaS Integrator_ from version 1 of this standard. Certificates that have already been issued remain valid and will get updated when issued once again.
37+
38+
### General expectations
39+
40+
The general expectation for certification is to provide proof of experience in setting up, operating and supporting SCS-compliant environments.
41+
42+
SCS is an open source community project with the goal of enabling digital sovereignty. As such, the commitment and support of this mission SHOULD be recognized and promoted beyond technical competence.
43+
44+
The applicant SHOULD work towards ensuring that digital sovereignty is implemented in accordance with the SCS definition (Standards and [Mission Statement](https://docs.scs.community/community/mission-statement)). This is expressed in a way that, in addition to the technology used to build environments (not necessarily only SCS environments), knowledge and experience in SCS standards compliance (SCS-compatible IaaS and KaaS) is also available and that environments built by the applicant have already been configured in accordance with the standards and are listed on the SCS compliance list.
45+
46+
The applicant SHOULD work towards ensuring that the cloud environments it sets up and/or manages are also officially visible as SCS clouds, thereby strengthening the SCS brand.
47+
48+
### Scoring system
49+
50+
The applicant MUST achieve a total of at least FOUR points to become SCS Silver Integrator or at least TWO points to qualify as SCS Bronze Integrator according to the following scoring system:
51+
52+
- two points for each SCS-compliant environment of a third party successfully brought into production by the applicant in the last 12 months;
53+
- two points for each SCS-compliant environment of a third party actively being managed by the applicant for the last 12 months, one point for 6 months;
54+
- two points for each SCS-compliant IaaS public-cloud environment with at least two regions or at least three availability zones being operated by the applicant for the last 12 months, one point for 6 months.
55+
56+
Here, an SCS-compliant environment is one that qualifies for [_Certified SCS-compatible IaaS_](https://docs.scs.community/standards/scs-compatible-iaas) or [_Certified SCS-compatible KaaS_](https://docs.scs.community/standards/scs-compatible-kaas), depending on the desired certification.
57+
58+
### Attestation
59+
60+
The audit for the certification of an applicant is carried out by the Forum SCS-Standards or an attestation body. It will assess and, if necessary, obtain evidence from the applicant to be able to estimate which score will be achieved in total and how.
61+
62+
## Version history
63+
64+
- Version 1 introduced the certification as SCS Integrator with the option to request for a voting on exceptions.
65+
- Version 2 introduces tiers of certifications with a predefined scoring system in order to avoid the previously ambiguous voting on exceptions.
Lines changed: 15 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,36 +1,25 @@
11
---
2-
title: "Implementation hints for achieving Certified SCS Integrator"
2+
title: "Implementation hints for achieving SCS Integrator certification"
33
type: Supplement
44
track: Global
55
supplements:
6-
- scs-0007-v1-certification-integrators.md
6+
- scs-0007-v2-certification-integrators.md
77
---
88

99
## Introduction
1010

1111
The standard scs-0007 documents what requirements integration partners must fulfill to be eligible
1212
for being certified as SCS Integrators.
13-
This document contains hints how these requirements may be evaluated by the Forum SCS-Standards
14-
auditor and how exceptions will be handled.
15-
16-
### Voting on exceptions
17-
18-
When someone requests approval for a certified SCS integrator that does not meet all requirements,
19-
this can be waived with a qualified vote in the Forum SCS-Standards.
20-
To avoid conflict of interests and social pressure clouding this exception, we envision the
21-
following process:
22-
23-
- The beneficiary party (the integrator in whose favor the exception is requested) should be
24-
invited to a meeting to explain why they believe that they qualify as a certified SCS
25-
integrator despite not meeting the normal qualification criteria.
26-
- The forum members may ask the beneficiary clarifying questions that should be answered.
27-
- To ensure an open discussion, the beneficiary should be excluded from the discussions about
28-
the matter. The same applies if the beneficiary party is a member of the Forum
29-
SCS-Standards. In that case, the expulsion should not be counted against the required quorum
30-
to avoid forum members from having a disadvantage. If the excluded party is a voting member,
31-
they will automatically abstain from the vote.
32-
- Any parties that have significant conflicts of interests are expected to make these
33-
conflicts transparent and cast abstention votes.
34-
35-
By the time of re-certification, all exceptions from a previous certification should have been
36-
eliminated.
13+
This document describes the process and associated checks used to validate an applicant's suitability based on plausibility checks and the evidence submitted.
14+
15+
## Certification process procedure
16+
17+
To apply for a certification as an SCS Integrator, an application request must be sent to the attestation body. In the application request, the applicant specifies the certification tier for which it is applying. The relevant SCS-compliant environments must also be specified as references therein, which should be used to calculate the necessary score according to the scoring system.
18+
19+
If the listed references are joint environments (e.g. two or more implementation partners have jointly set up an SCS environment or manage them together), it must be sufficiently demonstrated what the applicant's own share in the setup and operation of the environment is.
20+
21+
As specified in standard scs-0007, the listed references must also be compatible with standard scs-0004, which means they must qualify as [_Certified SCS-compatible IaaS_](https://docs.scs.community/standards/scs-compatible-iaas) or [_Certified SCS-compatible KaaS_](https://docs.scs.community/standards/scs-compatible-kaas). However, they do not necessarily have to be certified according to SCS-0004. It is sufficient to demonstrate that the respective environment meets the corresponding scope in its current version. Proof is provided by running the official [SCS compliance test suite](https://github.com/SovereignCloudStack/standards/tree/main/Tests), whereby all tests must pass. The test suite can be run either by the applicant or the attestation body. For all standards included in the scope that are not covered by the test suite, additional evidence must also be provided. Ideally, the test report and additional evidence should be submitted directly together with the application request.
22+
23+
In the next step, the attestation body conducts an examination based on the application request and the accompanying evidence provided. The attestation body gets in contact with the applicant in order to resolve any remaining discrepancies and open issues together.
24+
25+
If there are no outstanding issues and all requirements have been sufficiently met with the relevant evidence, the respective certificate according to the score achieved will be issued.

0 commit comments

Comments
 (0)