[Pacemaker] running same resource on both nodes through clone

ESWAR RAO eswar7028 at gmail.com
Fri Jun 7 07:19:49 UTC 2013


Hi All,

I am trying to run same RA on both nodes using clone.
My set up is a 2 node cluster with HB+pacemaker.

The RA aren't started automatically.
They are started through pacemaker only.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++
#crm configure primitive ha_vip ocf:IPaddr2 params ip=192.168.101.205
cidr_netmask=32 nic=eth1 op monitor interval=30s

#crm configure primitive oc_d1 lsb::testd1 meta allow-migrate="true"
migration-threshold="1" failure-timeout="30s" op monitor interval="3s"
#crm configure clone oc_d1_clone oc_d1 meta clone-max="2"
clone-node-max="1" globally-unique="false" interleave="true"

#crm configure primitive oc_d2 lsb::testd2 meta allow-migrate="true"
migration-threshold="3" failure-timeout="30s" op monitor interval="5s"
#crm configure clone oc_d2_clone oc_d2 meta clone-max="2"
clone-node-max="1" globally-unique="false" interleave="true"

# crm configure colocation oc-ha_vip inf: ha_vip oc_d1_clone oc_d2_clone
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++

I observe the RAs are not getting started in the other node.

ha_vip    (ocf::heartbeat:IPaddr2):    Started ubuntu190
Clone Set: oc_d1_clone [oc_d1]
     Started: [ ubuntu190 ]
     Stopped: [ oc_d1:1 ]
 Clone Set: oc_d2_clone [oc_d2]
     Started: [ ubuntu190 ]
     Stopped: [ oc_d2:1 ]


But if I remove the colocation constraint then the RA are starting on the 2
nodes.
But without colocation, if any RA fails the vip will not migrate which is
bad.

Can some one help me out in my issue.


Thanks
Eswar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130607/ae36aed0/attachment-0003.html>


More information about the Pacemaker mailing list