OpenStack Testing (Tempest) of an existing cloud
Go to file
Sean Dague 6dbc6da416 add scenario directory
this adds the scenario directory as part of the tempest
restructure, and moves scenario tests over to the new directory.

To ensure we got everything that used the old DefaultClient and
DefaultManager classes these are refactored out into the scenario
directory as OfficialClient and OfficialClientManager.

The Nework Smoke test base class becomes NetworkScenarioTest, and
the two test files that used that come over to scenario directory
in the process.

These are all done with a single tempest/scenario/manager.py file
for now. As the scenario tests grow we'll figure out better
refactorings there.

This gives us 4 scenario test files as a starting point for future
scenario work.

Fixed remaining refactor issues with network tests

Clean up the documentation on the extracted classes

Part of bp:tempest-repo-restructure

Change-Id: I143b282c58cfac3bf979ba5ac68226155beff343
2013-05-17 08:52:22 -04:00
bin Start making setup.py similar to other OpenStack Projects 2012-12-05 19:51:26 +01:00
etc A Heat client which does basic stack operations. 2013-05-15 12:55:38 +12:00
include Updating images tests 2011-10-31 15:23:19 -04:00
tempest add scenario directory 2013-05-17 08:52:22 -04:00
tools Create Flake8 extension for tempest checks 2013-05-16 16:32:36 -04:00
.gitignore Ignore .testrepository/ 2013-05-07 09:13:02 +12:00
.gitreview Update .gitreview with new project name. 2011-11-30 10:59:36 -08:00
.mailmap Update gitignore because of oslo setup.py 2013-01-09 10:54:17 -05:00
.testr.conf Add support for testrepository 2013-02-08 11:18:26 +10:30
HACKING.rst Update hacking.py for @testtools.skip() formatting. 2013-03-22 15:40:59 -04:00
LICENSE Add License to Tempest. 2012-04-12 16:04:36 +02:00
README.rst Remove reference to dead script configure_tempest.sh 2013-05-03 14:13:15 -04:00
openstack-common.conf Migrate to pbr from openstack.common.setup. 2013-05-01 14:04:27 -04:00
run_tests.sh Finish up flake8 conversion. 2013-05-01 14:04:07 -04:00
setup.cfg Migrate to pbr from openstack.common.setup. 2013-05-01 14:04:27 -04:00
setup.py Migrate to pbr from openstack.common.setup. 2013-05-01 14:04:27 -04:00
tox.ini add scenario directory 2013-05-17 08:52:22 -04: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.

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.