On 04/07/2013, at 9:55 PM, Vladislav Bogdanov <bub...@hoster-ok.com> wrote:
> 04.07.2013 14:50, Andrew Beekhof wrote: >> >> On 04/07/2013, at 7:24 PM, Vladislav Bogdanov <bub...@hoster-ok.com> wrote: >> >>> Hi, >>> >>> I think about safest way to expanding the cluster, and my observations >>> show that new nodes are always added in the "online" state >>> (standby="off"). I would like nodes to appear in standby="on" state >>> unless they can be fenced immediately after addition (fencing is >>> configured for them). Other option would be to add them standby >>> unconditionally (f.e. admin want to configure some node attributes >>> before node runs some resources - like I want for some clusters). >>> >>> So, I think that it is worth adding new cluster option for that (f.e. >>> node-addition-policy [online(default)|standby|fencing] ). >>> >>> I tried to add node section for not-yet-known node with crmsh but >>> failed (it doesn't like $id for such nodes). After some thinking I >>> believe it is better to have some default policy instead of adding node >>> sections "in advance", just to minimize the consequences of human errors. >>> >>> Does that make sense for others? >> >> Not a word of it :) >> >> You want nodes that appear in the membership to default to standby=on if no >> other value is set? > > That depends on an actual cluster. In short - yes. I guess that could be useful. Can you file a bug for it please? _______________________________________________ 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