On 11/01/12 01:03, Digimer wrote:
On 01/10/2012 05:08 AM, Fabio M. Di Nitto wrote:For example: quorum { nodeid_list: x y z... node.x.votes: .. node.y.votes: .. }My only comment/recommendation would be; quorum { common_stuff: foo node x { votes: 1 id: 1 } node y { votes: 1 id: 2 } node z { votes: 1 id: 3 } } From an admin perspective, I find it easier to write one directive that will be more or less common, copypasta it X number of times and then go back and change the one or two values that need updating. This is functionally equivalent to your example, so I won't argue strongly for this. Though I must admit I also have a stylistic preference for separate directives. I think your version more closely meshes to objctl, so perhaps it's easier to use your example?
I think that's definitely more consistent with the rest of the config file, and also less confusing given the way that corosync-objctl dumps the internal configuration too.
Chrissie _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
