#Puppet Enterprise Upgrade Module
This is warning that the adrienthebo namespace version of pe_upgrade is being deprecated in favor of the puppetlabs version. We will be working to retire his forge version in favor of this one. If you previously used the git repo at:
You will need to update your remotes and file PRs against the puppetlabs/ one.
##Description
This module will upgrade Puppet Enterprise.
Travis Test status:
The simplest use of this class downloads the installer from the Puppet Labs servers.
include pe_upgrade
You can also locally host the downloads to conserve bandwidth and speed up deployment time.
To cut down on size, the Puppet Enterprise installer is not included. You will
need to download your operating system specific installers and place the
installers in ${modulename}/files, for instance site-files/files.
You can use the following class definition to download the installer from your Puppet Master.
class { 'pe_upgrade':
version => '2.7.0',
answersfile => "pe/answers/agent.txt.erb",
download_dir => 'puppet:///site-files/pe/2.7.0',
timeout => '3600',
}
In this example, download 'puppet-enterprise-${version}-all.tar.gz' and place it on your webserver.
class { 'pe_upgrade':
version => '2.5.0',
answersfile => "pe/answers/agent.txt.erb",
download_dir => 'http://site.downloads.local/pe/2.7.0',
timeout => '3600',
}
You can use Puppet Dashboard to configure this module. Since Puppet Dashboard doesn't directly support parameterized classes, you can use global variables to configure the module. See the data.pp class documentation for all respected variables.
The PE Upgrader restarts the puppet service as part of the upgrade process. This results in a TERM signal being sent to the puppet process executing the pe_upgrade module. This will look something like this:
notice executed successfully /Stage[main]/Pe_upgrade/Staging::File[puppet-enterprise-2.5.3-all.tar.gz]/Exec[/opt/staging/pe_upgrade/puppet-enterprise-2.5.3-all.tar.gz]/returns /etc/puppetlabs/puppet/modules/staging/manifests/file.pp 83 2012-08-08 20:29 UTC
notice executed successfully /Stage[main]/Pe_upgrade/Staging::Extract[puppet-enterprise-2.5.3-all.tar.gz]/Exec[extract puppet-enterprise-2.5.3-all.tar.gz]/returns /etc/puppetlabs/puppet/modules/staging/manifests/extract.pp 116 2012-08-08 20:30 UTC
notice executed successfully /Stage[main]/Pe_upgrade/Exec[Validate answers]/returns /etc/puppetlabs/puppet/modules/pe_upgrade/manifests/init.pp 137 2012-08-08 20:30 UTC
notice Caught TERM; calling stop Puppet 2012-08-08 20:30 UTC
The "failure" is expected and is not really a failure. Restarting the puppet service can also leave unexecuted changes for the next run. So a "full" upgrade may take two puppet runs.
A default answers file is available at templates/answers/default-agent.txt.erb. It's recommended that you upgrade the master by hand, since that will provide hiera for you, and since 2.5.0 has some new very site specific questions due to the console auth component, it's not really possible to provide a generic answers file.
The puppet-staging module is a prerequisite for this module. You can find it at the following locations:
- Puppet Forge: http://forge.puppetlabs.com/nanliu/staging
- Github: https://github.com/nanliu/puppet-staging
Please view the documentation in the enclosed manifests specific descriptions and usage.
Due to the complexity of upgrading masters, using this module to upgrade a master is possible but not supported out of the box; you'll have to supply your own answers file.