Hi,

On Fri, Feb 05, 2010 at 09:38:58AM -0700, [email protected] wrote:
> > Message: 6
> > Date: Fri, 5 Feb 2010 12:25:44 +0100
> > From: Dejan Muhamedagic <[email protected]>
> > Subject: Re: [Linux-HA] clone constraints
> > To: General Linux-HA mailing list <[email protected]>
> > Message-ID: <[email protected]>
> > Content-Type: text/plain; charset=us-ascii
> 
> > Hi,
> 
> [...]
> 
> Dejan,
> 
> Thanks for the reply.
> 
> Read your v0.9 "Fencing and Stonith". So for a lights-out device
> like riloe(Compaq stonith ilo) which can only handle one connection
> then clones are useless ? 

Clones are not necessary, regardless of the device type. One
instance is enough to fence a node.

> From your below statement(and "Why those strange location contraints?"
> pg 7) then stonithd implicitly refuses to kill its host and the two
> contrainsts above are redundant - you imply below we will receive 
> error messages ? Why would it generate error messages if this is the
> default ?

Because the computer doesn't know what's your intention. What
happens is that the node on which CRM tries to start the stonith
resource is removed from the host list. If the list becomes
empty, then the resource can't be started.

> If I expanded the cluster to three nodes using the same riloe plugin
> would I then still only have to define three simple stonith resources
> with no constraints ?

Yes.

> I presume without a collocation rule I could
> then have two of the resources running on one machine ?

Yes.

Thanks,

Dejan

> Thanks
> 
> > If you have clone-max=1, then you don't need a clone :) Really,
> > all you need are two simple stonith resources. If you feel
> > uncomfortable with the error log messages about a stonith
> > resource not being able to run on a node, then also add the two
> > location constraints as above. And you don't need the
> > collocation, it is implied.
> 
> > Thanks,
> 
> > Dejan
> 
> > > resource. Also changed clone_node_max to clone-node-max on both as per
> > > literature - hopefully this
> > > is correct. clone-max is set to one because this is "How amny copies 
> of
> > > the resource to start" in the
> > > cluster. For riloe there should only ever be one running and not on
> > > itself.
> > >
> > > Thanks
> > >
> > > > > <rsc_location id="rsc_location_group_1" rsc="grp_1">
> > > > > <rule id="prefered_location_group_1" score="100">
> > > > > <expression attribute="#uname" id="prefered_location_group_1_expr"
> > > > > operation="eq" value="wispoller1"/>
> > > > > </rule>
> > > > > </rsc_location>
> > > > > </constraints>
> > > > > </configuration>
> > > > > </cib>
> _______________________________________________
> 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

Reply via email to