Go to file

Andy McCrae de8b857668 Add swift-sync role and environment

Add the swift-remote host group and environment file.

Add an os_swift_sync role which will sync the swift ring and ssh keys
for swift hosts (remote and not-remote). Which has the following:
 * Moves the key and ring tasks out of os_swift role to os_swift_sync.
 * This adds the use of the "-r" flag that was added to the
   swift_rings.py and swift_rings_check.py.
 * Adds a ring.builder vs contents file consistency check.
 * Adjusts the rsync process to use the built-in synchronize module
 * Ensure services have started post ring/ssh key sync.

Adds environment file and sample configuration file for swift-remote
hosts (conf.d).

Move appropriate default vars to the os_swift_sync role, and remove them
from the os_swift role.

Rename the "os-swift-install.yml" playbook to "os-swift-setup.yml" as
this handles only the setup, and add a playbook to for both
os-swift-sync.yml and an overarching playbook (os-swift-install.yml)
that will call both the os-swift-sync.yml and os-swift-setup.yml
playbooks. This means the funcitonality of "os-swift-install.yml"
remains unchanged.

Adjust the run-playbooks.sh so that it calls the new overarching swift
playbook.

Change-Id: Ie2d8041b4bc46f092a96882fe3ca430be92195ed
Partially-Implements: blueprint multi-region-swift

2015-08-07 08:45:18 +00:00

doc

Merge "Implement Ceilometer"

2015-07-09 17:50:10 +00:00

etc

Add swift-sync role and environment

2015-08-07 08:45:18 +00:00

playbooks

Add swift-sync role and environment

2015-08-07 08:45:18 +00:00

scripts

Merge "Change ansible forks used"

2015-08-03 17:59:49 +00:00

.gitignore

Updated master to the latest SHAs - 22.06.2015

2015-06-24 15:50:42 +00:00

.gitreview

Adds .gitreview file to repo

2014-12-02 17:22:12 -06:00

ansible-role-requirements.yml.example

Convert existing roles into galaxy roles

2015-02-18 10:56:25 +00:00

CONTRIBUTING.rst

Updating CONTRIBUTING for commit messages

2015-04-06 10:38:40 -05:00

dev-requirements.txt

Port basic installation guide

2015-06-11 09:17:56 -05:00

development-stack.rst

fix bash/curl command in development-stack.rst

2015-05-27 11:21:27 +01:00

LICENSE.txt

Convert existing roles into galaxy roles

2015-02-18 10:56:25 +00:00

README.rst

Set permissions on user_secrets.yml to 0600

2015-06-11 20:39:46 +00:00

requirements.txt

Update the tempest install environment

2015-05-06 07:46:39 -05:00

README.rst

OpenStack Ansible Deployment

date: 2015-02-02 22:00
tags: lxc, openstack, cloud, ansible
category: *nix

Playbooks

There are several playbooks within that will setup hosts for use in OpenStack Cloud. The playbooks will enable LXC on hosts and provides the ability to deploy LXC containers for use within openstack.

Plays:

setup-hosts.yml Performs host setup for use with LXC in the OpenStack hosts.
setup-infrastructure.yml Performs all of the setup for all infrastructure components.
setup-openstack.yml Performs all of the setup for all of the OpenStack components.

If you dont want to run plays individually you can simply run setup-everything.yml which will perform all of the setup and installation for you.

Basic Setup:

If you have any roles that you'd like to have pulled in that are outside the scope and or replace modules within this repository please add them to the ansible-role-requirements.yml file. In this file you will want to fill in the details for the role you want to pull in using standard ansible galaxy format.

- name: SuperAwesomeModule
  src: https://github.com/super-user/SuperAwesomeModule
  version: master

Run the ./scripts/bootstrap-ansible.sh script, which will install, pip, ansible 1.9.x, all of the required python packages, and bring in any third part ansible roles that you may want to add to the deployment.
Copy the etc/openstack_deploy directory to /etc/openstack_deploy.
Fill in your openstack_deploy/openstack_user_config.yml, openstack_deploy/user_secrets.yml and openstack_deploy/user_variables.yml files which you've just copied to your /etc/ directory.
Generate all of your random passwords executing scripts/pw-token-gen.py --file /etc/openstack_deploy/user_secrets.yml.
Accomplish all of the host networking that you want to use within the deployment. See the etc/network directory in this repository for an example network setup.
When ready change to the playbooks/ directory and execute your desired plays. IE:

openstack-ansible setup-everything.yml

Notes

If you run the ./scripts/bootstrap-ansible.sh script a wrapper script will be added to your system that wraps the ansible-playbook command to simplify the arguments required to run openstack ansible plays. The name of the wrapper script is openstack-ansible.
The lxc network is created within the lxcbr0 interface. This supports both NAT networks as well as more traditional networking. If NAT is enabled (default) the IPtables rules will be created along with the interface as a post-up processes. If you ever need to recreate the rules and or restart the dnsmask process you can bounce the interface IE: ifdown lxcb0; ifup lxcbr0 or you can use the lxc-system-manage command.
The tool lxc-system-manage is available on all lxc hosts and can assist in recreating parts of the LXC system whenever its needed.
Inventory is generated by executing the playbooks/inventory/dynamic_inventory.py script. This is configured in the playbooks/ansible.cfg file.
If you don't use the pw-token-gen.py script you will want to ensure the permissions on /etc/openstack_deploy/user_secrets.yml are more secure. chmod 0600 /etc/openstack_deploy/user_secrets.yml

Bugs and Blueprints

Everything we do is in launchpad and gerrit. If you'd like to raise a bug, feature request, or are looking for ways to contribute please go to "https://launchpad.net/openstack-ansible".

Documentation

To build the docs make sure that you have installed the python requirements as found within the dev-requirements.txt file and then run the following command from within the doc directory.

make html