Sync stackhpc/2024.1 with stackhpc/2023.1

.automation.conf/config.sh

@@ -3,7 +3,14 @@
 
 # See: https://github.com/stackhpc/docker-rally/blob/master/bin/rally-verify-wrapper.sh for a full list of tempest parameters that can be overriden.
 # You can override tempest parameters like so:
-export TEMPEST_CONCURRENCY=2
+
+# The Tempest concurrency determines how many tests can be running at once.
+# Higher values run tests faster but risk running out of resources and failing tests
+# On production systems, Tempest concurrency can usually be set to a high number e.g. 16-64. It is often limited by the number of available floating IPs.
+# On virtualised test environments, compute and networking speeds often limit the concurrency to 1-16 before tests begin to fail due to timeouts.
+export TEMPEST_CONCURRENCY=16
+
+
 # Specify single test whilst experimenting
 #export TEMPEST_PATTERN="${TEMPEST_PATTERN:-tempest.api.compute.servers.test_create_server.ServersTestJSON.test_host_name_is_same_as_server_name}"
 
@@ -21,9 +28,7 @@ if [ ! -z ${KAYOBE_ENVIRONMENT:+x} ]; then
   fi
 
   if [[ "$KAYOBE_ENVIRONMENT" =~ "ci-multinode" ]]; then
-    # SMSLab is currently running with 1G switches. This causes tests using volumes and images to fail if
-    # the concurrency is set too high.
-    export TEMPEST_CONCURRENCY=1
+    export TEMPEST_CONCURRENCY=4
     # Uncomment this to perform a full tempest test
     # export KAYOBE_AUTOMATION_TEMPEST_LOADLIST=tempest-full
     # export KAYOBE_AUTOMATION_TEMPEST_SKIPLIST=ci-multinode-tempest-full

.github/workflows/stackhpc-all-in-one.yml

@@ -443,7 +443,7 @@ jobs:
             -v $(pwd)/tempest-artifacts:/stack/tempest-artifacts \
             -e KAYOBE_ENVIRONMENT -e KAYOBE_VAULT_PASSWORD -e KAYOBE_AUTOMATION_SSH_PRIVATE_KEY \
             $KAYOBE_IMAGE \
-            /stack/kayobe-automation-env/src/kayobe-config/.automation/pipeline/tempest.sh -e ansible_user=stack -e rally_no_sensitive_log=false
+            /stack/kayobe-automation-env/src/kayobe-config/.automation/pipeline/tempest.sh -e ansible_user=stack
         env:
           KAYOBE_AUTOMATION_SSH_PRIVATE_KEY: ${{ steps.ssh_key.outputs.ssh_key }}
 

doc/source/contributor/environments/ci-aio.rst

@@ -10,10 +10,10 @@ automates the manual setup steps below, and is recommended for most users.
 The manual setup steps are provided for reference, and for users who wish to
 make changes to the setup process.
 
-.. warning::
+.. seealso::
 
-    This guide was written for the Yoga release and has not been validated for
-    Caracal. Proceed with caution.
+   All-in-one GitHub CI testing using this environment is described :ref:`here
+   <testing-ci-aio>`.
 
 Prerequisites
 =============

doc/source/contributor/environments/ci-builder.rst

@@ -16,6 +16,16 @@ In general it is preferable to use the `container image build CI workflow
 to build container images, but this manual approach may be useful in some
 cases.
 
+.. seealso::
+
+   A container image build GitHub Actions workflow using this environment is
+   described :ref:`here <testing-container-images>`.
+
+.. seealso::
+
+   An overcloud host image build GitHub Actions workflow using this environment
+   is described :ref:`here <testing-host-images>`.
+
 Prerequisites
 =============
 

doc/source/contributor/environments/ci-multinode.rst

@@ -19,6 +19,11 @@ beyond the defaults. This includes:
 * Magnum
 * Wazuh
 
+.. seealso::
+
+   On-demand and nightly GitHub Actions workflows workflow using this
+   environment are described :ref:`here <testing-multinode>`.
+
 Manila
 ======
 The Multinode environment supports Manila with the CephFS native backend, but it

doc/source/contributor/index.rst

@@ -13,3 +13,4 @@ This guide is for contributors of the StackHPC Kayobe configuration project.
    package-updates
    pre-commit
    ofed
+   testing-ci-automation