openstack
/
openstack-ansible
Code Issues Proposed changes
Ansible playbooks for deploying OpenStack.
1,439 Commits 8 Branches 119 Tags 133 MiB
Python 61.5%
Shell 26.7%
Jinja 11.7%
Smarty 0.1%
Go to file
Matt Thompson 092f606adc Update how neutron migrations are handled 
We're seeing some neutron db sync failures in master branch (liberty).
It looks like there may be a few issues with the way we're handling
migrations:

1. We're not capturing the correct information in the 'Check last DB
   revision' task as the first line returned by 'neutron-db-manage
   history' is a header (this also means that the 'Inspect on disk
   neutron DB revision' task will never do what we intend).
2. We delegate 'Check last DB revision' to 'neutron_all' group, but in
   an ideal world this is probably only necessary on 'neutron_server'.
3. When stopping neutron server to run 'Perform a Neutron DB Upgrade',
   we're only stopping it on groups['neutron_server'][0], while all
   other neutron server containers are up servicing requests.
4. Perform a db stamp, which doesn't appear to be necessary.

This change makes the following changes:

1. Bumps neutron SHA to include 43c00a9, which introduces new
   --expand / --contract upgrade options (otherwise, you have to
   specify liberty_expand@head / liberty_contract@head which may no
   longer work when neutron gets bumped in the future)
2. Checks if migrations have previously run, and if not runs a
   'neutron-db-manage upgrade heads'
3. If migrations have previously run:
   a) it runs an online migration against expand alembic branch using
      'neutron-db-manage upgrade --expand'.
   b) it stops all neutron-server services
   c) it runs an offline migration against contract alembic branch
      using 'neutron-db-manage upgrade --contract'
   d) it starts all neutron-server instances
4. It removes the temporary pin introduced in
   https://review.openstack.org/218572 as the SHA bump includes the
   upstream fix https://review.openstack.org/218723

TODO: Currently, we upgrade expand and contract branches (shutting down
      neutron-server in the proceses), even if there are no pending
      migrations.  We need to find a clean way to check what migration
      we are on and compare to alembic HEADS file to see if we're up to
      date.  Unfortunately, 'neutron-db-manage current' doesn't indicate
      which migration is in which alembic branch, so you would have to
      further grep for each migration in the neutron migrations code to
      determine the branch.

NOTE: Liberty introduces the split alembic branches for online/offline
      migrations, see [1] for more information.

[1] http://docs.openstack.org/developer/neutron/devref/alembic_migrations.html

Change-Id: I1176b5fe12cad1ee732486ae179e76deea5623e1
Closes-Bug: #1486593
 		2015-09-03 05:45:35 +00:00
doc Update documentation for multiple VLAN ranges 2015-08-21 16:42:24 +00:00
etc Enable HAProxy Stats Web UI 2015-08-24 21:23:43 +00:00
playbooks Update how neutron migrations are handled 2015-09-03 05:45:35 +00:00
scripts Disable python buffering for gate checks 2015-09-02 09:02:06 +00:00
.gitignore Uses tox for automating documentation builds 2015-08-12 06:32:40 +01:00
.gitreview Adds .gitreview file to repo 2014-12-02 17:22:12 -06:00
CONTRIBUTING.rst Updating CONTRIBUTING for commit messages 2015-04-06 10:38:40 -05:00
LICENSE.txt Convert existing roles into galaxy roles 2015-02-18 10:56:25 +00:00
README.rst Small readme fix 2015-08-12 21:57:20 +00:00
ansible-role-requirements.yml.example Convert existing roles into galaxy roles 2015-02-18 10:56:25 +00:00
dev-requirements.txt Adds a pep8 target to tox.ini 2015-08-14 11:42:26 +00:00
development-stack.rst development-stack Doc Update 2015-08-13 05:03:58 +00:00
requirements.txt Update how neutron migrations are handled 2015-09-03 05:45:35 +00:00
setup.cfg Uses tox for automating documentation builds 2015-08-12 06:32:40 +01:00
setup.py Uses tox for automating documentation builds 2015-08-12 06:32:40 +01:00
tox.ini Implement tox.ini config for bashate and pep8 tests 2015-09-02 13:45:01 +01: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:
  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/bootstrap-ansible.sh script, which will install, pip, ansible 1.9.x, all of the required python packages, and bring in any third party ansible roles that you may want to add to the deployment.
  2. Copy the etc/openstack_deploy directory to /etc/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.
  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.
  • 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