66aa6dcd6a
Since pulling Ansible 2.1.1.0, the role fails with 'item_cloud not defined' when processing the per-cloud resources. I believe the issue is due to: https://github.com/ansible/ansible/issues/17148 Pinning to previous version for now till the issue is fixed. Change-Id: Ia7275f6bcc308dd0a0509744711c37451546026b |
||
---|---|---|
defaults | ||
doc/source | ||
meta | ||
tasks | ||
tests | ||
.gitignore | ||
.gitreview | ||
LICENSE | ||
README.rst | ||
requirements.txt | ||
resources.yml.sample | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
ansible-role-cloud-launcher
Ansible role to launch multiple OpenStack Clouds resources
- License: Apache License, Version 2.0
- Documentation: https://ansible-role-cloud-launcher.readthedocs.org
- Source: https://git.openstack.org/cgit/openstack/ansible-role-cloud-launcher
- Bugs: https://bugs.launchpad.net/ansible-role-cloud-launcher
Description
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.
Requirements
shade library needs to be installed, as that is required by the OpenStack Ansible modules.
Role Variables
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.
Dependencies
None
Example playbook
---
- hosts: localhost
connection: local
gather_facts: false
roles:
- { role: ansible-role-cloud-launcher }