Been through a similar upgrade myself.  The first step would be to spin up 
a new puppet master running Puppet Server.  You can copy over the SSL dir 
from your old/current master to avoid SSL errors on the agents.  For 
testing you'll want to make sure your manifests work correctly using the 
future parser, that can be enabled in the puppet.conf file on the agents.  
Setting up a separate environment for testing is also recommended.

Puppet Server will work with 3.7 clients so once you have a manifest that 
compiles correctly you can just point the agents to the new master's IP.


On Wednesday, October 11, 2017 at 8:07:13 AM UTC-7, Salty Old Cowdawg wrote:
>
> About three years ago (4 years ago?) I deployed a Puppet infrastructure 
> for my company and department based on FOSS Puppet 3.7.   Given that's been 
> deprecated of course I'm very much looking to migrate to Puppet 4.   
> Besides for about three months I worked for another company and got spoiled 
> by Puppet 4. 
>
> So I'm back at my old digs and assessing what it will take to go from P3 
> to P4.   Here are some of the things I have to think about
>
> 1) the migration needs to be fully automated both on the server end and 
> the client end. 
> 2) no really.... this is going to be done by operations personnel who have 
> a low threshold of fright for Puppet in spite of my best efforts to 
> desensitize them.
> 3) There is as penetrable firewall between me (developer) and the Puppet 
> infrastructure servers and clients so I cannot personally intervene
>
> Anybody out there been through this pain and have any suggestions and 
> pointers on how to make this happen with minimal "breakage?" 
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/8c276e2e-e692-43ec-9560-06f29138559c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to