Methods for configuring Puppet Enterprise

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.

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.
   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
   puppet_enterprise::profile::console	console_ssl_listen_port	[500]

3. Click Add parameter and commit changes.
4. On the nodes hosting the master and console, run Puppet.

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.

1. Open your default data file.
   The default location for Hiera data files is:

   • *nix: /etc/puppetlabs/code/environments/<ENVIRONMENT>/data/common.yaml

   • Windows: %CommonAppData%\PuppetLabs\code\environments\<ENVIRONMENT>\data\common.yaml

   If you customize the hiera.yaml configuration to change location for data files (the datadir setting) or the path of the common data file (in the hierarchy section), look for the default .yaml file in the customized location.
2. Add your new parameter to the file in editor.
   If you wanted to increase the number of seconds before a node is considered unresponsive from the default 3600 to 4000, add the following to your .yaml default file and insert your new parameter at the end.

   Puppet_enterprise::console_services::no_longer_reporting_cutoff: <4000>

3. Compile and view your overrides.

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.

1. Open your pe.conf file on your master.

   /etc/puppetlabs/enterprise/conf.d/pe.conf

2. Add the parameter and new value you want to set.
   If you wanted to change the proxy in your repo, add the following and change the parameter to your new proxy location.

   pe_repo::http_proxy_host": "proxy.example.vlan"

3. Run puppet agent -t
   If PE services are stopped, run puppet infrastructure configure.