Automatic Tempest Configuration Generator
40a5a97075
Usage section is there twice, it's because the README.rst is included in doc too and it contains usage section as well. The patch fixes that by not including the README.rst and copies the content of README.rst to the documentation, in order to have at least some, while documentation is being written or reviewed. Change-Id: I0247289029cd63b354965242ce7c1eca65f945eb Story: 2002703 Task: 22543 |
||
|---|---|---|
| config_tempest | ||
| doc | ||
| etc | ||
| playbooks | ||
| releasenotes | ||
| roles | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| HACKING.rst | ||
| LICENSE | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
python-tempestconf
Overview
python-tempestconf will automatically generate the tempest configuration based on your cloud.
- Free software: Apache license
- Documentation: http://git.openstack.org/cgit/openstack/python-tempestconf/tree/README.rst
- Source: https://git.openstack.org/openstack/python-tempestconf
- Bugs: https://storyboard.openstack.org/#!/project/912
- Release notes: https://docs.openstack.org/releasenotes/python-tempestconf
Usage
Git
- Clone and change to the directory:
$ git clone https://git.openstack.org/openstack/python-tempestconf
$ cd python-tempestconf- Create virtual environment using virtualenv:
$ virtualenv .venv
$ source .venv/bin/activate- Source the newly created virtual environment and install requirements:
(.venv) $ pip install -r requirements.txt
(.venv) $ pip install -r test-requirements.txt- Source cloud credentials, for example:
(py27) $ source cloudrc- 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 --createAfter this, ./etc/tempest.conf is generated.
RPM Installation (RDO)
- python-tempestconf is installed together with openstack-tempest, as a new dependency (starting from the Ocata release)
# yum install openstack-tempest- 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 --createNote
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>