Ansible playbooks for deploying OpenStack.
Go to file
Kevin Carter 5b4eee1fc1 Adds rsyslog client role and enables it in all plays
This commit adds the rsyslog_client role to the general stack. This
change is part 3 of 3 role will allow rsyslog to server as a log
shipper within a given host / container. The role has been setup to
allow for logs to be shipped to multiple hosts and or other
providers, e.g. splunk, loggly, etc... All of the plays that need
to support logging have been modified to use the new rsyslog_client
role.

Roles added:
* rsyslog_client

Plays modified:
* playbooks/galera-install.yml
* playbooks/lxc-hosts-setup.yml
* playbooks/os-cinder-install.yml
* playbooks/os-glance-install.yml
* playbooks/os-heat-install.yml
* playbooks/os-horizon-install.yml
* playbooks/os-keystone-install.yml
* playbooks/os-neutron-install.yml
* playbooks/os-nova-install.yml
* playbooks/os-swift-install.yml
* playbooks/os-tempest-install.yml
* playbooks/rabbitmq-install.yml
* playbooks/repo-server.yml

DocImpact
Implements: blueprint rsyslog-update

Change-Id: I4028a58db3825adb8a5aa73dbaabbe353bb33046
2015-03-17 13:52:30 -05:00
etc Removed all rackspace related logging parts 2015-03-14 22:35:59 -05:00
playbooks Adds rsyslog client role and enables it in all plays 2015-03-17 13:52:30 -05:00
rpc_deployment Convert existing roles into galaxy roles 2015-02-18 10:56:25 +00:00
scripts Removed all rackspace related logging parts 2015-03-14 22:35:59 -05:00
.gitignore Initial Commit 2014-08-26 18:08:15 -05: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 Updated contributing guidelines 2015-02-24 12:18:45 -06:00
dev-requirements.txt Convert existing roles into galaxy roles 2015-02-18 10:56:25 +00:00
development-stack.rst Removed all rackspace related logging parts 2015-03-14 22:35:59 -05:00
LICENSE.txt Convert existing roles into galaxy roles 2015-02-18 10:56:25 +00:00
README.rst Convert existing roles into galaxy roles 2015-02-18 10:56:25 +00:00
requirements.txt Convert existing roles into galaxy roles 2015-02-18 10:56:25 +00:00

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:
  1. 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
  1. Run the ./scripts/os-ansible-bootstrap.sh script, which will install, pip, ansible 1.8.x, all of the required python packages, and bring in any third part ansible roles that you may want to add to the deployment.
  2. Copy the etc/openstack_deploy directory to /etc/openstack_deploy or if you are executing all of this as an unprivileged user you can add the openstack_deploy bits into your home directory as ${HOME}/.openstack_deploy.
  3. 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 or your ${HOME} folder.
  4. Generate all of your random passwords executing scripts/pw-token-gen.py --file /etc/openstack_deploy/user_secrets.yml.
  5. 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.
  6. 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.
  • Our repository uses a custom LXC module which adds lxc: support to Ansible. The module within this repository is presently pending in upstream ansible at "https://github.com/ansible/ansible-modules-extras/pull/123".
  • Inventory is generated by executing the playbooks/inventory/dynamic_inventory.py script. This is configured in the playbooks/ansible.cfg file.

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".

Official Documentation

Comprehensive installation guides, including FAQs and release notes, can be found at "http://docs.rackspace.com/rpc/api/v9/bk-rpc-installation/content/rpc-common-front.html" < Note that these docs may not be up-to-date with the current release of this repository however they are still a good source of documentation.