Automatic Tempest Configuration Generator
Go to file
Emilien Macchi 6d2c9941b4 Switch endpoint_type to publicURL
We were using adminURL to talk to Keystone API but in most cases, we run Tempest
from outside of admin network for security reasons. We now use public URL, so the
public network, which is what we expect our cloud users to do.

Change-Id: Iefcca23dc7593148cfa836d588d484cac0707851
2017-11-23 23:25:05 +00:00
config_tempest Switch endpoint_type to publicURL 2017-11-23 23:25:05 +00:00
doc/source Merge "Start using reno for release notes" 2017-01-20 11:26:07 -05:00
etc Merge "Add support for admin parameters moving to auth" 2017-05-05 08:18:07 -04:00
releasenotes Switch endpoint_type to publicURL 2017-11-23 23:25:05 +00: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 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
.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 Updated README with updated links 2017-10-16 16:15:48 +05:30
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

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 -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>