On 27 Feb 2014, at 12:32 am, Néstor C. <xala...@gmail.com> wrote: > > > > 2014-02-18 0:47 GMT+01:00 Andrew Beekhof <and...@beekhof.net>: > > On 17 Feb 2014, at 10:34 pm, Néstor C. <xala...@gmail.com> wrote: > > > > > > > > > 2014-02-17 1:22 GMT+01:00 Andrew Beekhof <and...@beekhof.net>: > > > > On 21 Jan 2014, at 10:50 pm, Néstor C. <xala...@gmail.com> wrote: > > > > >> Hello. > > >> > > >> When you need that some primitives switch in block you can use a group. > > > > >Groups are just a syntactic shortcut for ordering and colocation > > >constraints. > > > > There is a manner of view this "hyde" contraints? > > > > > > >> > > >> There is a manner to get this when you have a clone or a master/slave > > >> involved? > > >> > > >> For example: > > >> > > >> Imagine a drbd disk (DR), a filesystem over ti (FS) and a service over > > >> all (SRV). > > >> The first one is a ms resource, and the other, primitives. > > >> > > >> The colocation rules are: > > >> colocation fs_on_dr inf: FS DR:Master > > >> colocation srv_on_fs inf: SRV FS > > >> > > >> The order rules are: > > >> order fs_after_dr inf: DR:promote FS:start > > >> order srv_after_fs inf: FS:start SRV:start > > >> > > >> How can switch the entire cluster to other node if SRV fails? (like if > > >> all was in a group) > > > > >In what way does it not do so already with the above constraints? > > > > I want some kind of "circular constraint" > > We actively detect and prevent colocation and ordering loops. > What version of pacemaker is this? > > > Pacemaker 1.1.9 on Suse sles 11 sp3
It is possible that pacemaker has gotten smarter since then and currently behaves as you'd like. Probably best to run this via SLES support so they can get a new version to you if needed. > > > like if srv fails move the entire stack to other node. > > If i add other constraint like: > > colocation dr on srv inf: DR:Master SRV > > > > It doesn't start. > > > > Thanks! > > > > > > _______________________________________________ > > 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 > > > _______________________________________________ > 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 > > > _______________________________________________ > 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
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ 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
