Configuring Puppet Enterprise
-
Tune infrastructure nodes
Use these guidelines to configure your Puppet Enterprise (PE) installation to maximize use of available system resources (CPU and RAM). -
How to configure PE
After you've installed Puppet Enterprise (PE), you can optimize it by configuring and tuning settings. For example, you might want to add your certificate to the allowlist, increase the max-threads setting forhttp
andhttps
requests, or configure the number of JRuby instances. -
Configure Puppet Server
If needed, you can configure Puppet Server settings to optimize your Puppet Enterprise (PE) installation. -
Configure PuppetDB
If needed, you can configure PuppetDB settings to optimize your Puppet Enterprise (PE) installation. -
Configure security settings
Configure these security settings to ensure your Puppet Enterprise (PE) environment is secure. -
Configure proxies
If you have components with limited (or no) internet access, you can configure proxies at various points in your infrastructure, depending on your connectivity limitations. -
Configure the console
After installing Puppet Enterprise (PE), you can change product settings to customize the PE console's behavior. You can configure many of these settings directly in the console. -
Configure orchestration
After installing PE, you can change some default settings to further configure the orchestrator andpe-orchestration-services
. -
Configure ulimit
As your infrastructure grows and you use Puppet Enterprise (PE) to manage more agents, you might need to increase the number of allowed file handles per client. -
Analytics data collection
Some components automatically collect data about how you use Puppet Enterprise (PE). You can opt out of this data collection during or after installing PE. -
Static catalogs
A catalog is a document that describes the desired state for each resource that Puppet manages on a node. Puppet Enterprise (PE) primary servers typically compile catalogs from manifests of Puppet code. A static catalog is a specific type of Puppet catalog that includes metadata specifying the desired state of any file resources containingsource
attributes pointing topuppet:///
locations on a node.