On 12/07/12 10:50, Andrew Beekhof wrote: > On Fri, Dec 7, 2012 at 1:44 PM, Gao,Yan <y...@suse.com> wrote: >> On 12/07/12 10:14, Andrew Beekhof wrote: >>> On Fri, Dec 7, 2012 at 12:46 PM, Gao,Yan <y...@suse.com> wrote: >>>>> what about: >>>>> container-type=(black | white) >>>>> >>>>> black: colocate with the vm >>>>> white: potentially other colocation or location constraints >>>> Or just: >>>> contained=(true| false) >>>> >>>> Detaults to true? >>> >>> Doesn't the set up a conceptual oxymoron? >> Hmm, a bit. I'd like a boolean attribute though. >> >> Regards, >> Gao,Yan >> >>> If its not contained why are you specifying a container? > > Any particular reason? A boolean is more user friendly I think. People like to simply answer yes or no ;-)
> Not that I'm tied to black/white as values, but most places I put > boolean options end up being replaced with an enum because we think of > something else to go there. > So I'm trying to learn from my mistakes :) :-) An enum would definitely mean possibilities . It should not be a big problem for UIs to provide the option list or tab completion. Regards, Gao,Yan -- Gao,Yan <y...@suse.com> Software Engineer China Server Team, SUSE. _______________________________________________ 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://bugs.clusterlabs.org
