Open Stack

Hi, Jay

Yep. Here is the link to mail archive (I hoped that they would hit "Reply
All" button):
https://www.mail-archive.com/pacemaker@oss.clusterlabs.org/msg19896.html

Actually, this is what Mirantis Linux Hardening team could do, I hope, in
this release cycle and push it to upstream.



On Thu, Jun 12, 2014 at 2:44 AM, Jay Pipes <jaypipes at gmail.com> wrote:

> On 05/26/2014 11:16 AM, Vladimir Kuklin 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?
>>
>> 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 ?
>>
>
> Ping. Hi Vladimir, did you ever get any response about this? I'm also
> interested in the answers...
>
> Best,
> -jay
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
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 <http://www.mirantis.ru/>
www.mirantis.ru
vkuklin at mirantis.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140612/5375dd65/attachment.html>