[Pacemaker] is_managed meta attribute on suse 10 with heartbeat + pacemaker

[emmanuel segura]

Hello Lars,

I saw the same problem on suse 11, this is the example command i found
in the man page for stop a resource

man crm_resource
     Start or stop a resource:

............
               crm_resource -r my_first_ip -p target_role -v stopped

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

============

Online: [ node01 node02 ]

Full list of resources:

 Dummy1    (ocf::pacemaker:Dummy):    Started node01
 Dummy2    (ocf::pacemaker:Dummy):    Started node02
 Dummy3    (ocf::pacemaker:Dummy):    Started node02

node01:~ # crm configure show Dummy2
primitive Dummy2 ocf:pacemaker:Dummy \
    meta target-role="Started"

node01:~ # crm configure show Dummy2
primitive Dummy2 ocf:pacemaker:Dummy \
    meta target-role="Started" \
    params target_role="stopped"

using the meta parameter with the man page command

node01:~ # crm_resource --meta -r Dummy2 -p target_role -v stopped

node01:~ # crm configure show Dummy2
primitive Dummy2 ocf:pacemaker:Dummy \
    meta target-role="Started" target_role="stopped" \
    params target_role="stopped"
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

So, from my point of view, the man page is wrong for two reasons, the
meta attributes target_role it should be target-role and the --meta
options is missing

2014-07-14 11:05 GMT+02:00 emmanuel segura <emi2fast at gmail.com>:
> Thanks Lars,
>
> I took the command from man page, "Disabling a resource management for
> a resource in the CRM
>               crm_resource -p is_managed -r my_first_ip -t primitive -v off
> "
>
> I think the man pages is wrong, because is missing the --meta parameter
>
> 2014-07-12 20:36 GMT+02:00 Lars Marowsky-Bree <lmb at suse.com>:
>> On 2014-07-10T21:57:24, emmanuel segura <emi2fast at gmail.com> wrote:
>>
>>> I know heartbeat is deprecated, but we have an old cluster, and today
>>> i tryed to disable the cluster monitoring for maintance on a resource
>>> using the following command "crm_resource -r myresource -t primitive
>>> -p is_managed -v off", but after this, the cluster stopped the
>>> resource, so my question is, is_managed is different between suse 10
>>> and suse 11 pacemaker version.
>>
>> SLES 10 did not yet ship pacemaker, but heartbeat with the builtin crm
>> (the predecessor to pacemaker).
>>
>> In theory, is_managed off isn't supposed to stop resources on SLES10
>> either, but you may be lacking a --meta in that commandline.
>>
>> It's conceivable of course that you're hitting a rare bug, in which case
>> you may have to report it to SUSE; that version is based on heartbeat
>> 2.1.4 with heavy backports from pacemaker, I doubt anyone here can help
>> with that. (And, frankly, I'm praying I don't have to go dig out that
>> code again myself ;-)
>>
>>
>> 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 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



-- 
esta es mi vida e me la vivo hasta que dios quiera