On Wed, Jan 07, 2009 at 03:43:12PM +0100, Andrew Beekhof wrote: > On Wed, Jan 7, 2009 at 14:49, Dejan Muhamedagic <[email protected]> wrote: > > Hello, > > > > Most of you are probably back from holidays, so now may be good > > time to give you some food for thought. > > > > Some, though probably not many, have already tried the crm shell > > and configuration utility. And some complained about unwieldy and > > long commands. Specifying primitives and location constraints is > > indeed somewhat clumsy. Here's proposal to at least partly > > alleviate the pain. Many thanks to Dominik Klein for useful > > suggestions and for driving the discussion privately. > > > > Of course, there is room for more improvements. Please don't keep > > your ideas to yourself. > > > > 1. Detach monitor operations from primitives > > > > old (one statement): > > primitive drbd0 drbd params drbd_resource=drbd0 \ > > op monitor role=Master interval=59s timeout=30s \ > > op monitor role=Slave interval=60s timeout=30s > > new (three statements): > > primitive drbd0 drbd params drbd_resource=drbd0 > > monitor drbd0:Master 59s:30s > > monitor drbd0:Slave 60s:30s > > I like. But as dk mentioned, allowing the old format would be nice too.
"like *it*"? Yes, the old format would still be accepted. But the output from show, and edit, would probably go with the new format. > > 2. Shorter specification of boolean variables > > > > old: > > ms ms-drbd0 drbd0 \ > > meta clone-max=2 notify=true globally-unique=false > > target-role=stopped > > new: > > ms ms-drbd0 drbd0 \ > > meta clone-max=2 notify not globally-unique stopped > > how do you know which ones are booleans? > is this only for meta attributes? what if we add new ones? > > not so keen on this. The idea was to somehow get that information, i.e. for RA parameters from the meta-data and for the meta attributes from the pacemaker source. > > 3. New "prefer" statement/clause for location preference > > > > old: > > location ms-drbd0-master-on-xen-1 ms-drbd0 rule role=master 100: > > #uname eq xen-1 > > new: > > prefer ms-drbd0:Master xen-1 # score 100 is implied > > i really wouldn't like to see a score being inferred, but otherwise i > like the new syntax Score of 100 is what is typically used. It is also good to have a "standard" value, IMO. Anyway, if one wants to use another value, the location command is of course still available. > but again, we probably need to support (but not necessarily advertise) > the old syntax for compatibility reasons > > > > > new1 (two statements): > > group g1 global-ip web-server > > prefer g1 node1 > > new2 (one statement): > > group g1 global-ip web-server prefer node1 > > marginal (i prefer the old way), but as long as both are supported i dont mind > > > > > 4. Shorter specification of colocation constraints > > > > old: > > colocation apache-group-on-ms-drbd0 inf: apache-group ms-drbd0:Master > > colocation apache-not-with-slave -inf: apache-group ms-drbd0:Slave > > new: > > colocate apache-group ms-drbd0:Master # inf is implied > > separate apache-group ms-drbd0:Slave # -inf is implied > > also a good improvement Thanks, Dejan _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
