Methods for configuring PE
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 certificate to the allowlist, increase the max-threads setting for
https requests, or configure the number of
PE shares 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 include
and the Puppet Server
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.
Configure settings using the console
The console allows you to use a graphical interface to configure Puppet Enterprise (PE).
Changes in the console 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.
There are two ways to change settings in the console: setting configuration data and editing parameters.
Set configuration data
Configuration data set in the console is used for automatic parameter lookup, the same way that Hiera data is used. Console configuration data takes precedence over Hiera data, but you can combine data from both sources to configure nodes.
- You want to override Hiera data. Data set in the console overrides Hiera data when configured as recommended.
- You want to give someone access to set or change data and they don’t have the skill set to do it in Hiera.
- You simply prefer the console user interface.
- In the console, click Node groups and select the node group that you want to add configuration data to.
On the Configuration data tab, specify a
Class and select a Parameter
You can select from existing classes and parameters in the node group's environment, or you can specify free-form values. Classes aren’t validated, but any class you specify must be present in the node’s catalog at runtime in order for the parameter value to be applied.
When you select a parameter, the Value field is automatically populated with the inherited or default value.
- Optional: Change the default parameter Value.
Parameters are declared resource-style, which means they can be used to override other data; however, this override capability can introduce class conflicts and declaration errors that cause Puppet runs to fail.
- In the console, click Node groups and select the node group you want to add a parameter to.
On the Classes tab, select the class you want to modify, and
select the Parameter you want to add.
The Parameter list shows all parameters available for the selected class in the node group’s environment. When you select a parameter, the Value field is automatically populated with the inherited or default value.
- Optional: Change the default Value.
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 Puppet Enterprise (PE) configuration settings.
pe.conf, but not those set in the PE 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 in Hiera:
Open your default data file in a text editor.
The default location for Hiera data files is:
hiera.yamlconfiguration to change the location of data files (the
datadirsetting) or the path of the common data file (in the
hierarchysection), you'll find the default
.yamlfile in your customized location.
Add your new parameter to the file.
For example, to increase the number of seconds before a node is considered unresponsive from the default of 3600 to 4000, add the following to your default
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
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 primary server:
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.