> From: [EMAIL PROTECTED] > To: [email protected] > Subject: Re: [Linux-HA] A resource starts when an event happens > Date: Fri, 18 Jul 2008 09:50:32 +0200 > > look up rsc_location constraints in: > > http://clusterlabs.org/mw/Image:Configuration_Explained.pdf >
The document has examples for running the resources in the node with the best connectivity or examples of choosing a location based on connectivity. I search a configuration that a resource x, starts only when an event happens, not before. For example: A resource IPaddres starts when the node miss the connectivity and this recourse will stop when the node will have connectivity. A rsc_location is the solution? How would this rsc_location? Does the configuration below because it is no valid? > On Jul 18, 2008, at 2:08 AM, ZiLioN ZilLioN wrote: > > > > > Hello! > > I want a configuration that a resource IPaddress starts ONLY when > > the node miss conectivity (pingd), not before. > > This configuration is possible: > > > > <primitive id="..." class="..." provider="..." type="IPaddr" > > is_managed="false"> > > <operation> > > <op id="..." name="start" timeout="5s" prereq="nothing" > > on_fail="restart" role="stopped"> > > <instance_attributes id="..."> > > <rule id="..." score="INFINITY"> > > <expression id="..." > > attribute="pingd" operation="not_defined" /> > > </rule> > > <attributes> > > <nvpair id="..." name="ip" > > value"x.x.x.x" /> > > </attributes> > > </instance_attributes> > > </op> > > </operation> > > </primitive> > > > > I think that this configuration is very difficult... > > > > How do I do? The expression return true o false when the connectivity is miss. In this case the operation is start...Is rare :) _________________________________________________________________ Tu mejor plan para el fin de semana y toda la actualidad del mundo del corazón. Entra en MSN Entretenimiento http://entretenimiento.es.msn.com/_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
