Getting started with Puppet Enterprise
Puppet Enterprise (PE) is automation software that helps you and your organization be productive and agile while managing your IT infrastructure.
PE is a commercial version of Puppet, our original open source product used by individuals managing smaller infrastructures. It has all the power and control of Puppet, plus a graphical user interface, orchestration services, role-based access control, reporting, and the capacity to manage thousands of nodes. PE incorporates other Puppet-related tools and products to deliver comprehensive configuration management capabilities.
There are two things you need to get started with PE: your content and the Puppet platform.
Content
You develop and store your automation content in a Git repository and upload it onto the Puppet platform. It consists of Puppet code, plan and task code, and Hiera data. You store content in a control repo, which contains bundles of code called modules and references to additional content from external sources, like the Puppet Forge — a repository of thousands of modules made by Puppet developers and the Puppet community.
Puppet platform
The Puppet platform includes the master, compilers, and agents. Use it to assign your desired state to managed systems, orchestrate ad-hoc automation tasks on managed and unmanaged systems, and get reports about configuration automation activity.
In this guide, you will learn how to install PE, add nodes to the console, set up your control repo, and run through an example task of managing websever configurations — using either Apache to manage a *nix machine or IIS to manage a Windows machine.
Before you begin, check out our video for more information about how Puppet works.
-
Install PE
Installing PE sets up a standard installation, which you can use to try out PE with up to 10 nodes or to manage up to 4,000 nodes. -
Add nodes to the inventory
Your inventory is the list of nodes managed by Puppet. Add nodes with agents, agentless nodes that connect over SSH or WinRM, or add network devices like network switches and firewalls. Agent nodes help keep your infrastructure in your desired state. Agentless nodes do not have an agent installed, but can do things like run tasks and plans. -
Add code and set up Code Manager
Set up your control repo, create a Puppetfile, and configure Code Manager so you can start adding content to your PE environments. -
Manage Apache configuration on *nix targets
-
Manage IIS configuration on Windows targets
-
Next steps
Now that you have set up some basic automated configuration management with PE, here are some things to do next: