OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have.
|2 months ago|
|defaults||2 years ago|
|doc/source||3 years ago|
|meta||3 years ago|
|tasks||7 months ago|
|tests||2 years ago|
|.gitignore||3 years ago|
|.gitreview||2 months ago|
|LICENSE||3 years ago|
|README.rst||3 years ago|
|requirements.txt||2 years ago|
|resources.yml.sample||2 years ago|
|setup.cfg||3 years ago|
|setup.py||3 years ago|
|test-requirements.txt||3 years ago|
|tox.ini||2 years ago|
Ansible role to launch multiple OpenStack Clouds resources
ansible-role-cloud-launcher is an Ansible role that allows to launch multiple OpenStack clouds resources. Resources can be defined in a cloud by cloud basis or defined in a profile, which may be reused by more than one cloud.
shade library needs to be installed, as that is required by the OpenStack Ansible modules.
The role expects variables fed by ansible-playbook on the CLI, for example:
ansible-playbook -i inventory play.yml -e "@resources.yml"
The role expects the resources variables file to have two dict variables, profiles and clouds.
profiles contains a list of OpenStack resources definitions that are meant to be reused by one or more clouds.
clouds contains a list of clouds the role will launch resources on. Each cloud definition will have the OSCC cloud name, a list of profiles the cloud will reuse and a list of resources specific to that cloud.
Please check resources.yml.sample on this repository for a full-blown example.