Re: [ClusterLabs] Planning for Pacemaker 3
On Thu, 2024-01-25 at 10:31 +0100, Jehan-Guillaume de Rorthais wrote: > On Wed, 24 Jan 2024 16:47:54 -0600 > Ken Gaillot 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). Hmm, that's bad news. :( I don't immediately see a way to allow comments without making the issue fully editable. Hopefully we can find some configuration magic ... > > > 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, > -- Ken Gaillot ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Planning for Pacemaker 3
On Wed, 24 Jan 2024 16:47:54 -0600 Ken Gaillot 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, ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Planning for Pacemaker 3
On Tue, 2024-01-23 at 18:49 +0100, Jehan-Guillaume de Rorthais wrote: > Hi there ! > > On Wed, 03 Jan 2024 11:06:27 -0600 > Ken Gaillot wrote: > > > Hi all, > > > > I'd like to release Pacemaker 3.0.0 around the middle of this > > year. > > I'm gathering proposed changes here: > > > > > > https://projects.clusterlabs.org/w/projects/pacemaker/pacemaker_3.0_changes/ > > > > Please review for anything that might affect you, and reply here if > > you > > have any concerns. > > 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), but realistically we're going to have our hands full dropping all the deprecated stuff in the time we have. Most of these can be done in any version. > 1. "recover", "migration-to" and "migration-from" actions support ? > > See discussion: > > https://lists.clusterlabs.org/pipermail/developers/2020-February/002258.html https://projects.clusterlabs.org/T317 https://projects.clusterlabs.org/T755 > > 2.1. INT64 promotion scores? https://projects.clusterlabs.org/T756 > 2.2. discovering promotion score ahead of promotion? https://projects.clusterlabs.org/T505 > 2.3. make OCF_RESKEY_CRM_meta_notify_* or equivalent officially > available in all > actions > > See discussion: > > https://lists.clusterlabs.org/pipermail/developers/2020-February/002255.html > https://projects.clusterlabs.org/T757 > 3.1. deprecate "notify=true" clone option, make it true by default https://projects.clusterlabs.org/T758 > 3.2. react to notify action return code > > See discussion: > > https://lists.clusterlabs.org/pipermail/developers/2020-February/002256.html > https://projects.clusterlabs.org/T759 > Off course, I can volunteer to help on some topics. > > Cheers! > -- Ken Gaillot ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Planning for Pacemaker 3
Hi there ! On Wed, 03 Jan 2024 11:06:27 -0600 Ken Gaillot wrote: > Hi all, > > I'd like to release Pacemaker 3.0.0 around the middle of this year. > I'm gathering proposed changes here: > > https://projects.clusterlabs.org/w/projects/pacemaker/pacemaker_3.0_changes/ > > Please review for anything that might affect you, and reply here if you > have any concerns. 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 :) 1. "recover", "migration-to" and "migration-from" actions support ? See discussion: https://lists.clusterlabs.org/pipermail/developers/2020-February/002258.html 2.1. INT64 promotion scores? 2.2. discovering promotion score ahead of promotion? 2.3. make OCF_RESKEY_CRM_meta_notify_* or equivalent officially available in all actions See discussion: https://lists.clusterlabs.org/pipermail/developers/2020-February/002255.html 3.1. deprecate "notify=true" clone option, make it true by default 3.2. react to notify action return code See discussion: https://lists.clusterlabs.org/pipermail/developers/2020-February/002256.html Off course, I can volunteer to help on some topics. Cheers! ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Planning for Pacemaker 3
Thanks, I hadn't heard that! On Thu, 2024-01-04 at 01:13 +0100, Valentin Vidić via Users wrote: > On Wed, Jan 03, 2024 at 11:06:27AM -0600, Ken Gaillot wrote: > > I'd like to release Pacemaker 3.0.0 around the middle of this > > year. > > I'm gathering proposed changes here: > > > > > > https://projects.clusterlabs.org/w/projects/pacemaker/pacemaker_3.0_changes/ > > > > Please review for anything that might affect you, and reply here if > > you > > have any concerns. > > Probably best to drop support for rkt bundles as that project has > ended: > > https://github.com/rkt/rkt/issues/4024 > -- Ken Gaillot ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Planning for Pacemaker 3
On Wed, Jan 3, 2024 at 8:09 PM Madison Kelly wrote: > > On 2024-01-03 12:06, Ken Gaillot wrote: > > Hi all, > > I'd like to release Pacemaker 3.0.0 around the middle of this year. > I'm gathering proposed changes here: > > https://projects.clusterlabs.org/w/projects/pacemaker/pacemaker_3.0_changes/ > > Please review for anything that might affect you, and reply here if you > have any concerns. > > Pacemaker major-version releases drop support for deprecated features, > to make the code easier to maintain. The biggest planned changes are > dropping support for Upstart and Nagios resources, as well as rolling > upgrades from Pacemaker 1. Much of the lowest-level public C API will > be dropped. > > Because the changes will be backward-incompatible, we will continue to > make 2.1 releases for a few years, with backports of compatible fixes, > to help distribution packagers who need to keep backward compatibility. > > If this is already a feature, this is going to sound silly... > > Would it be possible to trigger scripts if a resource or stonith device > entered a FAILED state? You can configure an alert to be called for resource events, and ignore the events you don't care about: * https://clusterlabs.org/pacemaker/doc/2.1/Pacemaker_Explained/html/alerts.html * https://clusterlabs.org/pacemaker/doc/2.1/Pacemaker_Administration/html/alerts.html > > -- > wiki - https://alteeve.com/w > cell - 647-471-0951 > work - 647-417-7486 x 404 > > ___ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ -- Regards, Reid Wahl (He/Him) Senior Software Engineer, Red Hat RHEL High Availability - Pacemaker ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Planning for Pacemaker 3
On 2024-01-03 12:06, Ken Gaillot wrote: Hi all, I'd like to release Pacemaker 3.0.0 around the middle of this year. I'm gathering proposed changes here: https://projects.clusterlabs.org/w/projects/pacemaker/pacemaker_3.0_changes/ Please review for anything that might affect you, and reply here if you have any concerns. Pacemaker major-version releases drop support for deprecated features, to make the code easier to maintain. The biggest planned changes are dropping support for Upstart and Nagios resources, as well as rolling upgrades from Pacemaker 1. Much of the lowest-level public C API will be dropped. Because the changes will be backward-incompatible, we will continue to make 2.1 releases for a few years, with backports of compatible fixes, to help distribution packagers who need to keep backward compatibility. If this is already a feature, this is going to sound silly... Would it be possible to trigger scripts if a resource or stonith device entered a FAILED state? -- wiki -https://alteeve.com/w cell - 647-471-0951 work - 647-417-7486 x 404 ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
Re: [ClusterLabs] Planning for Pacemaker 3
On Wed, Jan 03, 2024 at 11:06:27AM -0600, Ken Gaillot wrote: > I'd like to release Pacemaker 3.0.0 around the middle of this year. > I'm gathering proposed changes here: > > https://projects.clusterlabs.org/w/projects/pacemaker/pacemaker_3.0_changes/ > > Please review for anything that might affect you, and reply here if you > have any concerns. Probably best to drop support for rkt bundles as that project has ended: https://github.com/rkt/rkt/issues/4024 -- Valentin ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
