<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><div>Greetings,</div><div><br></div><div>I am getting closer to what I need. </div><div><br></div><div>I am having trouble figuring out a rule for p_VIPeth1_1 that will cause it's score to be -inf if p_R_NODE1 is not running.</div><div>Here is the rule that I am struggling with. </div><div><div><br></div><div>location p_VIPeth1_1_loc2 p_VIPeth1_1 \</div><div><span class="Apple-tab-span" style="white-space: pre;"> </span>rule $id="p_VIPeth1_1_loc2-rule" -inf: p_R_NODE1 eq Stopped</div></div><div><br></div><div><br></div><div>\/ The entire config so far is below \/</div><div><br></div><div>root@clust1:~# crm configure show</div><div>node $id="404ea40c-f92d-4649-869d-41beaf261d87" clust1 \</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>attributes standby="off"</div><div>node $id="ae33be72-ccbb-4f54-859f-fd400efeb60b" clust2 \</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>attributes standby="off"</div><div>primitive p_PINGDB ocf:pacemaker:ping \</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>params host_list="192.168.254.42" name="p_PINGDB" \</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>op monitor interval="15s" timeout="5s"</div><div>primitive p_R_NODE1 lsb:rabbitmq-server \</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>op monitor interval="15s" timeout="15s" \</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>meta target-role="Started" is-managed="true"</div><div>primitive p_R_NODE2 lsb:rabbitmq-server \</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>op monitor interval="15s" timeout="15s" \</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>meta target-role="Started"</div><div>primitive p_VIPeth1_1 ocf:heartbeat:IPaddr \</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>params ip="192.168.254.78" cidr_netmask="255.255.255.0" nic="eth1" \</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>op monitor interval="40s" timeout="20s" \</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>meta target-role="Started" is-managed="true"</div><div>clone p_PINGDB_clone p_PINGDB</div><div>location cli-standby-p_R_NODE1 p_R_NODE1 \</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>rule $id="cli-standby-rule-p_R_NODE1" -inf: #uname eq clust2</div><div>location p_R_NODE1_loc p_R_NODE1 -inf: clust2</div><div>location p_R_NODE1_pref p_R_NODE1 inf: clust1</div><div>location p_R_NODE2_loc p_R_NODE2 -inf: clust1</div><div>location p_R_NODE2_pref p_R_NODE2 inf: clust2</div><div>location p_VIPeth1_1_loc p_VIPeth1_1 \</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>rule $id="p_VIPeth1_1_loc-rule" -inf: p_PINGDB lte 0</div><div><b>location p_VIPeth1_1_loc2 p_VIPeth1_1 \</b></div><div><b><span class="Apple-tab-span" style="white-space:pre"> </span>rule $id="p_VIPeth1_1_loc2-rule" -inf: p_R_NODE1 eq Stopped</b></div><div>property $id="cib-bootstrap-options" \</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>dc-version="1.1.6-9971ebba4494012a93c03b40a2c58ec0eb60f50c" \</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>cluster-infrastructure="Heartbeat" \</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>stonith-enabled="false" \</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>default-action-timeout="120" \</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>last-lrm-refresh="1395671783"</div><div>root@clust1:~# </div><div><br></div><div><br></div><div>Thanks, </div><div>Steve</div><div><br></div><div><br></div><br><div>From: andrew@beekhof.net<br>Date: Wed, 19 Mar 2014 09:37:43 +1100<br>To: pacemaker@oss.clusterlabs.org<br>Subject: Re: [Pacemaker] Don't want to stop lsb resource on migration<br><br><pre> <br>On 19 Mar 2014, at 6:56 am, Bingham <knee-jerk-reaction@hotmail.com> wrote:<br> <br>> <br>> My problem is that I need to have rabbitmq running on both node1 and node2.<br>> I also need the IP to fail over if rabbitmq were to fail on the current node.<br>> <br>> The 2 rabbitmq services are communicating with each other. <br>> Data is pushed to the clients. <br>> <br>> Even though the IP may currently live on node1, data may flow through node1 then through node2 (via rabbit) and out to client.<br>> <br>> Rnode1 -------> client1<br>> / /|\<br>> DB---->VIP |<br>> \|/<br>> Rnode2 --------> client2<br>> <br>> <br>> <br>> Maybe I should not have these resources grouped together since that implies collocation infinity for IP and rabbitmq?<br> <br>Correct. It also sounds like rabbitmq should be a master/slave resource<br> <br>> <br>> <br>> Steve<br>> <br>> <br>> From: andrew@beekhof.net<br>> Date: Tue, 18 Mar 2014 11:44:34 +1100<br>> To: pacemaker@oss.clusterlabs.org<br>> Subject: Re: [Pacemaker] Don't want to stop lsb resource on migration<br>> <br>> <br>> On 14 Mar 2014, at 1:00 am, Bingham <knee-jerk-reaction@hotmail.com> wrote:<br>> <br>> > Hello,<br>> > <br>> > My setup:<br>> > I have a 2 node cluster using pacemaker and heartbeat. I have 2 resources, ocf::heartbeat:IPaddr and lsb:rabbitmq-server. <br>> > I have these 2 resources grouped together and they will fail over to the other node.<br>> > <br>> > <br>> > <br>> > question:<br>> > When rabbitmq is migrated to node1 from node2 I would like to 'not' have the the </etc/init.d/rabbitmq-server stop> happen on the failed server (node1 in this example).<br>> <br>> 'migrate' has special meaning here.<br>> After a failure rabbitmq is moved (stopped on the old node and started on the new one), which is different from a migration.<br>> <br>> Leaving rabbitmq in an unclean state on node1 would definitely not be a good idea.<br>> <br>> > <br>> > Is it possible to do this in crm? <br>> > <br>> > I realize that I could hack the initscript's case statement for stop to just "exit 0", but I am hoping there is a way to do this in crm.<br>> > <br>> > <br>> > Thanks for any help,<br>> > Steve<br>> > <br>> > <br>> > _______________________________________________<br>> > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br>> > <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>> > <br>> > Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>> > Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>> > Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>> <br>> <br>> _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a> Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a> Getting started:<a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a> Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>> _______________________________________________<br>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org<br>> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>> <br>> Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>> Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br> <br></pre><br>_______________________________________________
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</div> </div></body>
</html>