Am Mittwoch, 27. November 2013, 10:51:43 schrieb Bauer, Stefan:
> Thank you Michael for pointing that out.
> 
> I now use colocation cluster inf: (p_openvpn1 p_openvpn2) cluster
> 
> Now the openvpn resources can be stopped independently - but still depend on
> ressources from the cluster-group.
> 
> Is that the expected behavior? I'm a bit confused as I expected the other
> way around. If the group is (after) openvpn in the list, it should depend
> on openvpn. Like I would read from left to right.

Rewrite the constraint like:

colocation col_cluster inf: cluster (p_openvpn1 p_openvpn2)

colocation reads: colocate resource WITH another resource. But this is all 
documented in the manuals.

-- 
Mit freundlichen Grüßen,

Michael Schwartzkopff

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
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

Reply via email to