On 27 May 2014, at 1:16 am, Vladimir Kuklin <vkuk...@mirantis.com> wrote:

> Hi all
> 
> We are working on HA solutions for OpenStack(-related) services and figured 
> out that sometimes we need clones to be notified if one of the cluster nodes 
> running clone instances goes offline. E.g., we need this information to make 
> RabbitMQ AMQP broker cluster to forget this node until it goes up again. This 
> is easily achievable if we stop the instance on the node - then notification 
> is sent to clone instances and everything is fine. But what can we do if node 
> goes offline unexpectedly? Is there any way to notify other clones that the 
> slave is dead and perform corresponding actions?

Currently no, but it sounds like a useful feature to add.

> 
> One of the ways we figured out is to implement additional cluster monitoring 
> action in resource OCF and purge "dead" nodes, but it looks a little bit 
> overwhelming and inconvenient. Is there a chance we missed some attributes 
> that allow configuration of such behaviour that pacemaker notifies other 
> clones on node offline/fence/cold_shutdown ?
> 
> 
> 
> -- 
> Yours Faithfully,
> Vladimir Kuklin,
> Fuel Library Tech Lead,
> Mirantis, Inc.
> +7 (495) 640-49-04
> +7 (926) 702-39-68
> Skype kuklinvv
> 45bk3, Vorontsovskaya Str.
> Moscow, Russia,
> www.mirantis.com
> www.mirantis.ru
> vkuk...@mirantis.com
> _______________________________________________
> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Reply via email to