Merge branch 'main' into feat/add-flavor-page

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

@@ -4,6 +4,10 @@ type: Procedural
 status: Stable
 track: Global
 stabilized_at: 2022-11-28
+description: |
+  SCS-0001 outlines the structure, requirements, and lifecycle of standards, procedural documents, and decision
+  records within the Sovereign Cloud Stack (SCS) community, ensuring clarity, organization, and governance in
+  the development and maintenance of interoperable and transparent cloud infrastructure standards.
 ---
 
 ## Introduction

Standards/scs-0002-v2-standards-docs-org.md

@@ -6,6 +6,9 @@ authors: Max Wolfs
 status: Draft
 track: Global
 replaces: scs-0002-v1-standards-docs-org.md
+description: |
+  SCS-0002 outlines the standardized structure and maintenance processes for easily accessible and
+  comprehensible content of the SCS project.
 ---
 
 ## Introduction

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

@@ -3,6 +3,10 @@ title: Sovereign Cloud Standards YAML
 type: Procedural
 status: Draft
 track: Global
+description: |
+  SCS-0003 outlines the standards and certification processes for interoperable and sovereign cloud offerings,
+  categorizing certifications into levels and layers, and detailing their progression, prerequisites, and versioning
+  in a machine-readable YAML format for clarity, traceability, and tool integration.
 ---
 
 ## Introduction

Standards/scs-0100-v3-flavor-naming.md

@@ -5,6 +5,11 @@ status: Stable
 stabilized_at: 2023-06-14
 track: IaaS
 replaces: scs-0100-v2-flavor-naming.md
+description: |
+  The SCS Flavor Naming Standard provides a systematic approach for naming instance flavors in OpenStack
+  environments, ensuring backward compatibility and clarity on key features like the number of vCPUs, RAM,
+  and Root Disk, as well as extra features like GPU support and CPU generation. The standard aims for
+  usability and portability across all SCS flavors.
 ---
 
 ## Introduction

Standards/scs-0101-v1-entropy.md

@@ -3,6 +3,13 @@ title: SCS Entropy
 type: Standard
 status: Draft
 track: IaaS
+description: |
+  The SCS-0101 Entropy Standard ensures adequate entropy is available in virtual instances, crucial for operations
+  such as secure key creation in cryptography. The standard recommends using kernel version 5.18 or higher and
+  activating the hw_rng_model: virtio attribute for images, while compute nodes should employ CPUs with entropy
+  accessing instructions unfiltered by the hypervisor. It allows the infusion of the hosts entropy sources into
+  virtual instances and ensures the availability and quality of entropy in virtual environments, promoting system
+  security and efficiency.
 ---
 
 ## Introduction

Standards/scs-0102-v1-image-metadata.md

@@ -5,6 +5,12 @@ stabilized_at: 2022-10-31
 status: Stable
 track: IaaS
 replaces: Image-Metadata-Spec.md
+description: |
+  The SCS-0102 Image Metadata Standard outlines how to categorize and manage metadata for cloud-based operating
+  system images to ensure usability and clarity. The standard encompasses naming conventions, technical requirements,
+  image handling protocols including updating and origin, and licensing/support details. These guidelines ensure
+  that users can understand, access, and utilize OS images effectively, with clear information on features, updates,
+  and licensing provided through well-defined metadata properties.
 ---
 
 ## Motivation

Standards/scs-0103-v1-standard-flavors.md

@@ -3,6 +3,12 @@ title: SCS Standard Flavors and Properties
 type: Standard
 status: Draft
 track: IaaS
+description: |
+  The SCS-0103 standard outlines mandatory and recommended specifications for flavors and properties in OpenStack
+  environments to ensure uniformity across SCS clouds. Mandatory and recommended flavors are defined with specific
+  configurations of vCPUs, vCPU types, RAM, and root disk sizes, alongside extra specs like scs:name-vN, scs:cpu-type,
+  and scs:diskN-type to detail the flavor's specifications. This standard facilitates guaranteed availability and
+  consistency of flavors, simplifying the deployment process for DevOps teams.
 ---
 
 ## Introduction

Standards/scs-0104-v1-standard-images.md

@@ -3,6 +3,12 @@ title: SCS Standard Images
 type: Standard
 status: Draft
 track: IaaS
+description: |
+  The SCS-0104 standard establishes guidelines for virtual machine images in Sovereign Cloud Stack (SCS) environments,
+  specifying mandatory, recommended, and optional images via a YAML file, ensuring interoperability and streamlined
+  deployments. It mandates that image upload via Glance must be allowed, ensuring flexibility for users. The standard's
+  machine-readable document facilitates automated processing for compliance and integration purposes, promoting
+  consistency and reliability in cloud environments.
 ---
 
 ## Introduction

Standards/scs-0210-v1-k8s-new-version-policy.md

@@ -4,6 +4,12 @@ type: Standard
 status: Stable
 stabilized_at: 2023-02-07
 track: KaaS
+description: |
+  The SCS-0210 standard outlines the expected pace at which providers should adopt new Kubernetes versions, aiming
+  for alignment with the rapid development cycle of Kubernetes. Providers must offer the latest minor version within
+  four months of its release and the newest patch version within a week, ensuring users have timely access to security
+  updates, bug fixes, and features. The standard emphasizes the need for expedited updates for critical CVEs and
+  expects providers to thoroughly test new versions before deployment.
 ---
 
 ## Introduction

Standards/scs-0211-v1-kaas-default-storage-class.md

@@ -4,6 +4,11 @@ type: Standard
 status: Stable
 stabilized_at: 2023-02-13
 track: KaaS
+description: |
+  The SCS-0211 standard outlines the properties required for the default StorageClass in Kubernetes as a Service (KaaS).
+  The standard ensures that the default StorageClass, identified by the "storageclass.kubernetes.io/is-default-class"
+  annotation, supports the ReadWriteOnce access mode and protects volume data against loss due to single disk or
+  host hardware failures.
 ---
 
 ## Introduction

Standards/scs-0300-v1-requirements-for-sso-identity-federation.md

@@ -4,6 +4,13 @@ type: Decision Record
 status: Stable
 stabilized_at: 2023-06-21
 track: IAM
+description: |
+  The SCS-0300 standard outlines requirements for Single Sign-On (SSO) identity federation within the Sovereign
+  Cloud Stack (SCS). It addresses the need for customers to access SCS services using credentials stored and managed
+  externally, facilitating user onboarding and reducing the need for additional dedicated SCS accounts. The standard
+  focuses on delegating authentication to external identity providers and mapping users to roles within SCS for
+  authorization, while also considering the use of machine identities. Keycloak is the current choice as an Identity
+  Provider (IdP) for its support of OAuth 2.0 grants and its integration with OpenStack and kolla-ansible.
 ---
 
 ## Introduction

Standards/scs-0412-v1-metering-json.md

@@ -3,6 +3,12 @@ title: Exposition of IaaS metering data as JSON
 type: Standard
 status: Draft
 track: Ops
+description: |
+  The SCS-0412 standard addresses the need for a standardized interface to expose IaaS metering data in JSON format
+  within the Sovereign Cloud Stack (SCS). This is to aid cloud operators in integrating SCS IaaS layer data with
+  their existing billing and customer relationship systems. The standard adopts the Ceilometer HTTP hook format
+  provided by the OpenStack Ceilometer project for telemetry and metering, avoiding the need for additional translation
+  layers and implementation components.
 ---
 
 ## Introduction