• Overview
  • Release notes
  • Puppet platform documentation
  • Quick start guides
  • Managing Windows nodes
  • Installing
  • Upgrading
  • Migrating from 3.8
  • Configuring PE
  • Configuring high availability
  • Monitoring infrastructure state
  • Managing nodes
  • Managing access
  • Managing applications
  • Enforcing change with Puppet orchestrator
  • Managing and deploying Puppet code
  • Provisioning with Razor
  • SSL and certificates
  • APIs
  • Managing MCollective
  • Maintenance
  • Troubleshooting
  • Appendix

New features, enhancements, and deprecations

This version is out of date. For current versions, see Puppet Enterprise support lifecycle.

This page describes new features, enhancements, and deprecations in this Puppet Enterprise (PE) release.

For more information about this release, see:

Tip: This PE release contains several components that have additional release notes. Refer to Related release notes for more information.

New features in PE 2016.5.2

PE 2016.5.2 is primarily a release to fix bugs and provide security improvements. For more information, review the resolved issues and security vulnerabilities documentation.

New features in PE 2016.5.1

High availability

High availability for Puppet Enterprise ensures that your system remains operational even if certain infrastructure components become unreachable. With high availability enabled, Puppet runs fail over to a replica if your master or master of masters is unreachable. If your master is permanently disabled, you can promote the replica to serve as the new master.

Note: In this release, we don’t support high availability for split installations – where the master, console, and PuppetDB components are installed on separate machines. Only monolithic installations - with or without compile masters and a master of masters - is supported.

For more information about high availability, see:

Enhancements in PE 2016.5.1

Puppet orchestrator enhancements

  • A new flag, --no-enforce-environment, ensures the orchestrator will ignore the environment set by the --environment flag for agent runs. When you use this flag with the puppet job run command, agents run in the environment specified by the PE Node Manager or their puppet.conf file.

RBAC and activity service enhancements

  • The Run Puppet on agent nodes permission now includes the ability to trigger a Puppet run from the PE console or orchestrator. See RBAC available permissions.

  • The activity service event reporting now includes agent runs that are part of orchestration jobs.

Analytics enhancements

  • We have expanded the data that Puppet Enterprise collects from PE installations to include basic information about agents and console usage. This data is sent to Puppet so we can improve our product. For details about what data is collected and how to opt out, see Puppet Enterprise analytics data collection.

Code Manager enhancements

  • A new status action in the puppet code command verifies from the command line that Code Manager and file sync are responding.

  • Code Manager now provides environment isolation for your resource types. Generated metadata files ensure that each environment uses the correct version of the resource type. For more information, see Code Manager documentation.

Console enhancements

  • Corrective change reporting has been added to the node graph and the Events page in the PE console. PE differentiates between changes driven by updates to Puppet code (“intentional changes”) and changes made by Puppet to return a system to the desired state as defined by Puppet code (“corrective changes”). Corrective change reporting is available only for Puppet agents running PE 2016.4 or later.

  • The node graph and Events page now provide information regarding whether a Puppet run was completed in enforcement or no-op mode, and whether changes were enforced or simulated. No-op mode reporting is available only for Puppet agents running PE 2016.4 or later.

Service restart/reload enhancements

Most of PE’s services (including pe-puppetserver, pe-puppetdb, pe-console-services, and pe-orchestration-services) now have a reload action, which acts like a restart but is significantly faster. If you need to refresh a service after changing its configuration, you can almost always reload it instead of restarting.

To reload a service, run service <NAME> reload instead of service <NAME> restart.

The reload action restarts a service without restarting its underlying Java Virtual Machine (JVM) process. Since starting the JVM is the most time-consuming part of a restart, the speed improvement is very noticeable.

However, some configuration changes require a full restart. These are:

All other config changes are reload-safe.

Security enhancements

  • Use the certregen module, available on the Puppet Forge, to regenerate and redistribute Puppet CA certificates that are expiring soon, as the Puppet CA cert expires after five years. Refer to the module’s README for full instructions.

Monitoring and reporting enhancements

  • A new puppet infrastructure status command displays errors and alerts from PE services, including the activity, classifier, and RBAC services, Puppet Server, and PuppetDB.

Razor enhancements

  • Razor now includes a supported task for installing Fedora 23.
  • Razor now supports Windows installation using international ISOs. When you create a Windows policy to provision non-English systems, use the node_metadata attribute to specify a locale.
  • New commands let you update an existing policy’s repository, broker, or node metadata. For example, without re-creating any policies, you can add a broker to a policy that used the noop broker, or switch to the puppet-pe broker when you upgrade to Puppet Enterprise.
  • In the create-broker command, a new ntpdate_server property in the configuration attribute lets you specify an NTP server. The server is used to synchronize the date and time before installing the agent, which prevents certificate errors.
  • In the modify-node-metadata command, a new force attribute lets you bypass errors in a batch operation with no_replace. Existing keys aren’t modified.

Deprecations and removals in PE 2016.5.1

Support ends for some Puppet Enterprise versions

Puppet is ending support for the following Puppet Enterprise versions on 31 December 2016:

  • 3.8
  • 2015.2
  • 2015.3
  • 2016.1

Puppet Enterprise 2016.2 will no longer be supported after 30 April 2017.

If you’re still using one of these versions, you must move to a supported version, preferably the most recent release.

Platforms reaching end of support

Support soon ends for some platforms, as described in the system requirements.

Puppet release notes

This version of PE includes Puppet version 4.8.1. Refer to the Puppet release notes for more information.

Puppet agent release notes

This version of PE includes Puppet agent version 1.8.2. Refer to the Puppet agent release notes for more information.

PuppetDB release notes

This version of PE includes PuppetDB version 4.2.5. Refer to the PuppetDB release notes for more information.

Puppet Server release notes

This version of PE includes Puppet Server version 2.7.2. Refer to the Puppet Server release notes for more information.

Puppet sites use proprietary and third-party cookies. By using our sites, you agree to our cookie policy.