New features, enhancements, and deprecations

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.4

PE 2016.4: long-term support release

PE 2016.4 is the next consecutive release following PE 2016.2. PE 2016.4 has been designated as a long-term support release for customers who require longer testing periods between PE upgrades. PE 2016.4 will be fully supported (security releases, critical bug fixes, and full customer support) for 24 months from its general availability date.

Corrective change reporting in the PE console

This release introduces corrective change reporting in the PE console. PE now 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”). Use the console’s Overview page to quickly identify nodes that received corrective changes on the last Puppet run, and view details of corrective change events on the Reports page. Corrective change reporting is available only for Puppet agents running PE 2016.4.

Puppet data collection

In order to better understand how you, our customers, are using PE, Puppet Server automatically collects basic data about your PE installation and sends it to Puppet. This data (click here to see what we collect) helps us improve our products and make decisions about the future of PE. If you wish to opt out of sending data to Puppet, see Opting out of Puppet Enterprise analytics.

No-op mode run statuses in the PE console

Reporting in the PE console provides more granularity and context about no-op mode run performance. The Overview page now offers a breakdown of the run status of each node run in no-op mode on the last Puppet run. Filtering by no-op mode run status has also been added to the Reports page. No-op mode reporting is available only for Puppet agents that are running PE 2016.4.

Enhancements in PE 2016.4

Puppet orchestrator enhancements

  • You can now directly enforce change to selections of your infrastructure with the Puppet orchestrator. This version of PE adds the ability to run orchestrator jobs against the following targets:

    • Nodes derived from a Puppet Query Language (PQL) query.
    • A specific node or list of nodes.
    • A single instance or all instances of an application in an environment.
  • Puppet Application Orchestration and the orchestration service are now enabled by default in PE.

Platform enhancements

  • The MCollective metadata refresh cron job has been improved so that when it’s created, it’s created with a random minute. Previously the cron job was created with a fixed runtime of 0, 15, 30, or 45 minutes. Now the load of running the job is spread evenly across time. If you are upgrading from a previous version of PE you can expect to see most agents change this cron resource.

  • When installing PE agents on *nix-based systems, you can pass parameters to the install script to specify configuration settings for inclusion in custom_attributes and extension_requests sections of csr_attributes.yaml. See Passing configuration parameters to the install script for an example.

Console enhancements

  • On the Nodes > Classification page, a hierarchical view replaces the previous alphabetical list.

  • Timestamps in the console can be displayed in local time, with UTC time shown on hover.

  • The Overview page provides a count of nodes on which one or more resources were enforced during the last Puppet run in no-op mode. Enforced resources are created when the noop => false metaparameter setting is used on no-op mode runs.

Code Manager and r10k enhancements

  • We’ve improved support for managing non-module content, such as Hiera data, with Code Manager and r10k. The Puppetfile includes an install_path option you can set for any Git repository you declare. This allows you to declare non-module content in your Puppetfile, and then use the install_path option to install it in your environment outside of the “modules” directory.

  • This release adds the ability to track a control repo branch relative to the environment your Puppetfile is in. This means that when you create new branches from an existing branch of your control repo, you can have environment-specific content directed by the Puppetfile without having to edit the new Puppetfile.

  • The puppet-code command now supports Windows and OSX systems. See puppet-code documentation for usage details.

  • For r10k, you can specify the levels at which r10k purges unmanaged content during deployment. See the purge_levels parameter for details.

PE client tools enhancements

API enhancements

  • When generating an authentication token, you can affix a plain-text, user-specific label to the token. Use this label to more readily refer to the token when working with RBAC API endpoints, or when revoking your own token.

  • The DELETE /roles/<rid> endpoint in the v1 RBAC service API no longer requires the use of the Content-Type header.

Deprecations and removals in PE 2016.4

  • Previously, in the Puppet orchestrator, you could pass an application target without a flag. That behavior is deprecated in this release. The puppet job subcommands now require a flag to run a job on a target. In addition, the --env flag is deprecated. Instead, use --environment or --e.

  • This release deprecates the puppet_enterprise::use_application_services and the puppet_enterprise::profile::orchestrator::use_application_services parameters. PE ignores these parameters and raises a warning if you have set them. To avoid these warnings, remove the parameters from classification. If you need to disable these services, see Disabling application management and Disabling orchestration services.

  • The PE client tools package no longer contains the Razor client. See the Razor installation documentation for instructions on installing the Razor client.

  • Refer to the system requirements for a list of platforms that will soon be end-of-life (EOL).

Puppet release notes

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

Puppet agent release notes

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

PuppetDB release notes

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

Puppet Server release notes

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

↑ Back to top