Puppet Enterprise

Puppet Enterprise, or PE, turns Puppet's desired-state model into an operated platform. Puppet code still compiles into a catalog for each node. PE adds the services and controls required to deploy code, classify nodes, inspect results, run work on demand, delegate access, and scale the platform.

PE is not a different configuration language. Its value is the control plane around Puppet.

The primary server

The primary server is the central infrastructure node. A standard installation places PE infrastructure services there.

Puppet Server receives catalog requests and hosts the catalog compiler. The compiler combines code, data, facts, and classification into a catalog for one agent.

The certificate authority accepts and signs certificate requests and publishes revocation information. Certificates establish node identities and protect service communication.

File sync distributes tested code from staging to the live code directory. In larger installations, it also sends that code to compilers.

The PE console provides a web interface for inventory, node groups, reports, jobs, and administration. Treat it as an operational view and control surface, not the source of Puppet code.

PuppetDB and operational evidence

PuppetDB stores current facts and catalogs plus retained event reports. PE services query this data to build inventory, status views, node-group rules, and report analysis.