openstack
/
tempest
Code Issues Proposed changes
OpenStack Testing (Tempest) of an existing cloud
500 Commits 1 Branch 47 Tags 240 MiB
Python 99.8%
Shell 0.2%
Go to file
Dan Prince 8527c8a168 RestClient: Don't hard code volume service name. 
Updates the common/rest_client keystone_auth function so that
it doesn't hard code the 'service_name' for the volume service.

The motivation here is to allow Tempest to run in more environments
where the volume service name may not always be 'cinder'.

Change-Id: I3b892781929642fd42a3dd3b4ba8d44486bfe275
 		2012-12-14 14:00:31 -05:00
bin Start making setup.py similar to other OpenStack Projects 2012-12-05 19:51:26 +01:00
etc Merge "Add num_retries configuration option" 2012-12-14 10:22:09 +00:00
include Updating images tests 2011-10-31 15:23:19 -04:00
stress Fix pep8 violations in stress tests 2012-12-10 10:10:32 -05:00
tempest RestClient: Don't hard code volume service name. 2012-12-14 14:00:31 -05:00
tools Adds paramiko to pip-requires 2012-12-12 23:47:47 -05:00
.gitignore Start making setup.py similar to other OpenStack Projects 2012-12-05 19:51:26 +01:00
.gitreview Update .gitreview with new project name. 2011-11-30 10:59:36 -08:00
HACKING.rst Improve pep8 checks to be similar to those in nova 2012-12-12 11:49:30 -05:00
LICENSE Add License to Tempest. 2012-04-12 16:04:36 +02:00
README.rst fix for Bug1078481 2012-11-20 00:09:43 +00:00
run_tests.sh Improve pep8 checks to be similar to those in nova 2012-12-12 11:49:30 -05:00
setup.cfg Refactor Tempest to be parallel-test friendly 2012-07-02 11:05:21 -04:00
setup.py Start making setup.py similar to other OpenStack Projects 2012-12-05 19:51:26 +01:00
tox.ini Improve pep8 checks to be similar to those in nova 2012-12-12 11:49:30 -05:00

README.rst

:

Tempest - The OpenStack Integration Test Suite

This is a set of integration tests to be run against a live cluster.

Quickstart

To run Tempest, you first need to create a configuration file that will tell Tempest where to find the various OpenStack services and other testing behavior switches.

The easiest way to create a configuration file is to copy the sample one in the etc/ directory :

$> cd $TEMPEST_ROOT_DIR
$> cp etc/tempest.conf.sample etc/tempest.conf

After that, open up the etc/tempest.conf file and edit the configuration variables to match valid data in your environment. This includes your Keystone endpoint, a valid user and credentials, and reference data to be used in testing.

Note

If you have a running devstack environment, look at the environment variables in your devstack/localrc file. The ADMIN_PASSWORD variable should match the api_key value in the tempest.conf [nova] configuration section. In addition, you will need to get the UUID identifier of the image that devstack uploaded and set the image_ref value in the [environment] section in the tempest.conf to that image UUID.

In addition, the <devstack-repo>/tools/configure_tempest.sh script can also be used to generate a tempest.conf based on your devstack's rc files. TEMPEST_DIR variable points to location /opt/stack/temptest. Update this variable if the location is different..

Tempest is not tied to any single test runner, but Nose been the most commonly used tool. After setting up your configuration file, you can execute the set of Tempest tests by using nosetests :: $> nosetests tempest

To run one single test ::
$> nosetests -sv tempest.tests.compute.servers.test_server_actions.py:

ServerActionsTestJSON.test_rebuild_nonexistent_server

Configuration

At present, there are three sections to be configured: nova, environment, and image. The nova section includes information about your Keystone endpoint, as well as valid credentials for a user. It also contains logical timeouts for certain actions. The environment section contains reference data to be used when testing the Compute portion of OpenStack, as well as feature flags for tests that may or may not work based on your hypervisor or current environment. Lastly, the image section contains credentials and endpoints for the Glance image service.

Common Issues

Tempest was originally designed to primarily run against a full OpenStack deployment. Due to that focus, some issues may occur when running Tempest against devstack.

Running Tempest, especially in parallel, against a devstack instance may cause requests to be rate limited, which will cause unexpected failures. Given the number of requests Tempest can make against a cluster, rate limiting should be disabled for all test accounts.

Additionally, devstack only provides a single image which Nova can use. For the moment, the best solution is to provide the same image uuid for both image_ref and image_ref_alt. Tempest will skip tests as needed if it detects that both images are the same.