Hi,
Then I can't find a good solution :
Let me explain what I would like :
1/ one clone-fs1 type ocfs2 to be mounted on both nodes when pacemaker is up
2/ one group1 of resources which needs clone-fs1 to be mounted
3/ one group2 of resources which needs clone-fs1 to be mounted
4/ group1 and group2 can be started on same node or group1 on one side
and group2 on the other side
So I tried to play with constraints and order and so I configured :
crm configure colocation coloc1 +INFINITY: group1 clone-fs1
crm configure colocation coloc2 +INFINITY: group2 clone-fs1
crm configure order order1 mandatory: clone-fs1 group1
crm configure order order2 mandatory: clone-fs1 group2
these order commands only to be sure that clone-fs1 was mounted before
starting the group1 or group2
And I was expecting the clone-fs1 to be started on both nodes (as it is
a clone resource), and
that group1 or group2 could be started on whatever node, but in fact
this configuration
leads to (example with only group1) :
Resource Group: group1
IPaddr (ocf::heartbeat:IPaddr): Started node1
res-nagios (lsb:nagios): Started node1
Clone Set: clone-fs1
Started: [ node1 ]
Stopped: [ fs-BCM-data:1 ]
and of course when group1 is started on node2 :
Resource Group: group1
IPaddr (ocf::heartbeat:IPaddr): Started node2
res-nagios (lsb:nagios): Started node2
Clone Set: clone-fs1
Started: [ node2 ]
Stopped: [ fs-BCM-data:1 ]
So, is it a way to get the behavior I want :
clone-fs1 mounted on both sides
group1 started only if clone-fs1 is already started
group2 started only if clone-fs1 is already started
group1 and group2 could be started not on same node
???
Thanks
Regards
Alain Moullé
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
