[Pacemaker] order constraint clone / group of primitives resources

[Andrew Beekhof]

On 23 May 2014, at 6:54 pm, Björn Urbanek <habanera at gmx.com> wrote:

> Hello!
> 
> I'm using pacemaker with crmsh. 
> 
> I want to realize the following order:
> 
> I have 3 primitive resources:
> P1 
> P2 
> P3
> 
> I have also a cloneset of a primitive resource CL_P4. 
> 
> I want to say that one the resources of the primitive set (P1 P2 P3) is
> required to start CL_P4. It doesn't mather which, only that one is started.
> (P1 P2 P3) --> CL_P4
> Also the cluster should always try to start all 3 primitive P1/P2/P3 per
> default, but if one or two of these resources failes or have to be relocated
> it should doesn't affect the CL_P4. 
> Only if all of the (P1 P2 P3) resources are down or have to be relocated at
> the same time CL_P4 should be affected and have to stopped and restarted.
> 
> Can anyone help me / give me a hint?

Look for require-all=false in the documentation

> 
> Many thanks!
> 
> Best regards
> 
> Bjoern
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140526/b275c13d/attachment-0003.sig>