On May 21, 2006, at 3:44 PM, Lars Marowsky-Bree wrote:
Prop 1: I set up a "meta" hashtable and populate it with meta_attributes (and for backwards compatibility copy in any unset attributes from the regular hashtable).
From then on i just look up the name at the meta hashtable.
"and add the crm-meta- prefix at the end"
i think thats the bit we diverged on (because i didnt say it).
so the admin would still configure <nvpair name=X value=Y/>
end the code would still look for X
the only change is that when we're creating the list of parameters to pass to the lrm, we prefix them with "crm-meta-"... so X comes out as crm-meta-X (and if you configured it in the old way, as X too for backwards compatibility)
Ah, I see.
Well, that makes more sense.
So, as soon as a meta-section is seen, the "automatic" population of it from the regular name-space is turned off for that resource?
yep
Makes sense, yes. I think now I get what you say.
Though still, how would the RA inform the tools about description & defaults for this?
this is where i'm a bit lost... these aren't RA parameters so in theory there's nothing to change right? And the tools like the mgmtd/GUI would still need to be modified to set these options in a whole different section.
I'd still go with simply prefixing them everywhere.
-- Andrew Beekhof
"Would the last person to leave please turn out the enlightenment?" - TISM
|
_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
