<div dir="ltr">Hi, Jay<br><br>Yep. Here is the link to mail archive (I hoped that they would hit "Reply All" button):<br><a href="https://www.mail-archive.com/pacemaker@oss.clusterlabs.org/msg19896.html">https://www.mail-archive.com/pacemaker@oss.clusterlabs.org/msg19896.html</a><div>
<br></div><div>Actually, this is what Mirantis Linux Hardening team could do, I hope, in this release cycle and push it to upstream.<br><div><br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Thu, Jun 12, 2014 at 2:44 AM, Jay Pipes <span dir="ltr"><<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">On 05/26/2014 11:16 AM, Vladimir Kuklin wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all<br>
<br>
We are working on HA solutions for OpenStack(-related) services and<br>
figured out that sometimes we need clones to be notified if one of the<br>
cluster nodes running clone instances goes offline. E.g., we need this<br>
information to make RabbitMQ AMQP broker cluster to forget this node<br>
until it goes up again. This is easily achievable if we stop the<br>
instance on the node - then notification is sent to clone instances and<br>
everything is fine. But what can we do if node goes offline<br>
unexpectedly? Is there any way to notify other clones that the slave is<br>
dead and perform corresponding actions?<br>
<br>
One of the ways we figured out is to implement additional cluster<br>
monitoring action in resource OCF and purge "dead" nodes, but it looks a<br>
little bit overwhelming and inconvenient. Is there a chance we missed<br>
some attributes that allow configuration of such behaviour that<br>
pacemaker notifies other clones on node offline/fence/cold_shutdown ?<br>
</blockquote>
<br></div>
Ping. Hi Vladimir, did you ever get any response about this? I'm also interested in the answers...<br>
<br>
Best,<br>
-jay<br>
<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Yours Faithfully,<br>Vladimir Kuklin,<br>Fuel Library Tech Lead,<br>Mirantis, Inc.<br>+7 (495) 640-49-04<br>+7 (926) 702-39-68<br>Skype kuklinvv<br>
45bk3, Vorontsovskaya Str.<br>Moscow, Russia,<br><a href="http://www.mirantis.ru/" target="_blank">www.mirantis.com</a><br><a href="http://www.mirantis.ru/" target="_blank">www.mirantis.ru</a><br><a href="mailto:vkuklin@mirantis.com" target="_blank">vkuklin@mirantis.com</a></div>
</div>