Simplify scs-0101-v1 to remove gratuitous regulation

Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud>

Author: mbuechse

Standards/scs-0101-v1-entropy.md

@@ -96,15 +96,11 @@ will be available in virtual instances.
 
 ### Flavors
 
-It is recommended that all flavors have the following attribute:
+The following optional flavor extra_specs are relevant in case an
+external HRNG is to be used:
 
 ```console
 hw_rng:allowed=True
-```
-
-The following attributes are optional:
-
-```console
 hw_rng:rate_bytes - The allowed amount of bytes for the the guest
     to read from the host's entropy per period.
 hw_rng:rate_period - Sets the duration of a read period in seconds.
@@ -116,9 +112,10 @@ It is recommended to use images having a kernel (patch level) version 5.18
 or up. This condition is already satisfied by every mandatory image defined
 in the [Image Metadata Standard](https://github.com/SovereignCloudStack/standards/blob/main/Standards/scs-0102-v1-image-metadata.md).
 
-It is recommended that images activate the attribute `hw_rng_model: virtio`.
+An image may activate the attribute `hw_rng_model: virtio` so
+that an external HRNG can be used.
 
-The daemon `rngd` must be installed (usually from `rng-tools`
+The daemon `rngd` may be installed (usually from `rng-tools`
 or `rng-utils`).
 
 The user may choose to use the `virtio-rng` device via `rngd`.

Standards/scs-0101-w1-entropy-implementation-testing.md

@@ -12,24 +12,16 @@ With reasonably recent hardware—x86 CPU with RDRAND/RDSEED (Intel from 2012,
 AMD from 2015) or ARM CPU with FEAT_RNG or FEAT_RNG_TRAP—and recent VM image—Linux
 kernel 5.18 or higher—, there is (almost) nothing to be done.
 
-Only the flavor and image attributes required by the standard have to be set:
-
-- flavor extra_spec: `hw_rng:allowed=True` ,
-- image property: `hw_rng_model: virtio` .
-
 ## Automated tests
 
 The following testcases [are implemented](https://github.com/SovereignCloudStack/standards/blob/main/Tests/iaas/openstack_test.py):
 
-- `scs-0101-image-property` ensures that each flavor has the extra spec `hw_rng:allowed=True`,
-- `scs-0101-flavor-property` ensures that each public image has the property `hw_rng_model: virtio`,
-- `scs-0101-rngd` ensures that the service `rngd` is present on a sample VM,
 - `scs-0101-entropy-avail` ensures that the special file `/proc/sys/kernel/random/entropy_avail` contains
   the value 256 (pinned since kernel 5.18) on a sample VM,
 - `scs-0101-fips-test` ensures that the number of FIPS 140-2 failures is below 5 out of 1000 blocks
   tested, as determined by `cat /dev/random | rngtest -c 1000` on a sample VM.
 
-Note: The latter two items act as surrogates for the following item, which
+These testcases act as surrogates for the following item, which
 cannot be detected directly:
 
 - CPU instructions for accessing entropy are available to the VMs.
@@ -39,6 +31,12 @@ checked, because of two reasons: (a) we already check the file `entropy_avail`
 (see subsection on Errors), and (b) users can always choose a recent image,
 as ensured by the image metadata standard.
 
+Three further testcases are available, but currently unused:
+
+- `scs-0101-image-property` ensures that each flavor has the extra spec `hw_rng:allowed=True`,
+- `scs-0101-flavor-property` ensures that each public image has the property `hw_rng_model: virtio`,
+- `scs-0101-rngd` ensures that the service `rngd` is present on a sample VM.
+
 ## Manual tests
 
 None.

Tests/scs-compatible-iaas.yaml

@@ -305,12 +305,8 @@ modules:
     url: https://docs.scs.community/standards/scs-0101-v1-entropy
     targets:
       main:
-      - scs-0101-rngd
       - scs-0101-entropy-avail
       - scs-0101-fips-test
-      recommended:
-      - scs-0101-flavor-property
-      - scs-0101-image-property
   - id: scs-0102-v1
     name: Image metadata v1
     url: https://docs.scs.community/standards/scs-0102-v1-image-metadata
@@ -527,7 +523,7 @@ versions:
     include:
       - opc-v2022.11
       - scs-0100-v3.1
-      - scs-0101-v1
+      # - scs-0101-v1  remove this because it hasn't been an issue for quite a while
       - scs-0102-v2  # instead of scs-0102-v1
       - scs-0103-v1
       - ref: scs-0104-v1-2