Hello, I don't agree, we should continue on the chosen path of not supporting Puppet 5 in the Victoria release. We've had Puppet 6 support since I introduced the testing for it in 2018 back then we ran Puppet 5 and Puppet 6 on every commit until we deemed it pretty redundant and moved Puppet 6 jobs to experimental while keeping the Puppet 6 syntax and unit jobs. We've never claimed that Puppet OpenStack is going to support downstream OS repackaging of Puppet, even though RDO/TripleO does the same we've always tested Puppet with upstream versions for our testing, only Debian has skipped that and testing with downstream packages. I don't think keeping Puppet 5 jobs for Debian would be a good idea because it would block the whole idea of moving to Puppet 6 in the first place. Puppet 5 will be EOL one month after Victoria release, while I highly doubt that we will introduce changes that will break Puppet 5 in the Victoria cycle we would like to start looking forwarding instead of being stuck with all the legacy stuff (now that we've moved to CentOS 8 as well), after being active in the project a longer time we've gone for semi-broken maintenance-mode-only to more active with keeping everything up to date and following the changes of the OpenStack community. Thanks to a number of contributors, thank you everyone! There is a lot things that we could do in Puppet OpenStack (but hey, resources to perform them is scarce) just to give an example the new Resource API [1] (whether it be with or without the usage of OpenStack CLI). If anybody ever want something to do I have nice big list of things that we could do, I've posted an old version of it in an email to this mailing list during PTL nominations. Best regards [1] https://review.opendev.org/#/q/topic:new-providers+(status:open+OR+status:me...) ________________________________________ From: Thomas Goirand <zigo@debian.org> Sent: Saturday, May 9, 2020 5:41 PM To: openstack-discuss@lists.openstack.org Subject: Re: [puppet] Puppet 5 is officially unsupported in Victoria release On 5/8/20 10:24 PM, Jeremy Stanley wrote:
On 2020-05-08 22:06:14 +0200 (+0200), Thomas Goirand wrote:
On 5/8/20 7:58 PM, Jeremy Stanley wrote: [...]
whether the Puppet OpenStack team wants the burden of spending a cycle targeting support for a Puppet version which will be EOL the month after the release (especially given deployment projects usually release as much as a month after the coordinated release already).
I don't see how this can be a burden. It's not as if the language changed that much and if there was major incompatibilities. [...]
Well, it does mean keeping those modules working with two major versions of Puppet which, speaking from past experience, is not easy (and a big part of why we decided to replace all our orchestration and configuration management in OpenDev with something other than Puppet after the Puppet 3->4->5 transition).
My understanding is that adding compatibility to a new version isn't easy, but keeping compat backward isn't that hard.
How much of a strain that is on the Puppet OpenStack team, I can't say.
It means at least keeping one CI job running with puppet 5. This could be the Debian one if I succeed in restoring Debian as a voting set of jobs. Cheers, Thomas Goirand (zigo)