Upgrading from Puppet 3 to 4 » History » Revision 2
Revision 1 (Dominic Cleal, 05/26/2016 07:34 AM) → Revision 2/23 (Dominic Cleal, 05/26/2016 08:13 AM)
h1. Upgrading from Puppet 3 to 4
+_This wiki page is a work in progress for the release of Foreman 1.12 and is currently incomplete._+
This wiki page is a rough guide on how to upgrade from Puppet 3 to Puppet 4 when using Foreman. It doesn't replace Puppet's own documentation - you need to take both into account, and it's not for the faint-hearted.
Remember, Puppet is a separate piece of software to Foreman. Foreman integrates with Puppet in only a few places (e.g. reports, ENC and smart proxy class imports) but the Foreman installer may have set it up for you initially. Most of the work is changing the Puppet installation and then updating paths and configs in Foreman to suit.
If you're unfamiliar with how Puppet works, then you should consider setting up a new installation and migrating hosts instead.
h2. Planning
Ensure you are running Foreman 1.12 or higher, previous versions are not compatible with Puppet 4, while 1.12 is compatible with both 3 and 4, so carry out that upgrade first. See "Upgrading to Foreman 1.12":http://theforeman.org/manuals/1.12/index.html#3.6Upgrade for more information.
*Start with "Puppet 3.x to 4.x: Get upgrade-ready":https://docs.puppet.com/puppet/latest/reference/upgrade_major_pre.html* - it has many excellent points, including:
* As with any upgrade, the smaller the step, the easier it will be. Ensure you've already upgraded to the latest 3.x release and fixed any deprecations from the release notes before moving to 4. This will save time later.
* Ensure your Puppet modules are going to be compatible with Puppet 4's new ("future") parser
* Plan to upgrade your masters before your agents, because the master can serve older agents, but not the other way around.
* Back up everything, especially SSL keys and certificates.
* Ensure you have enough RAM, Puppet Server defaults to requiring at _least_ 2GB
The guide will assume you're using regular 'puppet' packages either from your OS (or EPEL) or from Puppet Labs repositories. Puppet 4 packages are All-In-One (AIO) packages and work quite differently, introducing lots of new paths for config files and binaries. More information on these at:
* "Welcome to Puppet Collections":https://puppet.com/blog/welcome-to-puppet-collections
* "About Puppet collections and packages":https://docs.puppet.com/puppet/latest/reference/puppet_collections.html
h2. Upgrading
h3. Install new PC1 packages
# Configure the new PC1 repositories with the "Using Puppet Collections":https://docs.puppet.com/guides/puppetlabs_package_repositories.html#using-puppet-collections instructions.
# On EL, run @yum remove puppet-server@ to prevent later conflicts.
# Install the @puppetserver@ package, which should replace @facter@, @puppet@ and @puppet-server@ with @puppetserver@ and @puppet-agent@
h3. Move configs and files to new structure
This section is based on "Puppet 3.x to 4.x: Upgrade Puppet Server":https://docs.puppet.com/puppet/latest/reference/upgrade_major_server.html which goes into far more detail.
# Move or copy any environments from @/etc/puppet/environments@ to @/etc/puppetlabs/code/environments@
# Move or copy all SSL keys and certificates from @/var/lib/puppet/ssl@ to @/etc/puppetlabs/puppet/ssl@
# Remove the Puppet master VirtualHost from Apache at @/etc/httpd/conf.d/25-puppet.conf@ (EL) or @a2dissite 25-puppet@ (Debian/Ubuntu)
# Remove 8140 from the Apache ports in @/etc/httpd/conf/ports.conf@ or @/etc/apache2/ports.conf@
# Update SSL paths in @/etc/httpd/conf.d/05-foreman-ssl.conf@ or @/etc/apache2/sites-available/05-foreman-ssl.conf@, changing @/var/lib/puppet/ssl@ to @/etc/puppetlabs/puppet/ssl@
# Restart httpd/apache2 to free up the port
Config and ENC files:
# @mv /etc/puppet/autosign.conf /etc/puppetlabs/puppet/@
# @mv /etc/puppet/foreman.yaml /etc/puppetlabs/puppet/@
# @mv /etc/puppet/node.rb /etc/puppetlabs/puppet/@
# @cp /etc/puppet/puppet.conf /etc/puppetlabs/puppet/puppet.conf@ and change:
#* in the 'main' section:
#*# @vardir = /opt/puppetlabs/puppet/cache@
#*# @logdir = /var/log/puppetlabs/puppet@
#*# @rundir = /var/run/puppetlabs@
#*# @ssldir = /etc/puppetlabs/puppet/ssl@
#*# @environmentpath = /etc/puppetlabs/code@
#*# @basemodulepath = /etc/puppetlabs/code/environments/common:/etc/puppetlabs/code/modules:/opt/puppetlabs/puppet/modules@
#* in the 'master' section:
#*# @autosign = /etc/puppetlabs/puppet/autosign.conf { mode = 0644 }@
#*# @external_nodes = /etc/puppetlabs/puppet/node.rb@
#*# @ssldir = /etc/puppetlabs/puppet/ssl@