Automatic Tempest Configuration Generator
Go to file
Prateek Arora d03fa08aba Add new parameter in place of deprecated one
The allow_tenant_isolation parameter has been replaced by
use_dynamic_credentials. As such added the parameter and removed
the old one. The default location from where tempest expects
to pick up the file containing credentials is also added
in the patch. The file location is only added when the file
is being used.

Change-Id: I2e2ec3bcc88570a55cf97bd4b74278970ffa0564
2017-05-15 03:44:26 -04:00
config_tempest Add new parameter in place of deprecated one 2017-05-15 03:44:26 -04:00
doc/source Merge "Start using reno for release notes" 2017-01-20 11:26:07 -05:00
etc Add support for admin parameters moving to auth 2017-05-05 06:59:48 -04:00
releasenotes Add new parameter in place of deprecated one 2017-05-15 03:44:26 -04:00
.coveragerc Initial Cookiecutter Commit. 2016-08-24 17:21:57 +02:00
.gitignore Add os-client-config support 2017-04-12 09:43:28 +02:00
.gitreview Add gerrithub to .gitreview 2016-12-12 11:00:41 +01:00
.mailmap Initial Cookiecutter Commit. 2016-08-24 17:21:57 +02:00
.testr.conf Initial Cookiecutter Commit. 2016-08-24 17:21:57 +02: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 Add os-client-config support 2017-04-12 09:43:28 +02:00
requirements.txt Add os-client-config support 2017-04-12 09:43:28 +02:00
setup.cfg Fixed discover-config-tempest to read default-overrides.conf from 2017-01-27 16:16:05 +05:30
setup.py Refactored python-tempestconf to work with devstack 2017-01-18 17:47:00 +05:30
test-requirements.txt Refactored python-tempestconf to work with devstack 2017-01-18 17:47:00 +05:30
tox.ini Add unit tests 2017-02-07 11:20:40 +00:00

README.rst

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://github.com/redhat-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 -y 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>