Re: ordering scores and kinds

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Andrew Beekhof <andrew@xxxxxxxxxxx> writes:

> On 22 Sep 2014, at 6:24 pm, Ferenc Wagner <wferi@xxxxxxx> wrote:
>
>> http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/s-resource-ordering.html
>> says that optional ordering is achieved by setting the "kind" attribute
>> to "Optional".  However, the next section
>> http://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/_advisory_ordering.html
>> says that advisory ordering is achieved by setting the "score" attribute
>> to 0.  Is there any difference between an optional and an advisory
>> ordering constraint?
>
> No.  kind=optional is the newer syntax that was intended to be more
> human friendly
>
>> How do nonzero score values influence cluster behaviour, if at all?
>
> score > 0 is equivalent to kind=mandatory
>
>> Or is the kind attribute intended to replace all score settings on
>> ordering constraints?
>
> yes

Great, thanks!  Please consider adding this info to the documentation
(even knowing the history can be comforting, as the old syntax will
never vanish from the internet).  And please also specify what is the
default kind if both of the kind and score attributes are missing.
-- 
Thanks,
Feri.

-- 
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster




[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux