From da02f4de19db7b4e79deec7c70e993063c3ec3ec Mon Sep 17 00:00:00 2001 From: Alex-Welsh Date: Fri, 27 Sep 2024 10:12:08 +0100 Subject: [PATCH] Add note on Tempest concurrency, increase defaults --- .automation.conf/config.sh | 13 +++++++++---- .../notes/tempest-concurrency-1c86c0ef90e104f6.yaml | 5 +++++ 2 files changed, 14 insertions(+), 4 deletions(-) create mode 100644 releasenotes/notes/tempest-concurrency-1c86c0ef90e104f6.yaml diff --git a/.automation.conf/config.sh b/.automation.conf/config.sh index 84b11dd07..76f2a59a0 100644 --- a/.automation.conf/config.sh +++ b/.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 diff --git a/releasenotes/notes/tempest-concurrency-1c86c0ef90e104f6.yaml b/releasenotes/notes/tempest-concurrency-1c86c0ef90e104f6.yaml new file mode 100644 index 000000000..db9658694 --- /dev/null +++ b/releasenotes/notes/tempest-concurrency-1c86c0ef90e104f6.yaml @@ -0,0 +1,5 @@ +--- +features: + - | + The default Tempest concurrency has been increased from 2 to 16. + This is often easily achievable in production systems.