On 1/12/2012 1:10 AM, Andrew Beekhof wrote: >> Defining the set of nodes that compose the cluster seems like >> a very good thing just for its own sake. > > On the otherhand, I'd argue that forcing people to run > corosync-quorumtool and to then re-add the same information to the > config with an editor, on every existing node, when adding a new > member is inherently error prone. The current interface to add/remove nodes is suboptimal at best. Adding a node is easy, but remove it is indeed painful, making the user experience rather poor IMHO. Fabio _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
