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

2013-12-09 Thread Bauer, Stefan (IZLBW Extern) 
Thank you for your time! It works now :)

Stefan

-Ursprüngliche Nachricht-
Von: Michael Schwartzkopff [mailto:m...@sys4.de] 
Gesendet: Montag, 9. Dezember 2013 14:26
An: The Pacemaker cluster resource manager
Betreff: Re: [Pacemaker] Ressources not moving to node with better connectivity 
- pingd

Am Montag, 9. Dezember 2013, 13:06:04 schrieb Bauer, Stefan:
> Why are some resources listed more than once in the output?
> What is the difference between group_color and native_color?
> If a resource has a value of -INFINITY is it because the cluster 
> already decided that this resource should not run on this host or it 
> can not run on this host due to other reasons?
> 
> I'm not quite sure, how a resource stickiness interferes with the 
> internal decicions taken to migrate.

Everything is points. stickiness is points. constraints result in points.

With every event the cluster calculates the matrix from all nodes and all 
resources. A resource will run on that node it can collect most points.

Beware of impicit constraints that give points. I.e. a colocation

col col_A_with_B inf: A B

will result in -inf points for the resource B on all nodes where A is not 
running.

Look at the output of crm_simulate -s -L, write down the matrix and understand 
it.

--
Mit freundlichen Grüßen,

Michael Schwartzkopff

--
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044 Franziskanerstraße 15, 
81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein

___
Pacemaker mailing list: Pacemaker@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

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

2013-12-09 Thread Michael Schwartzkopff 
Am Montag, 9. Dezember 2013, 13:06:04 schrieb Bauer, Stefan:
> Why are some resources listed more than once in the output?
> What is the difference between group_color and native_color?
> If a resource has a value of -INFINITY is it because the cluster already
> decided that this resource should not run on this host or it can not run on
> this host due to other reasons?
> 
> I'm not quite sure, how a resource stickiness interferes with the internal
> decicions taken to migrate.

Everything is points. stickiness is points. constraints result in points.

With every event the cluster calculates the matrix from all nodes and all 
resources. A resource will run on that node it can collect most points.

Beware of impicit constraints that give points. I.e. a colocation

col col_A_with_B inf: A B

will result in -inf points for the resource B on all nodes where A is not 
running.

Look at the output of crm_simulate -s -L, write down the matrix and understand 
it.

-- 
Mit freundlichen Grüßen,

Michael Schwartzkopff

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein

signature.asc
Description: This is a digitally signed message part.
___
Pacemaker mailing list: Pacemaker@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

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

2013-12-09 Thread Bauer, Stefan (IZLBW Extern) 
Why are some resources listed more than once in the output?
What is the difference between group_color and native_color?
If a resource has a value of -INFINITY is it because the cluster already 
decided that this resource should not run on this host or it can not run on 
this host due to other reasons?

I'm not quite sure, how a resource stickiness interferes with the internal 
decicions taken to migrate.

Stefan


-Ursprüngliche Nachricht-
Von: Michael Schwartzkopff [mailto:m...@sys4.de] 

Test your config.

check the points by

# crm_simulate -s -L

and adjust your scoring system accordingly.


Mit freundlichen Grüßen,

___
Pacemaker mailing list: Pacemaker@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

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

2013-12-09 Thread Michael Schwartzkopff 
Am Montag, 9. Dezember 2013, 11:27:51 schrieb Bauer, Stefan:
> Hi Michael,
> 
> so that means, either increasing one value or lower the other right?
> Or is lowering resource_stickiness the only reasonable way?
> 
> I tried a multiplier of 1000 but no change in the behavior.
> 
> Stefan
> 
> -Ursprüngliche Nachricht-
> Von: Michael Schwartzkopff [mailto:m...@sys4.de]
> You resource_stickiness is too high in respect to the pingd points. You
> resource "earns" 700 points staying there where it is and only 300 points
> for moving. Reduce your resource_stickiness to a reasonable amount.

Test your config.

check the points by

# crm_simulate -s -L

and adjust your scoring system accordingly.


Mit freundlichen Grüßen,

Michael Schwartzkopff

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein

signature.asc
Description: This is a digitally signed message part.
___
Pacemaker mailing list: Pacemaker@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

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

2013-12-09 Thread Lars Marowsky-Bree 
On 2013-12-09T10:28:32, "Bauer, Stefan (IZLBW Extern)"  
wrote:

> location groupwithping cluster1 \
> rule $id="groupwithping-rule" pingd: defined pingd

I tend to prefer a -inf score for nodes where pingd is *not* defined or
zero.

(Downside is that when you lose all connectivity, all services will be
stopped.)


Regards,
Lars

-- 
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 
21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde


