d410903ea6
* let's the tool handle it itself. * generate-tempestconf-file role uses url_cirros_image in test-demo-user.yaml so it cannot be removed. Change-Id: Iae526d807f7438148e39747634e1f190879fb4ce
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
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>