<div dir="ltr"><div><div><div>Hi Dejan,<br><br></div>Thanks for the response.<br><br></div><div>In our setup, we want the resources to start on the 2 nodes (active/active) so that the downtime would be less.<br></div><div>
<br></div><div>All clients connect to the VIP. If the resource on any one node goes down, I expect the VIP should be moved to another node and since the resource is already running on the another node the down time would be less.<br>
<br></div><div>I thought of configuring them as is-manged= false then the pacemaker wouldn't restart the resources on failed node.<br></div><div><br></div><div>Thanks<br></div></div>Eswar<br><div><div><div><div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Fri, Jun 7, 2013 at 7:32 PM, Dejan Muhamedagic <span dir="ltr"><<a href="mailto:dejanmm@fastmail.fm" target="_blank">dejanmm@fastmail.fm</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<div><div class="h5"><br>
On Fri, Jun 07, 2013 at 12:49:49PM +0530, ESWAR RAO wrote:<br>
> Hi All,<br>
><br>
> I am trying to run same RA on both nodes using clone.<br>
> My set up is a 2 node cluster with HB+pacemaker.<br>
><br>
> The RA aren't started automatically.<br>
> They are started through pacemaker only.<br>
><br>
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br>
> #crm configure primitive ha_vip ocf:IPaddr2 params ip=192.168.101.205<br>
> cidr_netmask=32 nic=eth1 op monitor interval=30s<br>
><br>
> #crm configure primitive oc_d1 lsb::testd1 meta allow-migrate="true"<br>
> migration-threshold="1" failure-timeout="30s" op monitor interval="3s"<br>
> #crm configure clone oc_d1_clone oc_d1 meta clone-max="2"<br>
> clone-node-max="1" globally-unique="false" interleave="true"<br>
><br>
> #crm configure primitive oc_d2 lsb::testd2 meta allow-migrate="true"<br>
> migration-threshold="3" failure-timeout="30s" op monitor interval="5s"<br>
> #crm configure clone oc_d2_clone oc_d2 meta clone-max="2"<br>
> clone-node-max="1" globally-unique="false" interleave="true"<br>
><br>
> # crm configure colocation oc-ha_vip inf: ha_vip oc_d1_clone oc_d2_clone<br>
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++<br>
><br>
> I observe the RAs are not getting started in the other node.<br>
><br>
> ha_vip (ocf::heartbeat:IPaddr2): Started ubuntu190<br>
> Clone Set: oc_d1_clone [oc_d1]<br>
> Started: [ ubuntu190 ]<br>
> Stopped: [ oc_d1:1 ]<br>
> Clone Set: oc_d2_clone [oc_d2]<br>
> Started: [ ubuntu190 ]<br>
> Stopped: [ oc_d2:1 ]<br>
><br>
><br>
> But if I remove the colocation constraint then the RA are starting on the 2<br>
> nodes.<br>
> But without colocation, if any RA fails the vip will not migrate which is<br>
> bad.<br>
<br>
</div></div>Can you explain why do you need the oc_* resources running both<br>
nodes but at the same time they depend on the IP address which is<br>
not cloned. Looks to me a condition which is simply impossible to<br>
meet.<br>
<br>
Thanks,<br>
<br>
Dejan<br>
<div class="im"><br>
> Can some one help me out in my issue.<br>
><br>
><br>
> Thanks<br>
> Eswar<br>
<br>
</div>> _______________________________________________<br>
> Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><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>
_______________________________________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><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>
</blockquote></div><br></div></div></div></div></div></div>