Jan, Could you pls elaborate? Currently we are thinking of running a script that will generate the list of attributes after reading from another file . But these are running into 3000+ parameters. :( It will be a huge effort to maintain it.
All I want is Pacemaker not to all stop/start when resource attributes change. Would it be easier to modify the pacemaker source code and ignore this change of value? -Regards Nikhil On Wed, Nov 30, 2016 at 8:46 PM, Jan Pokorný <jpoko...@redhat.com> wrote: > On 28/11/16 09:44 +0530, Nikhil Utane wrote: > > I understand the whole concept of reload and how to define parameters > with > > unique=0 so that pacemaker can call the reload operation of the OCF > script > > instead of stopping and starting the resource. > > Now my problem is that I have 100s of parameters and I don't want to > > specify each of those with unique=0. > > Would it be doable that your agent, when asked for metadata, will > produce them as usual, but in addition runs the XML through XSL > template that will add these unique=0 declarations for you > (except perhaps some whitelist)? > > -- > Jan (Poki) > > _______________________________________________ > Users mailing list: Users@clusterlabs.org > http://clusterlabs.org/mailman/listinfo/users > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org > >
_______________________________________________ Users mailing list: Users@clusterlabs.org http://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
