On Thu, Nov 3, 2016 at 11:31 PM, Sam Morrison <sorri...@gmail.com> wrote: > > On 4 Nov. 2016, at 1:33 pm, Emilien Macchi <emil...@redhat.com> wrote: > > On Thu, Nov 3, 2016 at 9:10 PM, Sam Morrison <sorri...@gmail.com> wrote: > > Wow I didn’t realise puppet3 was being deprecated, is anyone actually using > puppet4? > > I would hope that the openstack puppet modules would support puppet3 for a > while still, at lest until the next ubuntu LTS is out else we would get to > the stage where the openstack release supports Xenial but the corresponding > puppet module would not? (Xenial has puppet3) > > > I'm afraid we made a lot of communications around it but you might > have missed it, no problem. > I have 3 questions for you: > - for what reasons would you not upgrade puppet? > > > Because I’m a time poor operator with more important stuff to upgrade :-) > Upgrading puppet *could* be a big task and something we haven’t had time to > look into. Don’t follow along with puppetlabs so didn’t realise puppet3 was > being deprecated. Now that this has come to my attention we’ll look into it > for sure. > > - would it be possible for you to use puppetlabs packaging if you need > puppet4 on Xenial? (that's what upstream CI is using, and it works > quite well). > > > OK thats promising, good to know that the CI is using puppet4. It’s all my > other dodgy puppet code I’m worried about. > > - what version of the modules do you deploy? (and therefore what > version of OpenStack) > > > We’re using a mixture of newton/mitaka/liberty/kilo, sometimes the puppet > module version is newer than the openstack version too depending on where > we’re at in the upgrade process of the particular openstack project. > > I understand progress must go on, I am interested though in how many > operators use puppet4. We may be in the minority and then I’ll be quiet :-) > > Maybe it should be deprecated in one release and then dropped in the next? >
So this has been talked about for a while and we have attempted to gauge the 3/4 over the last year or so. Unfortunately with the upstream modules also dropping 3 support, we're kind of stuck following their lead. We recently got nailed when the puppetlabs-ntp module finally became puppet 3 incompatible and we had to finally pin to an older version. That being said we can try and hold off any possible incompatibilities in our modules until either late in this cycle or maybe until the start of the next cycle. We will have several milestone releases for Ocata that will still be puppet 3 compatible (one being next week) so that might be an option as well. I understand the extra work this may cause which is why we're trying to give as much advanced notice as possible. In the current forecast I don't see any work that will make our modules puppet 3 incompatible, but we're also at the mercy of the community at large. We will definitely drop puppet 3 at the start of Pike if we manage to make it through Ocata without any required changes. I think it'll be more evident early next year after the puppet 3 EOL finally hits. Thanks, -Alex > > Cheers, > Sam > > > > > > > My guess is that this would also be the case for RedHat and other distros > too. > > > Fedora is shipping Puppet 4 and we're going to do the same for Red Hat > and CentOS7. > > Thoughts? > > > > On 4 Nov. 2016, at 2:58 am, Alex Schultz <aschu...@redhat.com> wrote: > > Hey everyone, > > Puppet 3 is reaching it's end of life at the end of this year[0]. > Because of this we are planning on dropping official puppet 3 support > as part of the Ocata cycle. While we currently are not planning on > doing any large scale conversion of code over to puppet 4 only syntax, > we may allow some minor things in that could break backwards > compatibility. Based on feedback we've received, it seems that most > people who may still be using puppet 3 are using older (< Newton) > versions of the modules. These modules will continue to be puppet 3.x > compatible but we're using Ocata as the version where Puppet 4 should > be the target version. > > If anyone has any concerns or issues around this, please let us know. > > Thanks, > -Alex > > [0] https://puppet.com/misc/puppet-enterprise-lifecycle > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > > -- > Emilien Macchi > > _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
