[Pacemaker] About the difference in handling of "sequential".

Kristoffer Grönlund kgronlund at suse.com
Tue Feb 18 20:09:05 EST 2014

On Wed, 19 Feb 2014 11:57:29 +1100
Andrew Beekhof <andrew at beekhof.net> wrote:

> It appears Yan did this on purpose.
> The reason would likely be that this set is for use in a location
> constraint (not ordering or colocation). And in particular, it is
> creating a fake set for resources using the same template - so there
> is no reason to think they should be ordered.
> So: 
> 1. sequential should _always_ default to true
> 2. please report it to me if you find somewhere that does not
> 3. since template_to_set() is creating (copying) a fake set, there is
> no conflict with 1.

Thanks, that's exactly the information I needed. :)

// Kristoffer Grönlund
// kgronlund at suse.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140219/f9e7936a/attachment-0003.sig>

More information about the Pacemaker mailing list