On Fri, Jan 13, 2012 at 10:37:54AM +0000, Christine Caulfield wrote: > >mandated it. In fact you can run cman in RHEL4 and RHEL5 without any > >nodes list if you don't need fencing. 'cman_tool join -X' ... and don't need proper quorum. > One further comment, speaking from a GSS point-of view, anything > that reduces the amount of configuration a user has to do to get a > cluster up and running is a > ____ _ _____ _ _ > / ___| ___ ___ __| | |_ _| |__ (_)_ __ __ _ > | | _ / _ \ / _ \ / _` | | | | '_ \| | '_ \ / _` | > | |_| | (_) | (_) | (_| | | | | | | | | | | | (_| | > \____|\___/ \___/ \__,_| |_| |_| |_|_|_| |_|\__, | > |___/ I agree, and I'll construe that to mean to you'd prefer corosync.conf without a list of cluster nodes. > That was one of my motivations behind the neglected -X option to > cman. I like minimal config, and we did a pretty good job with cluster.conf IMO. I often run clusters with just: <?xml version="1.0"?> <cluster name="bull" config_version="1"> <clusternodes> <clusternode name="bull-01" nodeid="1"/> <clusternode name="bull-02" nodeid="2"/> <clusternode name="bull-04" nodeid="4"/> <clusternode name="bull-05" nodeid="5"/> </clusternodes> </cluster> (Which is orders of magnitude better than what's currently possible with corosync.conf BTW. That was going to be my next campaign... if I get out of this one caring any more :-) Maybe you want to take that one up, you'll probably have more success than I would.) > The less a user has to configure, the less they will get wrong > and the fewer support calls they will make. Has the list of nodes specifically in cluster.conf been a source of mistakes and support calls over the years? My belief is that a lack of a node list would make the cluster more *difficult* to manage, not easier, which is mainly why I think it should be there. As I said before, where do you look for a list of all the nodes that *should* be in your cluster when you think there might be one or two missing? On your whiteboard? _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
