[Pacemaker] group logic in hb_gui

Bart Coninckx bart.coninckx at telenet.be
Fri Dec 24 05:16:36 EST 2010


On Friday 24 December 2010 06:49:00 Yan Gao wrote:
> On 12/24/10 04:55, Bart Coninckx wrote:
> > On Wednesday 22 December 2010 06:30:36 Yan Gao wrote:
> >> On 12/22/10 04:16, Bart Coninckx wrote:
> >>> All,
> >>> 
> >>> I recently jumped from the hb_gui version of SLES10 to the one in
> >>> SLES11. I noticed that the "colocated" and "ordered" properties of a
> >>> group cannot be set anymore. Should I assume that the ordering is now
> >>> determined by the order of the shown list (and hence the reason of
> >>> being able to shift resources up and down in the list)?
> >> 
> >> Correct.
> >> 
> >>> And is colocation now by default on for resources in a
> >>> group or should I now handle both ordering and colocation with
> >>> constraints?
> >> 
> >> The "ordered" and "colocated" attributes of a group default to "true".
> >> 
> >> Regards,
> >> 
> >>   Yan
> > 
> > Hi,
> > 
> > thx! So if I observe some of my iSCSILogicalUnit resource instances stop
> > and I can't start them, that is not related to the fact that Pacemaker
> > tries to start them on another node?
> 
> It's hard to say without a hb_report.
> 
> > The default colocation of the group they belong to
> > should prevent that?
> 
> The default colocation of a group prevent its members from running on
> different nodes.
> 
> Regards,
>   Yan

Yan,

thx for your answer. Wasn't aware yet of hb_report, just ran it and hope to be 
able to pinpoint the error myself before bugging the mailing list  ;-)


thx again,

B.




More information about the Pacemaker mailing list