On 2013-11-26T09:19:36, "Bauer, Stefan (IZLBW Extern)" <stefan.ba...@iz.bwl.de>
wrote:
> Hi,
>
> thank you for your input - unfortunately i want to go another path if
> possible to not not have to change more parts of my configuration:
>
> I have setup so far:
>
> group cluster1 p_eth0 p_conntrackd
> location groupwithping cluster1 \
> rule "id="groupwithping-rule" pingd: defined pingd
> colocation cluster inf: p_eth0 p_conntrackd
This colocation is redundant, since the group already implies it.
>
> Now I cannot simply add p_openvpn1 + openvpn2 to the above colocation because
> then the order is active. Why is colocation even taking care of the order of
> the resources?!
>
> If I change it to:
>
> Colocation cluster inf: p_eth0 p_conntrackd p_openvpn1 p_openvpn2 - I cannot
> start openvpn2 without having openvpn1 up.
> This is not what I want.
True. That's not what you want. Also, your colocations are the wrong way
around (you want to place p_conntrackd where p_eth0 is, not the other
way around). The easiest way is to split them into separate colocations:
colocation c-1 inf: p_openvpn1 cluster1
colocation c-2 inf: p_openvpn2 cluster1
Regards,
Lars
--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
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
