On 2013-12-06T08:55:47, Vladislav Bogdanov <bub...@hoster-ok.com> wrote:
> BTW, pacemaker cib accepts any meta attributes (and that is very
> convenient way for me to store some 'meta' information), while crmsh
> limits them to a pre-defined list. While that is probably fine for
> novices, that limits some advanced usage scenarios, that's why I
> disabled that check by a patch for my builds.
That's intentional. You're "polluting" a namespace that doesn't belong to
you. Any update that introduces a new feature could potentially collide
with your key/value pairs. Also, the CIB really isn't performant enough
to store meta data like this.
If by "advanced" you mean "abusing cluster features", yes, then I agree,
that are scenarios we want to limit ;-)
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@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
