Stress Testing of existing cloud using Tempest
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
afazekas 7103432b92 Unit test logging 3 months ago
doc/source Update IRC network to OFTC 2 years ago
releasenotes/notes [ussuri][goal] Drop python 2.7 support and testing 3 years ago
tempest_stress Unit test logging 3 months ago
.gitignore Adding swap files in .gitignore 3 years ago
.gitreview OpenDev Migration Patch 4 years ago
.stestr.conf Switch tox env to stestr & add .gitreview file 4 years ago
.zuul.yaml Add non-voting Python 3.10 jobs for Zed cycle 9 months ago
AUTHORS add config files path options 6 years ago
CONTRIBUTING.rst [ussuri][goal] Update contributor documentation 3 years ago
ChangeLog add config files path options 6 years ago
HACKING.rst Use updated hacking url link 4 years ago
LICENSE Initial commit for stress framework from tempest 6 years ago Initial commit for stress framework from tempest 6 years ago
README.rst Cleanup py27 support 3 years ago
babel.cfg Initial commit for stress framework from tempest 6 years ago
bindep.txt Fix doc job 2 years ago
requirements.txt Multiple fix: now running 6 years ago
setup.cfg Test python3.9 as voting job 1 year ago Cleanup py27 support 3 years ago
test-requirements.txt Switch to newer openstackdocstheme version 3 years ago
tox.ini Use py3 as the default runtime for tox 2 years ago


Tempest Field Guide to Stress Tests

OpenStack is a distributed, asynchronous system that is prone to race condition bugs. These bugs will not be easily found during functional testing but will be encountered by users in large deployments in a way that is hard to debug. The stress test tries to cause these bugs to happen in a more controlled environment.

Stress tests are designed to stress an OpenStack environment by running a high workload against it and seeing what breaks. The stress test framework runs several test jobs in parallel and can run any existing test in Tempest as a stress job.


This particular framework assumes your working Nova cluster understands Nova API 2.0. The stress tests can read the logs from the cluster. To enable this you have to provide the hostname to call 'nova-manage' and the private key and user name for ssh to the cluster in the [stress] section of tempest.conf. You also need to provide the location of the log files:

  • target_logfiles = "regexp to all log files to be checked for errors"
  • target_private_key_path = "private ssh key for controller and log file nodes"
  • target_ssh_user = "username for controller and log file nodes"
  • target_controller = "hostname or ip of controller node (for nova-manage)
  • log_check_interval = "time between checking logs for errors (default 60s)"

To activate logging on your console please make sure that you activate use_stderr in tempest.conf or use the default logging.conf.sample file.

Running default stress test set


  1. You first need to clone this repo.:

    $ git clone
    $ cd  tempest_stress
  2. Install:

    $ python install
  3. Install Tempest


To Run stress tests, two configuration files are needed:

  1. tempest.conf - As per Tempest configuration guidelines here: configuration
  2. stress_tests.conf - same location as tempest.conf

later one is being used to define all config options specific to stress tests.


Run all tests:

$ run-tempest-stress -a -d 30

Run specific test:

$ run-tempest-stress -t ./tempest_stress/etc/server-create-destroy-test.json -d 30

This sample test tries to create a few VMs and kill a few VMs.

For more information please refer run-tempest-stress CLI help:

$ run-tempest-stress -h

Additional Tools

Sometimes the tests don't finish, or there are failures. In these cases, you may want to clean out the nova cluster. We have provided some scripts to do this in the tools subdirectory. You can use the following script to destroy any keypairs, floating ips, and servers: