[ClusterLabs] Planning for Pacemaker 3

[Jehan-Guillaume de Rorthais]

On Wed, 24 Jan 2024 16:47:54 -0600
Ken Gaillot <kgaillot at redhat.com> wrote:
...
> > Erm. Well, as this is a major upgrade where we can affect people's
> > conf and
> > break old things & so on, I'll jump in this discussion with a
> > wishlist to
> > discuss :)
> >   
> 
> I made sure we're tracking all these (links below),

Thank you Ken, for creating these tasks. I subscribed to them, but it seems I
can not discuss on them (or maybe I failed to find how to do it).

> but realistically we're going to have our hands full dropping all the
> deprecated stuff in the time we have.

Let me know how I can help on these subject. Also, I'm still silently sitting on
IRC chan if needed.

> Most of these can be done in any version.

Four out of seven can be done in any version. For the three other left, in my
humble opinion and needs from the PAF agent point of view:

1. «Support failure handling of notify actions»
   https://projects.clusterlabs.org/T759
2. «Change allowed range of scores and value of +/-INFINITY»
   https://projects.clusterlabs.org/T756
3. «Default to sending clone notifications when agent supports it»
   https://projects.clusterlabs.org/T758

The first is the most important as it allows to implement an actual election
before the promotion, breaking the current transition if promotion score doesn't
reflect the reality since last monitor action. Current PAF's code makes a lot of
convolution to have a decent election mechanism preventing the promotion of a
lagging node.

The second one would help removing some useless complexity from some resource
agent code (at least in PAF).

The third one is purely for confort and cohesion between actions setup.

Have a good day!

Regards,