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 three main methods for configuring PE: using the console, adding a key to Hiera, or editing pe.conf
. For the most part, you can choose to use whatever
method you want, but sometimes one might be better than another depending on the
situation. In general, try to stay as consistent as possible.
pe.conf
only — not the console — to specify
configuration parameters. Using pe.conf
or Hiera ensures that configuration is applied to both
your master and replica. Configure settings using the console
Using the console to change parameters is the most user-friendly way of configuring Puppet Enterprise (PE) because you can use a graphical interface in order to make changes.
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
puppet_enterprise::profile
. - Add any parameters in PE-managed configuration files.
- Set parameters that configure at runtime.
To configure settings in the console, do the following:
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.
pe.conf
, but not 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, do the following:
Configure settings in pe.conf
Puppet Enterprise (PE) configuration data includes any data set in
/etc/puppetlabs/enterprise/conf.d/
but
pe.conf
is the file used for most
configuration activities during installation.
pe.conf
. Configure settings using pe.conf
when you want to: - Quickly access settings during installation.
- Configure for high availability.
Keep in mind, you might notice a nodes/
directory with files named after nodes in your PE infrastructure. These files
are created automatically for you to keep your PE configuration data in sync with your user data.