[Pacemaker] howto group resources without having an order

[Michael Schwartzkopff]

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 230 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20131127/b53efd11/attachment-0003.sig>