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.
Ensure your system capacity can manage a PE installation by reviewing the hardware requirements for standard installations.
A standard PE installation consists of these components installed on a single node:
- The primary server: the central hub of activity, where Puppet code is compiled to create agent catalogs, and where SSL certificates are verified and signed.
- The console: the graphical web interface, which features configuration and reporting tools.
- PuppetDB: the data store for data generated throughout your Puppet infrastructure.
Installation uses default settings to install all of the PE infrastructure components on a single node. After installing, you can scale or customize your installation as needed.
sudo su -
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.
Unpack the installation tarball:
tar -xf <TARBALL_FILENAME>
From the installer directory, run the installer and follow the CLI instructions
to complete your installation:
- Optional: Restart the shell in order to use client tool commands.
Log into the PE console
The console is a graphical interface where you can manage your infrastructure without relying on the command line.
To log in for the first time:
Open the console by entering the URL <PRIMARY_HOSTNAME> into your browser, where
hostname is the trusted certificate name of your primary server.
Note: You'll receive a browser warning about an untrusted certificate because you were the signing authority for the console's certificate, and your Puppet Enterprise deployment is not known to your browser as a valid signing authority. Ignore the warning and accept the certificate.
On the login page for the console, log in with the username
adminand the password you created when installing. Keep track of this login as you will use it later.
Check the status of your primary server
You can run a task to check the status of your primary server in the console.
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 the hostname of your primary server 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 on the nodes that failed during the initial run.Tip: Filter run results by task name to find specific task runs.
The status of your primary server should be “running” and “enabled”. To learn more about tasks, including how to install them from the Forge or how to write your own, visit the Installing tasks and Writing tasks sections of the docs.
Next, use the console to add nodes to your inventory.