On Wed, Jan 7, 2009 at 14:49, Dejan Muhamedagic <dejanmm[at]fastmail.fm> wrote:
> Most of you are probably back from holidays, so now may be good
> time to give you some food for thought. 

Happy to oblige.

>1. Detach monitor operations from primitives
>old (one statement):
...
>new (three statements):

Why the "params" keyword in the new syntax ?

Agree for the number of statements, but keep the old, unambiguous syntax like 
this:

primitive drbd0 drbd drbd_resource=drbd0
monitor drbd0 role=Master interval=59s timeout=30s
monitor drbd0 role=Slave interval=60s timeout=30s

Strongly suggest to support *both* syntaxes.


>2. Shorter specification of boolean variables 

Seems more cosmetic to me but have no reason to oppose.
Again strongly support *both* syntaxes.

CAUTION: Do not mix keyword lists (a la xml) and language constructs.

"not globally-unique" : NOK

"!globally-unique" : OK, preferred over above

"not-globally-unique" : OK


> 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

Ok, but support also:

prefer ms-drbd0 on=xen-1 role=master # score 100 is implied

... and combinations like:

prefer ms-drbd0:master on=xen-1  ... or ...
prefer ms-drbd0 xen-1 role=master

>
>new1 (two statements):
>group g1 global-ip web-server
>prefer g1 node1
>new2 (one statement):
>group g1 global-ip web-server prefer node1
>

Agree with the two-statement.

Disagree with the one-statement.
Ambiguous. Represents an unspecified language construct.
Creates a name exception to handle the nature of this language construct.

How do you parse, what rules used to parse:

group g1 global-ip prefer prefer node1

group g1 global-ip prefer node1

group g1 global-ip web-server prefer prefer

>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

Ugh. Definitely needed.

I apologize in advance, I really looked everywhere but may have overlooked 
this, exactly which HA facility accepts this "colocation" command with this 
syntax ?

>new:
>colocate apache-group ms-drbd0:Master # inf is implied
>separate apache-group ms-drbd0:Slave # -inf is implied

Unfortunately, ambiguous.

Also, "colocate" and "separate" not the best words to describe the actions I 
understand they are supposed to undertake.




      
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to