On Sunday, December 3, 2017 at 10:02:52 AM UTC-5, Martin Alfke wrote:
>
> Hi Ugo, 
>
> > On 03 Dec 2017, at 02:14, Ugo Bellavance <[email protected] <javascript:>> 
> wrote: 
> > 
> > Hi, 
> > 
> > I did google quite a lot about this because we're currently using the 
> EOL'd puppet 3.8 open-source and I'm planning the upgrade to a supported 
> version. I don't understand how the new lifecycle works. Should I upgrade 
> straight to 5 or will puppet 4 supported for a few years?  I have a puppet 
> server and I user hiera for some data. We don't use puppetdb or any other 
> fancy thing.  Our agents are only RHEL and CentOS. 
>
> Regarding EOL and life cycle you can check the following two documents: 
>
> PE support lifecycle: https://puppet.com/misc/puppet-enterprise-lifecycle 
> PE and component versions: 
> https://puppet.com/docs/pe/2017.3/overview/component_versions_in_recent_pe_releases.html
>  
>

Thanks for your quick response, it's the component versions document that I 
couldn't find. I think I'll target the next LTS version.
 

> Upgrades from Puppet 3 to newer versions can be done by directly upgrading 
> to Puppet 5. 
> In the first step you will check your existing code base and make it 
> compatible to Puppet 4 (and later). 
>

I have already started testing my code and modules against Puppet 4.  

In the next step you can enable new features like Data Types (Puppet 4.0 
> and later) and Hiera in Environments (Puppet 4.9 and later) 
>
 
Ok.they're not enabled by default?

If I understand correctly, Puppet switched to PC1 and weird numbers for 
puppet 4 and now Puppet 5 is in puppet5?

Thanks,

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/6f81f07a-cef6-4f99-98e2-a0736e90612c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to