This is related to the quorum discussion, but I want to set the constraints as the developers think through how best to implement the config file changes. 1. If someone wants to use multicast without the node IP addresses listed, we shouldn't stop that from happening. 2. If someone wants to use multicast with quorum, we should expect them to set the node list. (and print an error if not set) 2. The node list is mandatory for UDPU. 4. Our community will always be pointing people to use UDPU as their transport mechanism except in cases where slightly better performance is needed (less cpu consumption). 5. f For RRP, the node IP list must be set for each interface separately. This doesn't absolutely have to happen in the "totem.interface" section but it makes the most sense there. Moving forward I'd really like to transition users to consuming UDPU rather then multicast. I expect most users would prefer this method of operation to changing their switch configurations, As a result, we should get people in the habit of setting the IP addresses of the nodes that make up the cluster. Experts will always remain that don't want a static node list and those use cases won't be removed. Regards -steve _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
