On Wed, Dec 21, 2011 at 2:21 PM, Andrew Beekhof <and...@beekhof.net> wrote: > On Tue, Dec 13, 2011 at 11:32 PM, Vladislav Bogdanov > <bub...@hoster-ok.com> wrote: >> Hi Andrew, all, >> >> I'm now testing latest changes in git, everything goes much cleaner then >> a week ago, I'll (hopefully) make report later. >> >> One feature came into mind during testing: >> Imagine resource which was tried to be started on all nodes and failed >> everywhere. >> Then administrator changes resource definition to fix start problem. >> Now, resource is not tried to start until it is cleaned up (or both its >> failure-timeout passes and cluster state re-checked). >> Idea is to make automatic resource cleanup after definition change. > > Not good if the device wasn't failed. > Imagine someone changing the 'ip' for an IPaddr resource, the old > value would never be removed. > >> >> That would help those who use some automatic tools to manage pacemaker >> resources. >> >> Btw, I did not find cluster-recheck-interval in pacemaker explained >> "Cluster options" chapter together with stop-all-resources, >> maintenance-mode and placement-strategy. Former option described only in >> chapter about rules, others are not mentioned at all.
Ok, we'll have to fix that _______________________________________________ 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
