-
Notifications
You must be signed in to change notification settings - Fork 23
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into feat/add-certification-process2
- Loading branch information
Showing
12 changed files
with
407 additions
and
250 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,28 @@ | ||
| name: Check Go syntax | ||
|
|
||
| on: | ||
| push: | ||
| paths: | ||
| - 'Tests/kaas/kaas-sonobuoy-tests/**/*.go' | ||
| - .github/workflows/lint-go.yml | ||
|
|
||
| jobs: | ||
| lint-go-syntax: | ||
| runs-on: ubuntu-latest | ||
| steps: | ||
| - uses: actions/checkout@v4 | ||
|
|
||
| - name: Set up Go | ||
| uses: actions/setup-go@v4 | ||
| with: | ||
| go-version: '1.23' | ||
|
|
||
| # Install golangci-lint | ||
| - name: Install golangci-lint | ||
| run: | | ||
| curl -sSfL https://raw.githubusercontent.com/golangci/golangci-lint/master/install.sh | sh -s -- -b $(go env GOPATH)/bin v1.61.0 | ||
| # Run golangci-lint | ||
| - name: Run golangci-lint | ||
| working-directory: Tests/kaas/kaas-sonobuoy-tests | ||
| run: golangci-lint run ./... -v |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,42 @@ | ||
| --- | ||
| title: "SCS Availability Zone Standard: Implementation and Testing Notes" | ||
| type: Supplement | ||
| track: IaaS | ||
| status: Draft | ||
| supplements: | ||
| - scs-0121-v1-Availability-Zones-Standard.md | ||
| --- | ||
|
|
||
| ## Automated Tests | ||
|
|
||
| The standard will not preclude small deployments and edge deployments, that both will not meet the requirement for being divided into multiple Availability Zones. | ||
| Thus multiple Availability Zones are not always present. | ||
| Somtimes there can just be a single Availability Zones. | ||
| Because of that, there will be no automated tests to search for AZs. | ||
|
|
||
| ## Required Documentation | ||
|
|
||
| The requirements for each Availability Zone are written in the Standard. | ||
| For each deployment, that uses more than a single Availability Zone, the CSP has to provide documentation to proof the following points: | ||
|
|
||
| 1. The presence of fire zones MUST be documented (e.g. through construction plans of the deployment). | ||
| 2. The correct configuration of one AZ per fire zone MUST be documented. | ||
| 3. The redundancy in Power Supply within each AZ MUST be documented. | ||
| 4. The redundancy in external connection within each AZ MUST be documented. | ||
| 5. The redundancy in core routers within each AZ MUST be documented. | ||
|
|
||
| All of these requirements will either not change at all like the fire zones or it is very unlikely for them to change like redundant internet connection. | ||
| Because of this documentation must only be provided in the following cases: | ||
|
|
||
| 1. When a new deployment with multiple AZs should be tested for compliance. | ||
| 2. When there are physical changes in a deplyoment, which already provided the documentation: the changes needs to be documented and provided as soon as possible. | ||
|
|
||
| ### Alternative Documentation | ||
|
|
||
| If a deployment already did undergo certification like ISO 27001 or ISO 9001, those certificates can be provided as part of the documentation to cover the redundancy parts. | ||
| It is still required to document the existence of fire zones and the correct configuration of one AZ per fire zone. | ||
|
|
||
| ## Physical Audits | ||
|
|
||
| In cases where it is reasonable to mistrust the provided documentation, a physical audit by a natural person - called auditor - send by e.g. the [OSBA](https://osb-alliance.de/) should be performed. | ||
| The CSP of the deployment, which needs such an audit, should grant access to the auditor to the physical infrastructure and should show them all necessary IaaS-Layer configurations, that are needed to verify compliance to this standard. |
Oops, something went wrong.