Unfortunately the the environment the ha server/cluster I am trying to configure does not really fit with a grouping of IP/filsystem/lsb. In short: All the LSB services should be available on the same IP and there is not necessarily a mapping between the filesystems and the LSB script (so I just have to play it safe)
The ruleset is not that complicated really, it's just a lot of them :-) - The IP group has co-location and order on - The Filesystem and LSB group has co-location on and order off - Colocation between all Filesystems to the IP-group - Colocation between all LSB scripts to the IP-group - Colocation between all LSB scrpts and all Filesystems - Startorder from all LSB scripts to all Filesystems (this to enable restart) - Startorder between the groups: IP-group before Filesystems-group before LSB-group What I still do not understand is that a failed LSB-script does not trigger a failover?? Neither does a failed Filesystem (it only stops all LSB-scripts). Only a failed IP trigger a failover. Does this have anything to do with the "stickiness stuff"?? I have default-resource-stickiness = "100" default-resource-failure-stickiness = "-INFINITY" On Monday 07 May 2007 18:09:48 Yan Fitterer wrote: > Haven't looked at too much detail (lots of resources / constraints in > your cib...), but I would approach the problem differently: > > Make groups out of related IP / filesystem / service stacks. > > Then use the colocation constraints between services (across groups) to > force things to move together (if it is indeed what you are trying to > achieve). > > As well, I would start with maybe less resources, to make > experimentation and troubleshooting easier... > > What you describe below would seem broadly possible to me. > > My 2c > > Yan > > Kai Bjørnstad wrote: > > Hi, > > > > I am trying to setup an Active-Passive HA cluster dong "best effort" with > > little success. > > I am using Heartbeat 2.0.8 > > > > I have a set of IP resources, a set of external (iSCSI) mount resources > > and a set of LSB script resources. > > > > The goal of the configuration is to make Heartbeat do the following: > > - All resources should run on the same node at all times > > - If one or more of the IPs go down on, move all resources to the backup > > node. If no backup node is available, shut everything down. > > - If one or more of the mounts go down, move all resources (including > > IPs) to the backup node. If no backup node is available shut down all the > > LSB scripts and the failed mounts. Keep the mounts and IPs that did not > > fail up. - If one or more of the LSB scripts fail, move all resources to > > the backup node (including mounts and IPs). If the no backup node is > > available shut down the failed LSB script(s) but keep all other resoruces > > running (best effort) - Of course local restart should be attempted > > before moving to backup node. - Start IPs and Mounts before the LSB > > scripts > > - Start/restart order of IPs should not be enforced > > - Start/restart order of Mounts should not be enforced > > - Start/restart order of LSBs should not be enforced > > > > My question is basically: Is this at all possible??? > > -- Kai R. Bj�rnstad Senior Software Engineer dir. +47 22 62 89 43 mob. +47 99 57 79 11 tel. +47 22 62 89 50 fax. +47 22 62 89 51 [EMAIL PROTECTED] Olaf Helsets vei 6 N0621 Oslo, Norway Scali - www.scali.com Scaling the Linux Datacenter _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
