Skip to content

Latest commit

 

History

History
77 lines (49 loc) · 4.4 KB

upgrade.markdown

File metadata and controls

77 lines (49 loc) · 4.4 KB
Raw
title layout canonical
PuppetDB 3.1 » Upgrading PuppetDB
default
/puppetdb/latest/upgrade.html

Checking for Updates

PuppetDB's performance dashboard displays the current version in the upper right corner. It also automatically checks for updates and will show a link to the newest version under the version indicator if your deployment is out of date.

Migrating existing data

If you are not planning to change your underlying PuppetDB database configuration prior to upgrading, you don't need to worry about migrating your existing data; PuppetDB will handle this automatically. However, if you do plan to switch to a different database, you should export your existing data prior to changing your database configuration. For more information about the PuppetDB import and export tools, please see the documentation on Migrating Data.

Upgrading with the PuppetDB Module

If you installed PuppetDB with the module, you only need to do the following to upgrade:

  1. Make sure that the puppet master has an updated version of the puppetlabs-puppetdb module installed.
  2. If you imported the official packages into your local package repositories, import the new versions of the PuppetDB and termini packages.
  3. Change the value of the puppetdb_version parameter for the puppetdb or puppetdb::server and puppetdb::master::config classes, unless it was set to latest.
  4. If you are doing a large version jump, trigger a Puppet run on the PuppetDB server before the puppet master server has a chance to do a Puppet run. (It's possible for a new version of the termini to use API commands unsupported by old PuppetDB versions, which would cause Puppet failures until PuppetDB was upgraded, but this should be very rare.)

Manually Upgrading PuppetDB

What to Upgrade

When a new version of PuppetDB is released, you will need to upgrade:

  1. PuppetDB itself
  2. The PuppetDB termini on every puppet master (or every node, if using a standalone deployment)

You should upgrade PuppetDB first. Since PuppetDB will be down for a few minutes during the upgrade and puppet masters will not be able to serve catalogs until it comes back, you should schedule upgrades during a maintenance window during which no new nodes will be brought on line.

If you upgrade PuppetDB without upgrading the PuppetDB termini, your Puppet deployment should continue to function identically, with no loss of functionality. However, you may not be able to take advantage of new PuppetDB features until you upgrade the termini.

Upgrading PuppetDB

On your PuppetDB server: stop the PuppetDB service, upgrade the PuppetDB package, then restart the PuppetDB service.

$ sudo puppet resource service puppetdb ensure=stopped
$ sudo puppet resource package puppetdb ensure=latest
$ sudo puppet resource service puppetdb ensure=running

On Platforms Without Packages

If you installed PuppetDB by running rake install, you should obtain a fresh copy of the source, stop the service, and run rake install again. Note that this workflow is not well tested; if you run into problems, please report them on the PuppetDB issue tracker.

If you are running PuppetDB from source, you should stop the service, replace the source, and start the service as described in the advanced installation guide.

Upgrading the Terminus Plugins

On your puppet master servers: upgrade the PuppetDB termini package, then restart the puppet master's web server:

$ sudo puppet resource package puppetdb-termini ensure=latest

The command to restart the puppet master will vary depending on which web server you are using.

On Platforms Without Packages

Obtain a fresh copy of the PuppetDB source, and follow the instructions for installing the termini.

The command to restart the puppet master will vary depending on which web server you are using.