此内容没有您所选择的语言版本。

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:

    $ cd ~
    $ mkdir mytempest
    $ cd mytempest
    $ /usr/share/openstack-tempest-13.0.0/tools/configure-tempest-directory

    This creates a tempest workspace named mytempest for your user account.

  3. Generate the etc/tempest.conf file:

    $ 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>_
    • uuid is the UUID of the external network.

      Note

      For offline systems, you can specify an existing glance image by adding the --image parameter. For example: --image cirros-0.3.4-x86_64-disk.img

  4. You can view a list of existing workspaces:

    $ tempest workspace list

4.2. Verifying Your Tempest Configuration

  1. Generate the .testr.conf in your tempest workspace:

    $ testr init
  2. 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, set log_dir to the desired directory:

    [DEFAULT]
    log_dir = _<directory>_
  • If you have your own logging configuration file, in ~/mytempest/etc/tempest.conf, under the [DEFAULT] section, set log_config_append to your file:

    [DEFAULT]
    log_config_append = _<file>_
Note

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
Red Hat logoGithubRedditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

© 2024 Red Hat, Inc.