Thank you Andrew. Answers below. >>> Sounds interesting, can you give any comment about how it differs to the other[i] upstream agent? Am I right that this one is effectively A/P and wont function without some kind of shared storage? Any particular reason you went down this path instead of full A/A? [i] https://github.com/ClusterLabs/resource-agents/blob/master/heartbeat/rabbitmq-cluster <<< It is based on multistate clone notifications. It requries nothing shared but Corosync info base CIB where all Pacemaker resources stored anyway. And it is fully A/A. All running rabbit nodes may process AMQP connections. Master state is only for a cluster initial point at wich other slaves may join to it. Note, here you can find events flow charts as well [0] [0] https://www.rabbitmq.com/pacemaker.html Regards, Bogdan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151111/10fc9be5/attachment.html>