See https://projects.clusterlabs.org/T13#12405. We'll need an XSL transform to, at minimum, drop require-all from order constraints. Ideally, the XSL transform would grab the clone name from the ordering constraint and then add a clone-min="1" meta-attribute to the clone configuration. That may not be possible with XSL, however.
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T829 Drop support for require-all in order constraints | ||
| Restricted Maniphest Task |
Event Timeline
Comment Actions
@kgaillot I had added this as a parent task because we can't drop require-all from ordering constraints until after we've dropped support for rolling upgrades from <2.0.0
Comment Actions
I guess it's a matter of perspective :)
Set the policy of dropping support for rolling upgrades -> various tasks that break rolling upgrades
or
Various tasks that break rolling upgrades -> Dropping support for rolling upgrade is complete
Either approach works for me
Comment Actions
@clumens There's actually a lot of XSL stuff that I had ready to go, that didn't get reviewed in time for 3.0.0. I don't think I got around to this one, because the backlog of "to be reviewed" transforms was already so big.
We'd need to spend time figuring out how to do the transform, and we'd need to bump the schema major version from 4 to 5.
I can't remember whether there is any "compatibility" reason why we'd need to wait until Pacemaker 3.1. You could argue that the cruft of a new schema version and transform pipeline just for this, is overkill though.
I'm looking forward to finishing more of these XSL transforms whenever we're ready though. I did some of the most painful ones to get them out of the way, and they didn't make it in.