>
> I'm still not sure why the following does not work: 
> 
>       <clone id="pingd">
>               <instance_attributes id="pingd" >
>                       <attributes>    
>                               <nvpair id="pingd-globally_unique"
> name="globally_unique" value="0" />
>                               <nvpair id="pingd-clone_node_max"
> name="clone_node_max" value="1"/>
>                       </attributes>
>               </instance_attributes>
>               <primitive id="pingd-child" provider="heartbeat" class="ocf"
> type="pingd">
>                       <operations>
>                               <op id="pingd-child-monitor" name="monitor"
> interval="20ms" timeout="40ms" prereq="nothing"/>
>                               <op id="pingd-child-start" name="start"
> prereq="nothing"/>
>                       </operations>
>                       <instance_attributes id="pingd_inst_attr">
>                               <attributes>
>                                       <nvpair id="pingd-dampen"
> name="dampen" value="5s"/>
>                                       <nvpair id="pingd-multiplier"
> name="multiplier" value="100"/>
>                               </attributes>
>                        </instance_attributes>
>                       </primitive>
>       </clone>
> 
>      </resources>
>      <constraints>
>        <rsc_colocation id="colocation_ip_in_out" from="ip_resource_outside"
> to="ip_resource_inside" score="INFINITY"/>
>        <rsc_location id="prefer_2b" rsc="ip_resource_outside">
>          <rule id="rule_prefer_2b" score="10">
                                                        ^^^^^^
>            <expression attribute="#uname" operation="eq" value="CN-2-PC-B"
> id="9c3bc605-b595-42e0-9444-dfad8547cd3e"/>
>        </rule>
>       </rsc_location>
>       <rsc_location id="choose_connected" rsc="pingd-child">

What is "pingd-child"? Do you have such a resource?

>               <rule id="rule_choose_connected" score_attribute="pingd">
>                       <expression id="expr_rule_choose_connected"
> attribute="pingd" operation="defined"/>
>               </rule> 
>                               
>               </rsc_location>
>      </constraints>
> 
> Everything is working, except the rules for pingd. When a pingnode is 
> brought down the resources stay there where they where.(I was watching 
> the trafic, the pings go out.)

You should check the status section of the running CIB for values of the
pingd attribute:

cibadmin -Q | grep pingd

If they are the same for all nodes, then nothing will happen. If not, then
constraints are wrong.

Thanks,

Dejan

---------------

Hi Dejan,

I was checking out the cib status part and the values are changing:  
<nvpair id="..." name="pingd" value="100"/> => <nvpair id="..." name="pingd"
value="0"/>
So the problems seem to be at the constraints. 

"pingd_child" is the primitive id of the clone "pingd". 
I discovered one error already: 
rsc_location id="prefer_2b" rsc="ip_resource_outside">
          <rule id="rule_prefer_2b" score="100">
I changed it to score="10", otherwise (as I understand) both constraints
would have same weight. 
Still the resources are not moving. 
I set default_resource_stickiness to 0 and
default_resource_failure_stickiness to -INFINITY.

Thanks!

Peter


_______________________________________________
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