[Pacemaker] options listed more than once

[Pavlos Parissis]

On 16 November 2010 11:12, Andrew Beekhof <andrew at beekhof.net> wrote:
> On Tue, Nov 16, 2010 at 11:04 AM, Pavlos Parissis
> <pavlos.parissis at gmail.com> wrote:
>> On 16 November 2010 10:49, Andrew Beekhof <andrew at beekhof.net> wrote:
>>> On Mon, Nov 15, 2010 at 4:35 PM, Pavlos Parissis
>>> <pavlos.parissis at gmail.com> wrote:
>>>> Hi,
>>>>
>>>> When I have multiple values for a cluster options, ow do I check which
>>>> value is currently being used by the cluster?
>>>> In the configuration explained there is a reference to rules chapter
>>>> but I couldn't find an answer on that chapter.
>>>
>>> Good question, I don't think we have a way to do that directly at the moment.
>>> You might be able to use crm_resource to infer it with -g.
>> Nope
>
> did you try with -m too?
>> [root at node-01 ~]# crm_resource -g resource-stickiness  -r ip_01
>> Error performing operation: The object/attribute does not exist
>> [root at node-01 ~]# crm_resource -g resource-stickiness -t group -r pbx_service_01
>> Error performing operation: The object/attribute does not exist
>> [root at node-01 ~]# crm_resource -g resource-stickiness -t primitive -r ip_01
>> Error performing operation: The object/attribute does not exist


oops, no
 # crm_resource -m -g resource-stickiness -t primitive -r ip_01
1000

>>>
>>> Not a bad feature request though, could you add it to bugzilla?
>> Done, http://developerbugs.linux-foundation.org/show_bug.cgi?id=2521
>>
>>>
>>>>
>>>> Here is what I have and I want to get the current value of resource-stickiness
>>>> [root at node-03 log]# crm_attribute --type rsc_defaults --name
>>>> resource-stickiness --query
>>>> Multiple attributes match name=resource-stickiness
>>>>  Value: INFINITY       (id=working-hours-stickiness)
>>>>  Value: 0      (id=after-hours-stickiness)
>>>>
>>>>
>>>> Cheers,
>>>> Pavlos
>>>>
>>>> _______________________________________________
>>>> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>>>>
>>>
>>> _______________________________________________
>>> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>>>
>>
>> _______________________________________________
>> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>>
>
> _______________________________________________
> 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
>