___
Pacemaker mailing list: Pacemaker@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

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

2013-12-09 Thread Bauer, Stefan (IZLBW Extern) 
Hi Michael,

so that means, either increasing one value or lower the other right?
Or is lowering resource_stickiness the only reasonable way?

I tried a multiplier of 1000 but no change in the behavior.

Stefan

-Ursprüngliche Nachricht-
Von: Michael Schwartzkopff [mailto:m...@sys4.de] 
You resource_stickiness is too high in respect to the pingd points. You 
resource "earns" 700 points staying there where it is and only 300 points for 
moving. Reduce your resource_stickiness to a reasonable amount.

BTW: I hope 127.0.0.1 in the config of the ping resource is only for 
obfuscation on the list and no real configuration.


-- 
Mit freundlichen Grüßen,

Michael Schwartzkopff

___
Pacemaker mailing list: Pacemaker@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

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

2013-12-09 Thread emmanuel segura 
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) 

>  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:emi2f...@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) 
>
> 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 1000
>
> p_alias0  -INFINITY debian6-n1 1000
>
> p_conntrackd  100   debian6-n2 1000
>
> p_conntrackd  -INFINITY debian6-n1 1000
>
> p_eth01650  debian6-n2 1000
>
> p_eth0300   debian6-n1 1000
>
> p_openvpn 300   debian6-n2 1000
>
> p_openvpn -INFINITY debian6-n1 1000
>
> p_ping:0  100   debian6-n1 1000
>
>

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

2013-12-09 Thread Michael Schwartzkopff 
Am Montag, 9. Dezember 2013, 10:28:32 schrieb Bauer, Stefan:
> 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:emi2f...@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)
> mailto:stefan.ba...@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 1000
> p_alias0  -INFINITY debian6-n1 1000
> p_conntrackd  100   debian6-n2 1000
> p_conntrackd  -INFINITY debian6-n1 1000
> p_eth01650  debian6-n2 1000
> p_eth0300   debian6-n1 1000
> p_openvpn 300   debian6-n2 1000
> p_openvpn -INFINITY debian6-n1 1000
> p_ping:0  100   debian6-n1 1000
> p_ping:0  -INFINITY debian6-n2 1000
> p_ping:1  0 debian6-n1 1000
> p_ping:1  100   debian6-n2 1000
> 
> 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

You resource_stickiness is too high in respect to the pingd points. You 
resource "earns" 700 points staying there where it is and only 300 points for 
moving. Reduce your resource_

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

2013-12-09 Thread Bauer, Stefan (IZLBW Extern) 
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:emi2f...@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) 
mailto:stefan.ba...@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 1000
p_alias0  -INFINITY debian6-n1 1000
p_conntrackd  100   debian6-n2 1000
p_conntrackd  -INFINITY debian6-n1 1000
p_eth01650  debian6-n2 1000
p_eth0300   debian6-n1 1000
p_openvpn 300   debian6-n2 1000
p_openvpn -INFINITY debian6-n1 1000
p_ping:0  100   debian6-n1 1000
p_ping:0  -INFINITY debian6-n2 1000
p_ping:1  0 debian6-n1 1000
p_ping:1  100   debian6-n2 1000

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@oss.clusterlabs.org<mailto:Pacemaker@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@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

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

2013-12-09 Thread emmanuel segura 
where is your config?


2013/12/9 Bauer, Stefan (IZLBW Extern) 

>  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 1000
>
> p_alias0  -INFINITY debian6-n1 1000
>
> p_conntrackd  100   debian6-n2 1000
>
> p_conntrackd  -INFINITY debian6-n1 1000
>
> p_eth01650  debian6-n2 1000
>
> p_eth0300   debian6-n1 1000
>
> p_openvpn 300   debian6-n2 1000
>
> p_openvpn -INFINITY debian6-n1 1000
>
> p_ping:0  100   debian6-n1 1000
>
> p_ping:0  -INFINITY debian6-n2 1000
>
> p_ping:1  0 debian6-n1 1000
>
> p_ping:1  100   debian6-n2 1000
>
>
>
> 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@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@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

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

2013-12-09 Thread Bauer, Stefan (IZLBW Extern) 
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 1000
p_alias0  -INFINITY debian6-n1 1000
p_conntrackd  100   debian6-n2 1000
p_conntrackd  -INFINITY debian6-n1 1000
p_eth01650  debian6-n2 1000
p_eth0300   debian6-n1 1000
p_openvpn 300   debian6-n2 1000
p_openvpn -INFINITY debian6-n1 1000
p_ping:0  100   debian6-n1 1000
p_ping:0  -INFINITY debian6-n2 1000
p_ping:1  0 debian6-n1 1000
p_ping:1  100   debian6-n2 1000

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@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