Configuring Puppet Enterprise
Puppet Enterprise — 2018.1 (LTS)
Important:
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
disable18n,
environment_timeout,
always_retry_plugins, and the
Puppet Server
JRuby
max-active-instances
setting. To verify
PE
configuration defaults, check the
puppet.conf file after installation.
Methods for configuring Puppet Enterprise 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.Configuring and tuning Puppet Server Puppet Enterprise , optimize it for your environment by configuring and tuning Puppet Server settings as needed.Configuring and tuning the console Puppet Enterprise , you can change product settings to customize the console's behavior, adjust to your team's needs, and improve performance.Configuring and tuning PuppetDB Puppet Enterprise , optimize it for your environment by configuring and tuning PuppetDB configuration as needed.Configuring and tuning orchestration PE , you can change some default settings to further configure the orchestrator and pe-orchestration-services.Configuring proxies Configuring Java arguments for Puppet Enterprise ActiveMQ to improve performance in your Puppet Enterprise (PE) deployment. Configuring ulimit for PE services Tuning monolithic installations Writing configuration files Puppet supports two formats for configuration files that configure settings: valid JSON and Human-Optimized Config Object Notation (HOCON), a JSON superset.Analytics data collection Puppet Enterprise . If you want to opt out of providing this data, you can do so, either during or after installing.Static catalogs in Puppet Enterprise Puppet catalog that includes metadata that specifies the desired state of any file resources on a node that have source attributes. Using static catalogs can reduce the number of requests an agent makes to the master.