[Pacemaker] Ressources not moving to node with better connectivity - pingd

emmanuel segura emi2fast at gmail.com
Mon Dec 9 10:45:44 UTC 2013


your location ins't enaugh, sorry for my english :)

location mynet mygrp_or_rsc \
        rule $id="-rule" -inf: not_defined pingd or pingd number:lte 300



2013/12/9 Bauer, Stefan (IZLBW Extern) <Stefan.Bauer at iz.bwl.de>

>  Pardon!
>
>
>
> node debian6-n1
>
> node debian6-n2
>
> primitive p_alias0 ocf:heartbeat:IPaddr2 \
>
>         params ip="4.5.6.7" cidr_netmask="24" nic="eth0" \
>
>         op start interval="0" timeout="20" \
>
>         op stop interval="0" timeout="30" \
>
>         op monitor interval="20"
>
> primitive p_conntrackd lsb:conntrackd-sync \
>
>         op monitor interval="30s"
>
> primitive p_eth0 ocf:heartbeat:IPaddr2 \
>
>         params ip="10.0.2.250" cidr_netmask="24" nic="eth0" \
>
>         op start interval="0" timeout="20" \
>
>         op stop interval="0" timeout="30" \
>
>         op monitor interval="20"
>
> primitive p_openvpn lsb:openvpn \
>
>         op start interval="0" timeout="20" \
>
>         op stop interval="0" timeout="30" \
>
>         op monitor interval="20"
>
> primitive p_ping ocf:pacemaker:ping \
>
>         params host_list="7.4.5.6 127.0.0.1" multiplier="150" dampen="5s" \
>
>         op start interval="0" timeout="60" \
>
>         op stop interval="0" timeout="20" \
>
>         op monitor interval="20" timeout="60"
>
> group cluster1 p_eth0 p_alias0 p_openvpn p_conntrackd \
>
>         meta target-role="Started"
>
> clone pingclone p_ping \
>
>         meta interleave="true"
>
> location groupwithping cluster1 \
>
>         rule $id="groupwithping-rule" pingd: defined pingd
>
> colocation cluster inf: p_eth0 p_alias0 p_openvpn p_conntrackd
>
> property $id="cib-bootstrap-options" \
>
>         dc-version="1.1.7-ee0730e13d124c3d58f00016c3376a1de5323cff" \
>
>         cluster-infrastructure="openais" \
>
>         expected-quorum-votes="2" \
>
>         no-quorum-policy="ignore" \
>
>         stonith-enabled="false"
>
> rsc_defaults $id="rsc-options" \
>
>         resource-stickiness="100"
>
>
>
> Stefan
>
>
>
> *Von:* emmanuel segura [mailto:emi2fast at gmail.com]
> *Gesendet:* Montag, 9. Dezember 2013 11:22
> *An:* The Pacemaker cluster resource manager
> *Betreff:* Re: [Pacemaker] Ressources not moving to node with better
> connectivity - pingd
>
>
>
> where is your config?
>
>
>
> 2013/12/9 Bauer, Stefan (IZLBW Extern) <Stefan.Bauer at iz.bwl.de>
>
> Hi List,
>
>
>
> even though following well known documentations about a ping clone
> resource my resources are not moving to the node with the better
> connectivity:
>
>
>
> 2 Nodes configured, 2 expected votes
>
> 6 Resources configured.
>
> ============
>
>
>
> Online: [ debian6-n2 debian6-n1 ]
>
>
>
> Resource Group: cluster1
>
>      p_eth0     (ocf::heartbeat:IPaddr2):       Started debian6-n2
>
>      p_alias0   (ocf::heartbeat:IPaddr2):       Started debian6-n2
>
>      p_openvpn  (lsb:openvpn):  Started debian6-n2
>
>      p_conntrackd       (lsb:conntrackd-sync):  Started debian6-n2
>
> Clone Set: pingclone [p_ping]
>
>      Started: [ debian6-n1 debian6-n2 ]
>
>
>
> Node Attributes:
>
> * Node debian6-n2:
>
>     + pingd                             : 150           : Connectivity is
> degraded (Expected=300)
>
> * Node debian6-n1:
>
>     + pingd                             : 300
>
>
>
> I would expect the resources to move to N1.
>
> Resource-stickiness is set to 100.
>
> 2 Pinghosts are configured – n2 can right now only reach a single pinghost.
>
>
>
> Resource              Score     Node       Stickiness #Fail
> Migration-Threshold
>
> p_alias0              700       debian6-n2 100        0
>
> p_alias0              -INFINITY debian6-n1 100        0
>
> p_conntrackd          100       debian6-n2 100        0
>
> p_conntrackd          -INFINITY debian6-n1 100        0
>
> p_eth0                1650      debian6-n2 100        0
>
> p_eth0                300       debian6-n1 100        0
>
> p_openvpn             300       debian6-n2 100        0
>
> p_openvpn             -INFINITY debian6-n1 100        0
>
> p_ping:0              100       debian6-n1 100        0
>
> p_ping:0              -INFINITY debian6-n2 100        0
>
> p_ping:1              0         debian6-n1 100        0
>
> p_ping:1              100       debian6-n2 100        0
>
>
>
> Anybody see what the problem could be?
>
> To be honest I did not fully understood the deeper function of how the
> scores are calculated.
>
>
>
> Thank you.
>
>
>
> Stefan
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>
>
>
>
> --
> esta es mi vida e me la vivo hasta que dios quiera
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>
>


-- 
esta es mi vida e me la vivo hasta que dios quiera
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20131209/37cc1909/attachment.htm>


More information about the Pacemaker mailing list