[Pacemaker] crmsh: New syntax for location constraints, suggestions / comments

Michael Schwartzkopff ms at sys4.de
Fri Dec 13 04:55:32 EST 2013

Am Freitag, 13. Dezember 2013, 10:25:48 schrieb Lars Marowsky-Bree:
> On 2013-12-13T10:16:41, Kristoffer Grönlund <kgronlund at suse.com> wrote:
> > Lars (lmb) suggested that we might switch to using the { } - brackets
> > around resource sets everywhere for consistency. My only concern with
> > that would be that it would be a breaking change to the previous crmsh
> > syntax. Maybe that is okay when going from 1.x to 2.0, but it also
> > makes me a bit nervous. :)
> Yes, but consistency and syntax cleanups are important for 2.0.
> Also, then we may finally be able to change the order for collocation
> constraints as well ;-)

Syntax changes: ok. sounds reasonable.

Order for colocations and order constraints: Please don't do it. Everybody got 
use to the ordering as it is now. It also makes sense. Please remember the 
irritations we had moving from heartbeat 2.0 (with XML, shudder) to the new 
pacemaker/crm syntax and constraint orders. I don't want to have that again.

Mit freundlichen Grüßen,

Michael Schwartzkopff

[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64, +49 (162) 165 0044
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 230 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20131213/832b98f0/attachment-0003.sig>

More information about the Pacemaker mailing list