Yes, EnablePacemaker! A little old fashioned and not very well suited for OpenStack you say heh? Let's try to talk a bit about this then. News is that we're adding into TripleO/Puppet an option to deploy Pacemaker on the Overcloud nodes. Puppet you said? Sure TripleO can use Puppet now for the configuration of the Overcloud nodes, ask Dan Prince :) Actually usage of Puppet is nowdays the preferred approach and many features are available …

A wrap up on the status of TripleO's Cinder HA spec. First, a link to the cinder-ha blueprint, where you can find even more links, to the actual spec (under review) and the code changes (again, still under review). Intent of the blueprint is for the TripleO deployments to keep Cinder volumes available and Cinder operational in case of failures of any node.

This said, should $subject sound interesting to you, beware the code still …

One of the topics discussed during the TripleO mid-cycle meetup in RDU was our status in relation to deploying OpenStack in a highly available manner. This had been worked on for some time and recently reached a usable state.

Majority of complications seem to come from two factors: 1) we need to guarantee availability of external services too, like the database and the message broker, which aren't exactly designed for a scale-out scenario, 2) despite …