Automatic Tempest Configuration Generator
Go to file
Chandan Kumar 187471e3fd Use identity api_v3 default value from tempest
* Since from Queens cycle, api_v3 is set to true and the openstack
  catalog list for identity does not provides the version and extension
  info. So better we can use the default value from tempest.config
  otherwise it will set api_v3 to false.

Change-Id: Ic02310262f46bb011dac20eaa28f85f224df4e76
2018-02-14 20:09:42 +05:30
config_tempest Use identity api_v3 default value from tempest 2018-02-14 20:09:42 +05:30
doc Add support for new doc PTI jobs 2018-01-05 16:31:34 +05:30
etc Merge "Add support for admin parameters moving to auth" 2017-05-05 08:18:07 -04:00
playbooks zuul: fix the parent of the packstack jobs, concurrency 2018-02-12 16:22:44 +01:00
releasenotes Switch endpoint_type to publicURL 2017-11-23 23:25:05 +00:00
roles Change attribute of zuul projects 2018-02-05 01:49:37 +00:00
.coveragerc Initial Cookiecutter Commit. 2016-08-24 17:21:57 +02:00
.gitignore Switch to use stestr for unit tests 2017-12-05 10:06:13 +00:00
.gitreview Update .gitreview: point to review.openstack.org 2017-10-11 11:32:40 +02:00
.mailmap Initial Cookiecutter Commit. 2016-08-24 17:21:57 +02:00
.stestr.conf Switch to use stestr for unit tests 2017-12-05 10:06:13 +00:00
.zuul.yaml Merge "Fixed {test,-}.requirements.txt" 2018-02-13 21:45:51 +00:00
HACKING.rst Refactored python-tempestconf to work with devstack 2017-01-18 17:47:00 +05:30
LICENSE Initial Cookiecutter Commit. 2016-08-24 17:21:57 +02:00
README.rst Do not use “-y” for package install 2018-01-02 16:33:37 +07:00
requirements.txt Fixed {test,-}.requirements.txt 2018-02-13 10:23:18 +00:00
setup.cfg Cleaned setup.cfg for OpenStack release 2018-01-29 15:35:45 +05:30
setup.py Refactored python-tempestconf to work with devstack 2017-01-18 17:47:00 +05:30
test-requirements.txt Fixed {test,-}.requirements.txt 2018-02-13 10:23:18 +00:00
tox.ini Add support for new doc PTI jobs 2018-01-05 16:31:34 +05:30

python-tempestconf

Overview

python-tempestconf will automatically generate the tempest configuration based on your cloud.

Usage

Git

  1. Clone and change to the directory:
$ git clone https://git.openstack.org/openstack/python-tempestconf
$ cd python-tempestconf
  1. Create virtual environment using virtualenv:
$ virtualenv .venv
$ source .venv/bin/activate
  1. Source the newly created virtual environment and install requirements:
(.venv) $ pip install -r requirements.txt
(.venv) $ pip install -r test-requirements.txt
  1. Source cloud credentials, for example:
(py27) $ source cloudrc
  1. Run python-tempestconf to generate tempest configuration file:
(py27) $ python config_tempest/config_tempest.py --debug identity.uri $OS_AUTH_URL \
            identity.admin_password  $OS_PASSWORD --create

After this, ./etc/tempest.conf is generated.

RPM Installation (RDO)

  1. python-tempestconf is installed together with openstack-tempest, as a new dependency (starting from the Ocata release)
# yum install openstack-tempest
  1. Source cloud credentials, initialize tempest and run the discovery tool:
$ source cloudrc
$ tempest init testingdir
$ cd testingdir
$ discover-tempest-config --debug identity.uri $OS_AUTH_URL \
      identity.admin_password  $OS_PASSWORD --create

Note

In Ocata release new features were presented. discover-tempest-config is the new name of the old config_tempest.py script and it accepts the same parameters. More about new features can be found here

os-client-config support

python-tempestconf supports os-client-config so instead of sourcing openstackrc files you can use clouds.yml files. Location where these files should be stored and syntax which is used to specify cloud.yaml files can be found here

In case of git usage:

(py27) $ python config_tempest/config_tempest.py --debug --create --os-cloud <name of cloud>

In case of RPM:

$ tempest init testingdir
$ cd testingdir
$ discover-tempest-config --debug --create --os-cloud <name of cloud>