Open Stack

On 26 November 2013 17:51, Jay Pipes <jaypipes at gmail.com> wrote:

> There is no reason to run any OpenStack endpoint -- other than the Neutron
> L3 agent -- in an active/passive way. The reason is because none of the
> OpenStack endpoints maintain any state. The backend storage systems used by
> those endpoints *do* contain state -- but the endpoint services themselves
> do not.
>

100% agreed. The only parts of the system that need an active/passive HA
setup at this stage is the Neutron L3 Agent. Everything else can be setup
active/active.

My advice would be to continue using Percona XtraDB for your database
> backend (we use the same in a variety of ways, from intra-deployment-zone
> clusters to WAN-replicated clusters). That solves your database
> availability issues, and nicely, we've found PXC to be as easy or easier to
> administer and keep in sync than normal MySQL replication.
>

We use normal master/master MySQL replication, but we do have to untwist it
from time to time and watch the replication state carefully. For large
scale I'd definitely recommend looking at one of the other HA MySQL
packaging.


> We use RabbitMQ clustering and have had numerous problems with it,
> frankly. It's been our pain point from an HA perspective. There are other
> clustering MQ technologies out there, of course. Frankly, one could write a
> whole book just about how crappy the MQ clustering "story" is...
>

Interesting - we haven't had much trouble since implementing HA queues and
updating to the latest available RabbitMQ from their website (instead of
the Ubuntu package). Prior to the update we had memory leaks and lost
messages from time to time.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20131127/3c57b5de/attachment.html>