I node list is NOT technically important for quorum. VMS manages quite
happily without one - it builds up the node list at run-time as nodes
join the cluster. They need a security key to do so but no other
pre-configuration is needed if they have their own system disk (most VMS
clusters are single system disk, but it's not a requirement).
cman in RHEL4 didn't need a pre-defined nodes list, it was designed not
to need one. It's only the requirement of the higher layers that
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'
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
____ _ _____ _ _
/ ___| ___ ___ __| | |_ _| |__ (_)_ __ __ _
| | _ / _ \ / _ \ / _` | | | | '_ \| | '_ \ / _` |
| |_| | (_) | (_) | (_| | | | | | | | | | | | (_| |
\____|\___/ \___/ \__,_| |_| |_| |_|_|_| |_|\__, |
|___/
That was one of my motivations behind the neglected -X option to cman.
The less a user has to configure, the less they will get wrong and the
fewer support calls they will make.
Chrissie
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss
