From 59f92c11b21fcd1c9645f552b86f60680ee035cc Mon Sep 17 00:00:00 2001 From: Kurt Garloff Date: Thu, 27 Nov 2025 16:18:56 +0100 Subject: [PATCH 1/3] Avoid CPU:Mem which confuses some markdown parsers. Signed-off-by: Kurt Garloff --- Standards/scs-0100-v1-flavor-naming.md | 2 +- Standards/scs-0100-v2-flavor-naming.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Standards/scs-0100-v1-flavor-naming.md b/Standards/scs-0100-v1-flavor-naming.md index d874cdf53..86a0175b9 100644 --- a/Standards/scs-0100-v1-flavor-naming.md +++ b/Standards/scs-0100-v1-flavor-naming.md @@ -321,7 +321,7 @@ Extensions need to be specified in the above-mentioned order. These are flavors expected to exist on standard SCS clouds (x86-64). We expect disk sizes to be 5, 10, 20, 50, 100, 200, 500, 1000GB, 2000GB. -We expect a typical CPU:Mem[GiB] ratio of 1:4. +We expect a typical CPU\:Mem[GiB] ratio of 1:4. | vCPU:RAM ratio | Mandatory Flavors | | -------------- | -------------------------- | diff --git a/Standards/scs-0100-v2-flavor-naming.md b/Standards/scs-0100-v2-flavor-naming.md index 38d405828..946a44797 100644 --- a/Standards/scs-0100-v2-flavor-naming.md +++ b/Standards/scs-0100-v2-flavor-naming.md @@ -224,7 +224,7 @@ so users can expect some level of parallelism and independence. These are flavors that must exist on standard SCS clouds (x86-64). We expect disk sizes to be 5, 10, 20, 50, 100, 200, 500, 1000GB, 2000GB. -We expect a typical CPU:Mem[GiB] ratio of 1:4. +We expect a typical CPU to Mem[GiB] ratio of 1 to 4. | vCPU:RAM ratio | Mandatory Flavors | | -------------- | -------------------------- | From b105c8d4d48aaa2047f036dac74272004042ddd5 Mon Sep 17 00:00:00 2001 From: Kurt Garloff Date: Fri, 28 Nov 2025 10:47:12 +0100 Subject: [PATCH 2/3] Also escape CPU:RAM in scs-0103-v1. Signed-off-by: Kurt Garloff --- Standards/scs-0103-v1-standard-flavors.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Standards/scs-0103-v1-standard-flavors.md b/Standards/scs-0103-v1-standard-flavors.md index b85d66288..85e61f035 100644 --- a/Standards/scs-0103-v1-standard-flavors.md +++ b/Standards/scs-0103-v1-standard-flavors.md @@ -132,7 +132,7 @@ In addition, the following properties must be set (in the `extra_specs`): ### Remarks -We expect the most used vCPU:RAM[GiB] ratio to be 1:4. +We expect the most used vCPU\:RAM[GiB] ratio to be 1:4. Note that all vCPUs of SCS standard flavors are oversubscribed — the smallest `1L-1` flavor allows for heavy oversubscription (note the `L`), and thus can be offered very From f05d17b03e68bd60f09c6199bd3428ec7dde508b Mon Sep 17 00:00:00 2001 From: Kurt Garloff Date: Fri, 28 Nov 2025 10:51:48 +0100 Subject: [PATCH 3/3] Fix link to flavor-name-check.py script. Otherwise our CI will complain. Rightly so. Signed-off-by: Kurt Garloff --- Standards/scs-0100-v1-flavor-naming.md | 2 +- Standards/scs-0100-v2-flavor-naming.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/Standards/scs-0100-v1-flavor-naming.md b/Standards/scs-0100-v1-flavor-naming.md index 86a0175b9..1e69f8fb6 100644 --- a/Standards/scs-0100-v1-flavor-naming.md +++ b/Standards/scs-0100-v1-flavor-naming.md @@ -422,7 +422,7 @@ considered broken by the SCS team. ## Validation -There is a script in [flavor_name_check.py](https://github.com/SovereignCloudStack/standards/blob/main/Tests/iaas/flavor-naming/flavor-name-check.py) +There is a script in [flavor-name-check.py](https://github.com/SovereignCloudStack/standards/blob/main/Tests/iaas/scs_0100_flavor_naming/flavor-name-check.py) which can be used to decode, validate and construct flavor names. This script must stay in sync with the specification text. diff --git a/Standards/scs-0100-v2-flavor-naming.md b/Standards/scs-0100-v2-flavor-naming.md index 946a44797..7a85a8efc 100644 --- a/Standards/scs-0100-v2-flavor-naming.md +++ b/Standards/scs-0100-v2-flavor-naming.md @@ -295,7 +295,7 @@ to suggest extensions that we can discuss and add to the official scheme. ## Validation -There is a script in [`flavor_name_check.py`](https://github.com/SovereignCloudStack/standards/blob/main/Tests/iaas/flavor-naming/flavor-name-check.py) +There is a script in [`flavor-name-check.py`](https://github.com/SovereignCloudStack/standards/blob/main/Tests/iaas/scs_0100_flavor_naming/flavor-name-check.py) which can be used to decode, validate and construct flavor names. This script must stay in sync with the specification text.