Puppet Enterprise 2018.1

After you've installed Puppet Enterprise (PE), optimize it for your environment by configuring and tuning settings as needed. For example, you might want to add your own certificate to the whitelist, increase the max-threads setting for http and https requests, or configure the number of JRuby instances.

There are two main methods for configuring PE: using the console or adding a key to Hiera.

In general, use the console to apply and configure profile classes starting with puppet_enterprise::profile or when editing or adding any parameters in PE-managed configuration files. Parameter values set in the console override those you've manually set in the configuration files.

Use Hiera to apply and configure classes that aren't profile classes.

Configure settings using the console

In general, use the console to apply and configure profile classes starting with puppet_enterprise::profile or when editing or adding any parameters in PE-managed configuration files.

  1. In the console, click Classification, and select the node group that contains the class you want to work with.
  2. On the Configuration tab, find the class you want to work with, select the Parameter name from the list and edit its value, for example:
    ClassParameterValue
    puppet_enterprise::profile::certificate_authority client_whitelist example.puppetlabs.vm
  3. Click Add parameter and commit changes.

Configure settings with Hiera

Use Hiera to apply and configure classes that aren't profile classes.

You can use Hiera to do things like increase or decrease the number of JRuby instances on the Puppet Server, or tune the number of max_requests_per_instance that will accept requests on the Puppet Server.

In your Hiera default .yaml file, add the setting you're configuring.
The location for the Hiera defaults is /etc/puppetlabs/code/environments/%{environment}/hieradata for *nix and %CommonAppData%\PuppetLabs\code\environments\%{environment}\hieradata for Windows If you customized your hierarchy or datadir, access and edit the default .yaml file accordingly.
Back to top