[Pacemaker] [pacemaker][patch 3/4] Simple changes for "Pacemaker Explained", Chapter 6 CH_Constraints.xml

Tim Serong tserong at novell.com
Wed Apr 13 02:56:38 EDT 2011

 >>> On 4/13/2011 at 04:37 PM, Andrew Beekhof <andrew at beekhof.net> wrote: 
> On Wed, Apr 13, 2011 at 8:28 AM, Tim Serong <tserong at novell.com> wrote: 
> > On 4/12/2011 at 05:48 PM, Andrew Beekhof <andrew at 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.



Tim Serong <tserong at novell.com>
Senior Clustering Engineer, OPS Engineering, Novell Inc.

More information about the Pacemaker mailing list