Methods for configuring Puppet Enterprise
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
https requests, or
configure the number of JRuby
configuration settings used in open source Puppet and documented in the Configuration Reference, however PE defaults for certain settings might differ from the Puppet defaults. Some examples of
settings that have different PE defaults
always_retry_plugins, and the
max-active-instances setting. To verify PE configuration defaults, check the
puppet.conf file after installation.
There are three main methods for configuring PE: using the console, adding a key to Hiera, or editing
pe.conf. Be consistent with the method you choose, unless the situation calls
for you to use a specific method over the others.
pe.confonly — not the console — to specify configuration parameters. Using
pe.confor Hiera ensures that configuration is applied to both your master and replica.
Configure settings using the console
The console allows you to use a graphical interface to configure Puppet Enterprise (PE).
Changes in the console will override your Hiera data and data in
pe.conf. It is usually best to use the console
when you want to:
- Change parameters in profile classes starting with
- Add any parameters in PE-managed configuration files.
- Set parameters that configure at runtime.
To configure settings in the console:
- Click Classification, and select the node group that contains the class you want to work with.
On the Configuration tab, find the class you want to work with,
select the Parameter
name from the list and edit its value.
If you wanted to change the number used to identify the port your console is on from the default 443 to 500, change the parameter value in the following:
Class Parameter Value
- Click Add parameter and commit changes.
- On the nodes hosting the master and console, run Puppet.
Configure settings with Hiera
Hiera is a hierarchy-based method of configuration management that relies on a “defaults, with overrides” system. When you add a parameter or setting to your Hiera data, Hiera searches through the data in the order it was written to find the value you want to change. Once found, it overrides the default value with the new parameter or setting. You can use Hiera to manage your PE configuration settings.
pe.conf, but not those set in the console. It's best to use Hiera when you want to:
- Change parameters in non-profile classes.
- Set parameters that are static and version controlled.
- Configure for high availability.
To configure a setting using Hiera:
Open your default data file.
The default location for Hiera data files is:
hiera.yamlconfiguration to change location for data files (the
datadirsetting) or the path of the common data file (in the
hierarchysection), look for the default
.yamlfile in the customized location.
Add your new parameter to the file in
For example, to increase the number of seconds before a node is considered unresponsive from the default 3600 to 4000, add the following to your
.yamldefault file and insert your new parameter at the end.
To compile changes, run
puppet agent -t
Configure settings in
Puppet Enterprise (PE) configuration data includes any data set in
pe.conf is the file used for most
configuration activities during installation.
pe.conf. Configure settings using
pe.confwhen you want to:
- Access settings during installation.
- Configure for high availability.
To configure settings using
pe.conffile on your master:
Add the parameter and new value you want to set.
For example, to change the proxy in your repo, add the following and change the parameter to your new proxy location.
puppet agent -tNote: If PE services are stopped, run
puppet infrastructure configureinstead of
puppet agent -t.