>>> On 4/13/2011 at 04:37 PM, Andrew Beekhof <and...@beekhof.net> wrote: > On Wed, Apr 13, 2011 at 8:28 AM, Tim Serong <tser...@novell.com> wrote: > > On 4/12/2011 at 05:48 PM, Andrew Beekhof <and...@beekhof.net> wrote: > >> Here's an example of the before and after. Thoughts? > > > > Looks pretty good to me. Certainly easier to understand what's > > intended when reading the new version. > > > > Is it worth allowing <colocation_set> and <ordering_set> to have an > > optional role attribute, which would be inherited by all children? > > Or is that just more confusing (too many options not always a good > > thing). > > IMHO its more confusing. > Most sets wont set role at all and for the few that do only a fraction > of the resources in the set will typically need it. > > So not sure the additional complexity it buys us much other than > questions "do i configure it here or there?".
OK, agreed. Cheers, Tim -- Tim Serong <tser...@novell.com> Senior Clustering Engineer, OPS Engineering, Novell Inc. _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
