Chapter 4. Configuring the OpenStack Integration Test Suite
4.1. Creating a Workspace
Source the admin credentials:
In the undercloud:
$ source stackrc
Or in the overcloud:
$ source overcloudrc
Initialize tempest:
$ cd ~ $ mkdir mytempest $ cd mytempest $ /usr/share/openstack-tempest-13.0.0/tools/configure-tempest-directory
This creates a tempest workspace named
mytempestfor your user account.Generate the
etc/tempest.conffile:$ python tools/config_tempest.py --deployer-input ~/tempest-deployer-input.conf --debug --create identity.uri $OS_AUTH_URL identity.admin_password $OS_PASSWORD --network-id _<uuid>_
uuidis the UUID of the external network.NoteFor offline systems, you can specify an existing glance image by adding the
--imageparameter. For example:--image cirros-0.3.4-x86_64-disk.img
You can view a list of existing workspaces:
$ tempest workspace list
4.2. Verifying Your Tempest Configuration
Generate the
.testr.confin your tempest workspace:$ testr init
Verify your current tempest configuration, specifying the tempest.conf file that was just generated:
$ tempest verify-config -o ~/mytempest/etc/tempest.conf
4.3. Changing the Logging Configuration
The default location for log files is the logs directory within your tempest workspace.
To change this directory, in
~/mytempest/etc/tempest.conf, under the[DEFAULT]section, setlog_dirto the desired directory:[DEFAULT] log_dir = _<directory>_
If you have your own logging configuration file, in
~/mytempest/etc/tempest.conf, under the[DEFAULT]section, setlog_config_appendto your file:[DEFAULT] log_config_append = _<file>_
If this is set, all other logging configuration in tempest.conf will be ignored, including log_dir.
4.4. Configuring Microversion Tests
The OpenStack Integration Test Suite provides stable interfaces to test the API microversions. This section describes how to implement microversion tests using these interfaces. You first need to configure options in the tempest.conf configuration file to specify the target microversions. This is to make sure that the supported microversions match the microversions used in the OpenStack cloud. You can run multiple microversion tests in a single Integration Test Suite operation by specifying a range of target microversions.
For example, to limit the range of microversions for the compute service, in the [compute] section of your configuration file, assign values to the min_microversion and max_microversion parameters:
[compute] min_microversion = 2.14 max_microversion = latest
