Skip to content

Commit e00fce3

Browse files
authored
Edit "overview" steps
1 parent 57712af commit e00fce3

File tree

1 file changed

+8
-5
lines changed

1 file changed

+8
-5
lines changed

README.md

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -27,12 +27,15 @@ PEADM is a supported PE module. If you are a PE customer with the standard or pr
2727

2828
## Overview
2929

30-
This is the standard workflow for installing and using PEADM.
30+
This is the standard workflow for using PEADM to deploy a new PE installation.
3131

32-
1. To start using PEADM, [install Bolt](https://www.puppet.com/docs/bolt/latest/bolt_installing) on a jump host with SSH access to all nodes in your installation, and add the PEADM module to your Bolt project.
33-
2. On the Bolt host, run the `peadm::install` plan to bootstrap a new PE installation. For large or extra-large architectures, PEADM creates node groups in the classifier to set relevant parameters in the `puppet_enterprise` module.
34-
3. Use PE as normal. PEADM is not required until your next upgrade.
35-
4. When you are ready to upgrade PE, run the `peadm::upgrade` plan from the Bolt host.
32+
1. [Install Bolt](https://www.puppet.com/docs/bolt/latest/bolt_installing) on a jump host.
33+
2. To create a Bolt project that includes the PEADM module, run:</br>`mkdir <YOUR_PROJECT> && cd <YOUR_PROJECT> && bolt project init <YOUR_PROJECT> --modules puppetlabs-peadm`
34+
3. In the Bolt project directory, update the `inventory.yaml` file with connection information for the servers you plan to use for hosting PE infrastructure.
35+
4. In the Bolt project directory, create a `params.json` file containing the installation parameters.
36+
5. Run `peadm::install --params @params.json`.
37+
38+
Typically after using PEADM to install PE, the module is not required again until you want to automate an upgrade by using the `peadm::upgrade` plan.
3639

3740
### What PEADM affects
3841

0 commit comments

Comments
 (0)