[Pacemaker] OCF_RESKEY_CRM_meta* envars
Andrew Beekhof
andrew at beekhof.net
Tue Jun 2 07:48:22 EDT 2009
On Tue, Jun 2, 2009 at 11:24 AM, Florian Haas <florian at linbit.com> wrote:
> Andrew,
>
> On 2009-06-02 11:15, Andrew Beekhof wrote:
>>>> Check out the action2xml() function, in particular its use of hash2metafield().
>>> Hm. I feel a wee bit smarter after looking through that, but still fail
>>> to understand why
>>
>> Do you mean technically or conceptually?
>
> I would say I need to understand conceptually first, before I can tackle
> this issue on technical terms. :)
>
>> Which vars in particular are you talking about?
>
> OCF_RESKEY_CRM_meta_clone_max
> OCF_RESKEY_CRM_meta_clone_node_max
> OCF_RESKEY_CRM_meta_master_max
> OCF_RESKEY_CRM_meta_master_node_max
>
> I fail to understand under which circumstances exactly these are passed
> in for a Master/Slave resource. It would make sense to me that the would
> be passed in on any operation, but it appears to me that they are in
> fact not available in some.
You appear to have found a bug.
Those should always be present.
>
> Your insight is much appreciated. Thanks!
>
> Cheers,
> Florian
>
> _______________________________________________
> Pacemaker mailing list
> Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
More information about the Pacemaker
mailing list