Page MenuHomeClusterLabs Projects

Drop support for require-all in order constraints
Open, NormalPublic

Description

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.

Related Objects

StatusAssignedTask
OpenNone

Event Timeline

nrwahl2 triaged this task as Normal priority.Jun 4 2024, 2:46 AM
nrwahl2 created this task.
nrwahl2 created this object with edit policy "Restricted Project (Project)".
nrwahl2 added a subtask: Restricted Maniphest Task.
nrwahl2 moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.
kgaillot removed a subtask: Restricted Maniphest Task.Jun 4 2024, 10:47 AM
kgaillot added a parent task: Restricted Maniphest Task.

@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

In T829#12444, @nrwahl2 wrote:

@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

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