7f2ae4f105
If HAproxy binding is enabled for RabbitMQ service, we need to ensure queres are replicated and this is done by a specific policy. Since OpenStack is already tagging queues with rabbit_ha_queues=True parameter everywhere, we just create the policy and the queues by themselves. This is enabled only if HAproxy binding is enabled for now, because the feature seems required when using RabbitMQ load-balancing. The other use-case (when using Oslo messaging to failover to another RabbitMQ node) does not require this policy. If a node is down, OpenStack will fallback to another RabbitMQ node in the list from parameters. This patch allows you to configure 'exactly' or 'all' RabbitMQ HA policy modes. Why using 'exactly' mode ? To let operators scale up/down the replication accross an exact number of nodes. How it works ? Queue is mirrored to count nodes in the cluster. If there are less than count nodes in the cluster, the queue is mirrored to all nodes. If there are more than count nodes in the cluster, and a node containing a mirror goes down, then a new mirror will be created on another node. Also change the Puppetfile to have latest commits in puppetlabs-rabbitmq to have some fix related to rabbitmq_policy provider. Without this fix, some parameters are not integers but string, and we need integer. Closes-bug #1434474 Change-Id: I3f732360f83e10e0ae525573f9afdb7f68475149
puppet-openstack-cloud
Table of Contents
- Overview - What is the cloud module?
- Module Description - What does the module do?
- Setup - The basics of getting started with puppet-openstack-cloud
- Implementation - An under-the-hood peek at what the module is doing
- Limitations - OS compatibility, etc.
- Getting Involved - How to go deeper
- Development - Guide for contributing to the module
- Contributors - Those with commits
- Release Notes - Notes on the most recent updates to the module
Overview
The puppet-openstack-cloud module is a flexible Puppet composition layer capable of configuring the core OpenStack services:
- Nova (compute)
- Glance (image)
- Keystone (identity)
- Cinder (volume)
- Horizon (dashboard)
- Heat (orchestration)
- Ceilometer (telemetry)
- Neutron (networking)
- Swift (object storage)
- Trove (database as a service)
Cinder, Glance and Nova can use Ceph as backend storage, using puppet-ceph.
Only KVM and QEMU are supported as hypervisors, for now.
Neutron use ML2 plugin with GRE and Open-vSwitch drivers.
Cinder has multi-backend support:
- RBD (default)
- NetAPP
- iSCSI
- EMC VNX direct
- NFS
Glance supports different backends:
- RBD (default)
- file
- NFS (mount a NFS share by using file backend)
- Swift
Neutron supports:
- ML2 plugin with OVS agent (GRE + VXLAN supported)
- Cisco plugin with N1KV agent (non-ML2)
Trove support is now experimental.
Puppet Modules are a collection of related contents that can be used to model the configuration of a discrete service.
These Puppet modules are based on the openstack documentation.
Module Description
There are a lot of moving pieces in OpenStack, consequently there are several Puppet modules needed to cover all these pieces. Each module is then made up of several class definitions, resource declarations, defined resources, and custom types/providers. A common pattern to reduce this complexity in Puppet is to create a composite module that bundles all these component type modules into a common set of configurations. The cloud module is doing this compositing and exposing a set of variables needed to be successful in getting a functional stack up and running.
Pre-module Dependencies
Notes about Puppet3
Puppet 3.x isn't yet available on Debian/RedHat stable osfamily, but hopefully puppet provides a Official repository, please see this page for the setup.
Platforms
These modules have been fully tested on Ubuntu Precise and Debian Wheezy and RHEL 6.
Setup
What the cloud module affects
- The entirety of OpenStack!
Installing Puppet
Puppet Labs provides two tools for getting started with managing configuration modeling with Puppet, Puppet Enterprise or its underlying opensource projects, i.e. Puppet and MCollective.
- Puppet Enterprise is a complete configuration management platform, with an optimized set of components proven to work well together. Is free up to 10 nodes so if you're just using Puppet for OpenStack management this might just work perfectly. It will come configured with a handful of extra components that make for a richer experience, like a web interface for managing the orchestration of Puppet and certificate management.
- Puppet manages your servers: you describe machine configurations in an easy-to-read declarative language, and Puppet will bring your systems into the desired state and keep them there. This is the opensource version of Puppet and should be available in your operating system's package repositories but it is generally suggested you use the yum or apt repositories from Puppet Labs if possible.
Consult the documentation linked above to help you make your decision but don't fret about the choice to much, opensource Puppet agents are compatible with Puppet Enterprise Puppet masters.
Optional Puppet features
The swift portions of this module needs Puppet's exported resources. Exported resources leverages the PuppetDB to export and share data across other Puppet managed nodes.
Installing latest unstable cloud module from source
cd /etc/puppet/modules
git clone git@github.com:redhat-openstack/openstack-puppet-modules.git modules
cd modules
git checkout -b puppet-openstack-cloud origin/enovance
gem install --no-ri --no-rdoc r10k
# a debian package is available in jessie
PUPPETFILE=./Puppetfile PUPPETFILE_DIR=../ r10k --verbose 3 puppetfile install
Pre-puppet setup
The things that follow can be handled by Puppet but are out of scope of this document and are not included in the cloud module.
Beginning with puppet-openstack-cloud
Utilization of this module can come in many forms. It was designed to be capable of deploying all services to a single node or distributed across several. This is not an exhaustive list, we recommend you consult and understand all the manifests included in this module and the core openstack documentation.
Implementation
(more doc should be written here)
Limitations
- Deploys only with rabbitmq and mysql RPC/data backends.
- Not backwards compatible with pre-2.x release of the cloud modules.
Getting Involved
Need a feature? Found a bug? Let us know!
We are extremely interested in growing a community of OpenStack experts and users around these modules so they can serve as an example of consolidated best practices of how to deploy OpenStack.
The best way to get help with this set of modules is to email the group associated with this project:
dev [at] enovance [dot] com
Issues should be opened here:
https://bugs.launchpad.net/puppet-openstack-cloud/+filebug
Contributors
Release Notes
See CHANGELOG file.