lmb at suse
Oct 13, 2008, 11:43 AM
Post #5 of 5
(892 views)
Permalink
|
|
Re: How to get supported meta attributes?
[In reply to]
|
|
On 2008-10-06T08:38:04, Andrew Beekhof <beekhof [at] gmail> wrote:
>>> We previously discussed changing the configuration so that it was
>>> possible to validate the meta attributes, but in the end decided
>>> against it.
>> Maybe we could use meta-data instead of schemas to define them ?
>
> That just creates one more place to maintain it I'm afraid.
> The PE doesn't need it and the CIB wouldn't be using either (since
> validation is done with schemas).
But surely every pengine process knows which meta_attributes it would
consider "valid" for a given resource class
(primitive/clone/master_slave). Would it not be possible to enumerate
them in the meta-date call, so that the GUI has more hints?
Afterall, all data is available in include/crm/msg_xml.h - could that be
changed to an array which could be dumped via pengine metadata, or to a
public .h which the mgmtd/CLI could include during build?
Clearly, being more assisting to the UIs would be helpful ;-)
One imagines that with a real parser for them, some code even could be
consolidated to check their values etc. Just thinking. Nothing urgent
;-)
Regards,
Lars
--
Teamlead Kernel, SuSE Labs, Research and Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Pacemaker mailing list
Pacemaker [at] clusterlabs
http://list.clusterlabs.org/mailman/listinfo/pacemaker
|
