The OpenStack-Ansible project provides tools for deploying OpenStack from source using Ansible. It aims to deploy all core OpenStack services in an integrated and tested way. Recent releases have removed proprietary code and support multiple operating systems. Upcoming work includes splitting roles into reusable components, improved testing and security, and supporting additional OpenStack features like Neutron DVR.
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
OpenStack-Ansible Project Update
1. OpenStack-Ansible Project Update
Make your notes here:
https://etherpad.openstack.org/p/MAN-ops-Openstack-Ansible
OpenStack Operators Mid Cycle
15 Feb 2016
2. A brief history
• Initially developed to deploy Icehouse (v9) for Rackspace Private
Cloud.
• Kilo (v11) release on 30 April 2015
– Included the removal of all Rackspace specifics.
– Switched to the Ansible Galaxy role style of development.
• Became an official OpenStack Big Tent project 23 June 2015.
• Now used in production by multiple public and private cloud
deployments.
4. Project Release Cycle
• Major releases align with OpenStack release cycle
– Master branch follows OpenStackmaster branches.
– Named branch (eg: Liberty) follow OpenStackstable branches.
• Patch releases are scheduled every two weeks
– Includes OpenStack/RabbitMQpatch updates which have been the
basis of testing for the previous two weeks.
5. Liberty Release
• Package and deploy OpenStack services into python venvs
• MariaDB v10
– Part of multi-OS support critical path
• Neutron Linuxbridge ML2 Configuration & PLUMgrid Support
• Tunable OpenStack Configuration
– ini (all .conf files), yml (Ceilometer), json (Policy files)
– You can do almost any configuration in OpenStackthrough user-space
configuration in OpenStack-Ansible.
• Ability to use a Ceph to back Glance & Cinder
• Tested in OSIC with 3 Control Plane Hosts & 500+ Compute Hosts
6. Current capabilities you may not be aware of
• You can deploy without LXC containers
– Adjust the env.d files to turn ‘is_metal’ to True and no containers will be
deployed.
• You can choose your architecture
– Where stuff is deployed is decided based on host group membership.
– Neutron network design is entirely flexible.
• You can add additional packages to the deployment repo
– This is useful for adding drivers to Cinder/Neutron.
– Combine with tunable configurations and almost any configuration is
possible.
7. Current capabilities you may not be aware of
• It’s possible to use a proxy server, and almost possible to do the
whole installation offline.
– Work is ongoing to allow completely offline installs from the repo server.
• The Ansible roles are reusable
– You can do your own playbooks, use a different style of inventory, etc.
• If you want to add additional Ansible roles, you can
– ansible-role-requirements.yml
9. Get Involved
• Launchpad Landing Page
– https://launchpad.net/openstack-ansible
• Documentation
– http://docs.openstack.org/developer/openstack-ansible
– http://docs.openstack.org/developer/openstack-ansible/developer-
docs/quickstart-aio.html
• Attend community meetings
– https://wiki.openstack.org/wiki/Meetings/openstack-ansible
• Get help
– Mailing Lists: [openstack-ansible] in subject line
– IRC: #openstack-ansible in Freenode
10. What would you like to see us do in the
Newton development cycle?
• Tell us now
– https://etherpad.openstack.org/p/MAN-ops-Openstack-Ansible
• Attend community meetings
– https://wiki.openstack.org/wiki/Meetings/openstack-ansible
• Or join us on IRC
– #openstack-ansible in Freenode
• Email the OpenStack-Dev Mailing List
– Use ‘[openstack-ansible][enhancement-request]’ in the subject line