Installing Puppet Enterprise (PE) sets up a standard installation you can use to try out PE with up to 10 nodes or to manage up to 4,000 nodes. From there, you can scale up to the large or extra-large installation as your infrastructure grows, or customize your configuration as needed.
- The primary server: The central hub of activity. It is where Puppet code is compiled to create agent catalogs and where SSL certificates are verified and signed.
- The console: The graphical web user interface. It has configuration and reporting tools.
- PuppetDB: The data store for data generated throughout your Puppet infrastructure.
The Puppet Enterprise (PE) installer uses default settings to install PE infrastructure components on a single node. After installing, you can scale or customize your installation as needed.
Review the Hardware requirements for standard installations to make sure your system capacity can handle the standard PE installation.
Log in as root on your target primary server. If you're installing on a system that
doesn't allow root login, you must use
sudo su - to
complete these steps.
Download the tarball appropriate to
your operating system and architecture.
Tip: To download packages from the command line, run
wget --content-disposition <URL>or
curl -JLO <URL>, using the URL for the tarball you want to download.
To unpack the installation tarball, run:
tar -xf <TARBALL_FILENAME>
From the installer directory, run
./puppet-enterprise-installerand follow the CLI instructions to complete the installation.
- Optional: Restart the shell to use client tool commands.
Log in to the PE console
The Puppet Enterprise (PE) console is a graphical interface where you can manage your infrastructure without relying on the command line.
Open the console by entering the URL
<PRIMARY_HOSTNAME>into your browser. The hostname is your primary server's trusted certificate name.Note: You'll receive a browser warning about an untrusted certificate because you were the signing authority for the console's certificate, and your PE deployment is not known to your browser as a valid signing authority. Ignore this warning and accept the certificate.
On the console login page, log in with the username
adminand the password you created when installing. Keep track of this login because you'll need it later.
Check the status of your primary server
You can run a task in the console to check your primary server's status.
puppet_conf, and you can download more tasks from the Forge or write your own.
- In the console, in the Orchestration section, click Tasks.
- Click Run a task in the upper right corner of the Tasks page.
In the Task field, select
servicebecause you are checking the status of the primary server service.
- Optional: In the Job description field, provide a description. The text you enter here appears on the job list and job details pages.
Under Task parameters, enter parameters and values for
the task. The
servicetask has two required parameters. For action, choose
status. For name, enter puppet.
Under Select targets, select Node
- In the Inventory nodes field, add your primary server's hostname and select it.
Click Run task or Schedule job.
Your task run appears on the Tasks page. To rerun the task, click Run again and choose to rerun the task on all nodes or only the nodes that failed during the initial run.Tip: You can filter run results by task name to find specific task runs.
View the task status and output on the Jobs page after the task is finished running.
Confirm that your primary server's status is running and enabled.
Next, use the console to Add nodes to the inventory.
To learn more about tasks, including how to install them from the Forge and how to write your own tasks, go to Installing tasks and Writing tasks.