Red Hat Training

A Red Hat training course is available for Red Hat OpenStack Platform

Chapter 4. Configuring the OpenStack Integration Test Suite

4.1. Creating a Workspace

  1. Source the admin credentials:

    In the undercloud:

    # source stackrc

    Or in the overcloud:

    # source overcloudrc
  2. Initialize tempest:

    # tempest init mytempest
    # cd mytempest

    This creates a tempest workspace named mytempest.

    You can view a list of existing workspaces:

    # tempest workspace list
  3. Generate the etc/tempest.conf file:

    # discover-tempest-config --deployer-input ~/tempest-deployer-input.conf \
    --debug --create identity.uri $OS_AUTH_URL identity.admin_password \
    $OS_PASSWORD --network-id <UUID>

    uuid is the UUID of the external network.

    discover-tempest-config was formerly called and takes the same parameters. It is provided by python-tempestconf which is installed as a dependency of openstack-tempest.

4.2. Verifying Your Tempest Configuration

Verify your current tempest configuration:

# tempest verify-config -o <output>

output is the output file where your updated configuration is written. This is different from your original configuration file.

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 tempest.conf, under the [DEFAULT] section, set log_dir to the desired directory:

log_dir = <directory>

If you have your own logging configuration file, in tempest.conf, under the [DEFAULT] section, set log_config_append to your file:

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:

min_microversion = 2.14
max_microversion = latest