SCS Standard Images: Implementation Notes
Introduction
The SCS standard on standard images does not in itself lay down what images are actually required or recommended; rather it specifies the format of a YAML file that in turn serves said purpose. The particular YAML file that an implementer (a cloud service provider or operator) has to comply with is given in the respective version of the certificate scope "SCS-compatible IaaS" as a parameter to the standard. This document is intended to give implementers a step-by-step guide on how to comply with the SCS certificate scope.
Step-by-step walkthrough
Option A: pragmatic
Run the test script on your environment and check the error messages :)
-
Check out the standards repository.
git clone https://github.com/SovereignCloudStack/standards.git
cd standards -
Install requirements:
python3 -m venv .venv && source .venv/bin/activate
pip install -r requirements.txt -
Make sure that your
OS_CLOUD
environment variable is set. -
Run the main check script:
python3 ./Tests/scs-compliance-check.py ./Tests/scs-compatible-iaas.yaml -t standard-images-check \
-s $OS_CLOUD -a os_cloud=$OS_CLOUD -o report.yaml -C -
Inspect console output (stderr) for error messages.
Option B: principled
- Find your intended version of the certificate scope in the overview table. It will most likely be one whose 'State' is 'Effective' or 'Stable'.
- In (or below) the row labeled 'scs-0104: Standard images', you find a link to the YAML file that lists mandatory and recommended images, such as scs-0104-v1-images.yaml for v4 of the certificate scope.
- For each entry under
images
, ensure the following (either manually or by using the OpenStack Image Manager described in the section "Operational Tooling"):- if the entry says
status: mandatory
, your environment MUST provide this image, i.e., an image whose name matches thename_scheme
or (in absence of a name scheme) thename
. - every actual image in your environment that matches the
name_scheme
or (in absence of a name scheme) thename
has the correctimage_source
property: its value MUST start with one of the prefixes listed undersource
.
- if the entry says
Operational Tooling
The openstack-image-manager is able to create all standard, mandatory SCS images for you given image definitions from a YAML file. Please see its documentation for details.