On Tue, Mar 11, 2008 at 11:02 AM, Sebastian Reitenbach <[EMAIL PROTECTED]> wrote: > Hi, > > I want to achieve the following: > I have two groups of resources, these shall run on the same host, and > startup in a given order. > > Therefore I created an order and an collocation constraint. > So group1 starts before group2, and the collocation says, if group1 is not > able to run on a node, group2 will not start. > > However, if all resources in group1 are started, then the resources in > group2 are started too. But when I then shutdown any single resource in > group1, then group2 stops working too. > I am not sure, whether my collocation or order is the reason for the > observed behavior.
I have not tried it by myself but there are these "Advisory-Only Ordering" constraints: <rsc_order id="orderid" from="res2" to="res1" score="0"/> ... have a look at Andrews Pacemaker manual ... http://www.clusterlabs.org/wiki/images/f/fb/Configuration_Explained.pdf Regards, Andreas > > Right now, from what I observed, it seems, that when I stop just one > resource in the group, then the group itself is seen as stopped, and the > group2 stops then too. > My question is, is there a parameter or something to keep the group > as "started", until all resources in the group, or the group completely is > set to be stopped? is that possible? > > Otherwise I'd have use very many single resources, and very many order and > collocation constraints. > > cheers > Sebastian > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
