[Pacemaker] understanding scores
Pavlos Parissis
pavlos.parissis at gmail.com
Tue Nov 16 10:55:49 UTC 2010
On 16 November 2010 11:26, Dejan Muhamedagic <dejanmm at fastmail.fm> wrote:
> Hi,
>
> On Mon, Nov 15, 2010 at 05:01:27PM +0100, Pavlos Parissis wrote:
> > On 15 November 2010 16:43, Andrew Beekhof <andrew at beekhof.net> wrote:
> > > On Mon, Nov 15, 2010 at 3:18 PM, Pavlos Parissis
> > > <pavlos.parissis at gmail.com> wrote:
> > >> On 15 November 2010 08:07, Andrew Beekhof <andrew at beekhof.net> wrote:
> > >>> On Fri, Nov 12, 2010 at 7:54 PM, Pavlos Parissis
> > >>> <pavlos.parissis at gmail.com> wrote:
> > >>>> Hi,
> > >>>>
> > >>>> I am trying to understand how the scores are calculated based on the
> > >>>> output of ptest -sL and I have few questions
> > >>>> Below is my scores with a line number column and the bottom you
> will
> > >>>> find my configuration
> > >>>>
> > >>>> So, let's start
> > >>>>
> > >>>> 1 group_color: pbx_service_01 allocation score on node-01: 200
> > >>>> 2 group_color: pbx_service_01 allocation score on node-03: 10
> > >>>> 3 group_color: ip_01 allocation score on node-01: 1200
> > >>>> 4 group_color: ip_01 allocation score on node-03: 10
> > >>>> so for so good, ip_01 has 1000 due to resource-stickiness="1000"
> plus
> > >>>> 200 from the group location constraint
> > >>>>
> > >>>> 5 group_color: fs_01 allocation score on node-01: 1000
> > >>>> 6 group_color: fs_01 allocation score on node-03: 0
> > >>>> 7 group_color: pbx_01 allocation score on node-01: 1000
> > >>>> 8 group_color: pbx_01 allocation score on node-03: 0
> > >>>> 9 group_color: sshd_01 allocation score on node-01: 1000
> > >>>> 10 group_color: sshd_01 allocation score on node-03: 0
> > >>>> 11 group_color: mailAlert-01 allocation score on node-01: 1000
> > >>>> 12 group_color: mailAlert-01 allocation score on node-03: 0
> > >>>> hold on now, why all the above resources have 1000 on node-01 and
> not
> > >>>> 1200 as fs_01
> > >>>
> > >>> its only applied to ip_01, the rest inherit it from there
> > >>>
> > >>>>
> > >>>> 13 native_color: ip_01 allocation score on node-01: 5200
> > >>>> 5 resources x 1000 from resource-stickiness="1000" plus, right? what
> > >>>> is the difference between in native and group?
> > >>>
> > >>> Many things, can you be specific?
> > >> In principles what are the difference? if my question sounds stupid
> > >> then it is because I don't understand the terminology.
> > >
> > > well, groups are an ordered collection of natives.
> > >
> > >>
> > >>>
> > >>>>
> > >>>> 14 native_color: ip_01 allocation score on node-03: 10
> > >>>> 15 clone_color: ms-drbd_01 allocation score on node-01: 4100
> > >>>> why 4100?
> > >>>
> > >>> probably the promotion score
> > >> I have "order pbx_service_01-after-drbd_01 inf: ms-drbd_01:promote
> > >> pbx_service_01:start"
> > >> does promotion score you mention come out the above contstraint?
> > >
> > > only from colocation constraints
> > then it comes out from "colocation fs_01-on-drbd_01 inf: fs_01
> > ms-drbd_01:Master"
> > which has score inf, where at line 15 score is 4100.
> > >>
> > >> I think my issue here is how I look at the numbers, I assume that
> > >> every time I see score for a resource, that score also includes any
> > >> scores mentioned before. Is my assumption correct?
> > >
> > > often, it depends on what colocation constraints you have set up
> >
> > Ok, let me ask it differently, how by looking at the output of ptest
> > -sL can I find the score of a resource for a specific node?
> > Since the score of a resource for a specific node is mentioned in
> > several lines, it is not that easy- at least to me.
>
> You can try with showscores.sh. It should do exactly what you
> want. It is not package, but you can get it from the pacemaker
> repository.
>
> Thanks,
>
> Dejan
>
PERFECT!!!!!!!!
This is what I want. Thank you very much.
why is not part of the delivery?
Pavlos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20101116/abc03216/attachment-0002.htm>
More information about the Pacemaker
mailing list