Ansible role to deploy multiple clouds resources
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
OpenDev Sysadmins 60e701bb38 OpenDev Migration Patch 1 month ago
defaults Add ability to download an image from the Internet to upload it to Glance 2 years ago
doc/source Add doc folder 3 years ago
meta Add metadata to role 3 years ago
tasks Merge "Add region to task output" 7 months ago
tests Add quotas support for the cloud launcher 2 years ago
.gitignore Add .gitignore 3 years ago
.gitreview OpenDev Migration Patch 1 month ago
LICENSE Add Apache license file 3 years ago
README.rst Switch README from markdown to rst 3 years ago
requirements.txt Pin Ansible version to 2.1.2.0 2 years ago
resources.yml.sample Initial support for regions 2 years ago
setup.cfg Add setup.py and setup.cfg 3 years ago
setup.py Add setup.py and setup.cfg 3 years ago
test-requirements.txt Add test-requirements.txt for tox venvs 3 years ago
tox.ini Run cloud launcher with latest release candidate 2 years ago

README.rst

ansible-role-cloud-launcher

Ansible role to launch multiple OpenStack Clouds resources

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