On 6/15/07, Yan Fitterer <[EMAIL PROTECTED]> wrote:
There is a slight catch with this, in so far as using the --meta switch
updates the attribute in question in a different node in the cib xml.
BUT, I think (at least for some versions, the issue may be fixed in the
latest code) that there are cases where one can end up with the same
attribute in both places, which is obviously very confusing.
So for all the meta attributes (is_managed, target_role, etc...), it is
worth checking that they are all in their correct location in the XML,
otherwise the problem may come back later....
As an aside, we probably really need some enhancement so that the
utilities guess by themselves when attributes are meta, and not, so that
there isn't the risk of user error.
no.
the other reason the meta section was introduced was so that we didn't
reserve keywords for CRM options (and thus freeing them up for use as
RA options).
what you describe would defeat that purpose
It's probably rather a lot to ask
administrators to always remember!
I'm not even sure I know myself the exhaustive list :(
Yan
Junko IKEDA wrote:
> Max,
> Thanks a lot. I got it!
>
> It seemed that the resource didn't restart when I added <meta_attributes>.
> (there was no log message like "send_rsc_command ... stop/start" or
> "match_graph_event ... stop/start")
> I hope my understanding is correct.
>
> Junko
>
>> -----Original Message-----
>> From: Max Hofer [mailto:[EMAIL PROTECTED]
>> Sent: Friday, June 15, 2007 5:24 PM
>> To: [email protected]
>> Cc: Junko IKEDA
>> Subject: Re: [Linux-HA] re-start action when a resource parameter is
> changed
>> That is why they introduced reosurce meta_attributes.
>>
>> See the email from A. Beekhof "Re: [Linux-HA] setting is_managed to true
>> triggers restart"
>> the 08.05.2007.
>>
>> It is described there. I'm not sure if or when the option "--meta" was
> added
>> to crm_resource tool.
>>
>> kind regards
>> Max
>>
>> On Friday 15 June 2007, Junko IKEDA wrote:
>>> Hi,
>>>
>>> I'm trying to change some parameters for a resource with "crm_resource"
>>> ,online.
>>> It's easy to change them but I found a resource stopped at first, and
>>> started again anytime.
>>> Is it possible to ignore this re-start action in the case the resource
>>> wouldn't move to another node.
>>> for instance; change "resource_stickiness" from '0' to 'INFINITY'.
>>> The resource could keep running on the current node, right?
>>>
>>> It seems that this depends on the last "else" section in
>>> ~/crm/pengine/native.c.
>>> What will happen if this section is removed?
>>> Is "RSC_ROLE_STOPPED" value needed elsewhere?
>>>
>>> ~/crm/pengine/native.c
>>> -----------------------------------------------------------
>>> ...
>>> } else {
>>> stop = stop_action(rsc, current, TRUE);
>>> start = start_action(rsc, next, TRUE);
>>> stop->optional = start->optional;
>>>
>>> if(start->runnable == FALSE) {
>>> rsc->next_role = RSC_ROLE_STOPPED;
>>> } else if(start->optional) {
>>> crm_notice("Leave resource %s\t(%s)",
>>> rsc->id, next->details->uname);
>>>
>>> } else {
>>> crm_notice("Restart resource %s\t(%s)",
>>> rsc->id, next->details->uname);
>>> }
>>> }
>>> -----------------------------------------------------------
>>>
>>> Best Regards,
>>> Junko Ikeda
>>>
>>> NTT DATA INTELLILINK CORPORATION
>>> Open Source Solutions Business Unit
>>> Open Source Business Division
>>>
>>> Toyosu Center Building Annex, 3-3-9, Toyosu, Koto-ku, Tokyo 135-0061,
> Japan
>>> TEL : +81-3-3534-4810 FAX : +81-3-3534-4814
> mailto:[EMAIL PROTECTED]
>>> http://www.intellilink.co.jp/
>>>
>>> _______________________________________________
>>> Linux-HA mailing list
>>> [email protected]
>>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>>> See also: http://linux-ha.org/ReportingProblems
>>>
>>
>>
>> --
>> Max Hofer
>> APUS Software G.m.b.H.
>> A-8074 Raaba, Bahnhofstraße 1/1
>> T| +43 316 401629 11
>> F| +43 316 401629 9
>> W| www.apus.co.at
>> E| [EMAIL PROTECTED]
>
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
