> quorum {
> nodeid_list: x y z...
> node.x.votes: ..
> node.y.votes: ..
> }
I'd suggest a general nodes section that allows all nodes to be specified
along with their properties.
When corosync starts up, it would pick out its own entry in that nodes
section, and if it doesn't find one, it would fail to start.
A node entry needs ipaddr, nodeid, votes. A hostname might be nice also.
Something like
nodes {
node {
ipaddr: 1.1.1.1
nodeid: 1
votes: 1
}
node {
ipaddr: 2.2.2.2
nodeid: 2
votes: 1
}
}
With no nodeid specified, nodeid would default to ipaddr unless it's ipv6.
With no votes specified, votes would default to 1.
By default the quorum module would calculate expected votes by adding the
individual node votes (a different explicit expected votes value could be
specified in the quorum config block to override this.)
There shouldn't be any node-specific config values outside the node
sections so that the config file can be the same on all nodes.
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss
