Open Stack

On 4 Nov 2016, at 06:31, Sam Morrison <sorrison at gmail.com<mailto:sorrison at gmail.com>> wrote:


On 4 Nov. 2016, at 1:33 pm, Emilien Macchi <emilien at redhat.com<mailto:emilien at redhat.com>> wrote:

On Thu, Nov 3, 2016 at 9:10 PM, Sam Morrison <sorrison at gmail.com<mailto:sorrison at 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?


We’re running Puppet 3 at the moment with around 25,000 hosts. There is ongoing work testing Puppet 4 but it takes some time to make sure that the results are the same. The performance is looking promising.

I think we’ll be done with the migration by the time we get to Ocata (currently between Liberty and Mitaka)

Tim


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 <aschultz at redhat.com<mailto:aschultz at 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 at lists.openstack.org<mailto:OpenStack-operators at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


_______________________________________________
OpenStack-operators mailing list
OpenStack-operators at lists.openstack.org<mailto:OpenStack-operators at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators



--
Emilien Macchi

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org<mailto:OpenStack-dev-request at lists.openstack.org>?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20161104/a6a4e8df/attachment.html>