shade

History

Monty Taylor 1fcc3e7aee Temporarily disable volume and os_image functional tests There is a config issue with the shade devstack cinder tests. We'll fix it post v3 rollout, but for now there are some other patches that need to progress. There is also a bug in upstream ansible that snuck in (yay for assymetric gating) A fix is in but hasn't been released yet. Change-Id: Ifacccecfeb112497b78feff908c0e681d6c012cf		2017-10-12 11:59:15 -05:00
..
hooks	Removes unnecessary utf-8 encoding	2017-01-11 16:42:25 +05:30
roles	Fix exception when using boot_from_volume for create_server	2017-05-13 15:50:55 -04:00
README.txt	Add ability to selectively run ansible tests	2015-11-12 15:59:45 -05:00
run.yml	Temporarily disable volume and os_image functional tests	2017-10-12 11:59:15 -05:00

README.txt

This directory contains a testing infrastructure for the Ansible
OpenStack modules. You will need a clouds.yaml file in order to run
the tests. You must provide a value for the `cloud` variable for each
run (using the -e option) as a default is not currently provided.

If you want to run these tests against devstack, it is easiest to use
the tox target. This assumes you have a devstack-admin cloud defined
in your clouds.yaml file that points to devstack. Some examples of
using tox:

    tox -e ansible

    tox -e ansible keypair security_group

If you want to run these tests directly, or against different clouds,
then you'll need to use the ansible-playbook command that comes with
the Ansible distribution and feed it the run.yml playbook. Some examples:

    # Run all module tests against a provider
    ansible-playbook run.yml -e "cloud=hp"

    # Run only the keypair and security_group tests
    ansible-playbook run.yml -e "cloud=hp" --tags "keypair,security_group"

    # Run all tests except security_group
    ansible-playbook run.yml -e "cloud=hp" --skip-tags "security_group"