Hi, On Wed, Jan 07, 2009 at 03:13:22PM +0100, Dominik Klein wrote: > > 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 > > Is the first still possible (ie create a resource along with its monitor > ops)?
Sure. > > 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 > > > > 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 > > So 100 is a default value but can be overridden I hope? What's wrong with having 100 as a default? As I already wrote in another post, I think that it is good to have a "standard" preference value. Of course, if somebody insists, or needs a different score, they could still use the location statement. No doubt that some people will need different values, but I suspect that the majority of clusters just need a simple preference setting. Thanks, Dejan _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
