On Thu, Oct 30, 2008 at 08:21, Alex Strachan <[EMAIL PROTECTED]> wrote: > Hi All, > > HA non-symmetrical cluster with two nodes; dtbaims, itbaims. > HA 2.99.1, pacemaker 1.0 > > > I have been reviewing the pacemaker_configuration guide but no luck with > this config. Lots of variations but no joy. > > Error: > Oct 30 16:58:35 dtbaims pengine: [27989]: WARN: native_color: Resource > pingd:0 cannot run anywhere > Oct 30 16:58:35 dtbaims pengine: [27989]: WARN: native_color: Resource > pingd:1 cannot run anywhere > > > How do I configure a location rule on a non-symmetric cluster so that > pingd:0,1 will run?
<rsc_location id="foo" rsc="pingd" node="dtbaims" score="1"/> <rsc_location id="foo" rsc="pingd" node="itbaims" score="1"/> The constraints below all apply to the resources that depend on the pingd attribute. But that won't be set if you don't allow pingd to run anywhere too ;-) Now the bad news, pingd/attrd is busted in 1.0.0 :-( You'll either have to wait for 1.0.1 next week or grab the latest from: http://hg.clusterlabs.org/pacemaker/stable-1.0 > Clone defn: > <clone id="pingd-clone"> > <primitive id="pingd" provider="heartbeat" class="ocf" type="pingd"> > <instance_attributes id="instance_attributes.id49788"> > <nvpair id="pingd-dampen" name="dampen" value="5s"/> > <nvpair id="pingd-multiplier" name="multiplier" value="1000"/> > <nvpair id="pingd-hosts" name="host_list" > value="192.168.201.1"/> > </instance_attributes> > <meta_attributes id="primitive-pingd.meta"/> > </primitive> > <meta_attributes id="clone-pingd-clone.meta"/> > </clone> > > Location definition: > <rsc_location id="resource_its_vip-connected" rsc="resource_its_vip"> > <rule id="pingd-exclude-rule" score="-INFINITY"> > <expression id="expression.id49786" attribute="pingd" > operation="not_defined"/> > </rule> > <rule id="pingd-prefer-rule" score-attribute="pingd"> > <expression id="pingd-prefer" attribute="pingd" > operation="defined"/> > </rule> > </rsc_location> > > > My final attempt for the day... > <rsc_location id="resource_its_vip-connected" rsc="resource_its_vip"> > <rule id="pingd-exclude-rule" score="-INFINITY"> > <expression id="expression.id49786" attribute="pingd" > operation="not_defined"/> > </rule> > <rule id="pingd-prefer-rule-dtbaims" score-attribute="pingd" > boolean-op="and"> > <expression id="pingd-prefer-dtbaims" attribute="pingd" > operation="defined"/> > <expression attribute="#uname" id="expression.id50015" > operation="eq" value="dtbaims"/> > </rule> > <rule id="pingd-prefer-rule-itbaims" score-attribute="pingd" > boolean-op="and"> > <expression id="pingd-prefer-itbaims" attribute="pingd" > operation="defined"/> > <expression attribute="#uname" id="expression.id50016" > operation="eq" value="itbaims"/> > </rule> > </rsc_location> > > > Aarrrgh - nope. > > > > > > > > > > _______________________________________________ > 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
