Skip to content

Commit 702e09f

Browse files
committed
Update README to describe peadm module better
The README should give readers a better sense of what the peadm module is, what it does, what it affects, and what it does not affect. This commit provides an incremental improvement towards that end.
1 parent 0920c87 commit 702e09f

File tree

2 files changed

+50
-13
lines changed

2 files changed

+50
-13
lines changed

CHANGELOG.md

+7-1
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,13 @@
11
# PEADM module
22

33
## Unreleased
4-
- add service module as a dependency
4+
### Summary
5+
6+
Documentation and README update
7+
8+
### Improvements
9+
10+
- Provide a useful overview of the module in the README so that readers can quickly gain a sense of how the module is used, what it affects, and what it does not affect.
511

612
## Release 2.1.1
713
### Summary

README.md

+43-12
Original file line numberDiff line numberDiff line change
@@ -1,38 +1,69 @@
11
# Puppet Enterprise (pe) Administration (adm) Module
22

3-
This Puppet module contains Bolt plans used to deploy and manage Puppet Enterprise infrastructure. Plans are provided to automate common lifecycle activities, in order to increase velocity and reduce the possibility of human error incurred by manually performing these activities.
3+
This Puppet module contains Bolt plans used to deploy and manage Puppet Enterprise infrastructure. Plans are provided to automate common lifecycle activities in order to increase velocity and reduce the possibility of human error incurred by manually performing these activities.
44

55
The peadm module is able to deploy and manage Puppet Enterprise 2019.x Standard, Large, and Extra Large architectures.
66

7+
#### Table of Contents
8+
9+
1. [Expectations](#expectations)
10+
1. [Overview](#overview)
11+
* [What peadm affects](#what-peadm-affects)
12+
* [What peadm does not affect](#what-peadm-does-not-affect)
13+
* [Requirements](#requirements)
14+
3. [Usage](#usage)
15+
4. [Reference](#reference)
16+
5. [Getting Help](#getting-help)
17+
718
## Expectations
819

920
The peadm module is intended to be used only by Puppet Enterprise customers actively working with and being guided by Puppet Customer Success teams—specifically, the Professional Services and Solutions Architecture teams. Independent use is not recommended for production environments without a comprehensive understanding of the peadm module.
1021

11-
## Documentation
22+
## Overview
23+
24+
The normal usage pattern for peadm is as follows.
25+
26+
1. Users set up a Bolt host from which they can run peadm plans. The Bolt host can be any machine that has ssh access to all of the PE nodes.
27+
2. Users run the `peadm::provision` plan to bootstrap a new PE deployment. Depending on the architecture chosen, peadm may create some node groups in the classifier to set parameters on the built-in `puppet_enterprise` module, tuning it for large or extra large architectures.
28+
3. Users use and operate their PE deployment as normal. The peadm module is not used again until the next upgrade.
29+
4. When it is time to upgrade, users run the `peadm::upgrade` plan from their Bolt host to accelerate and aid in the upgrade process.
30+
31+
### What peadm affects
32+
33+
* The `peadm::provision` plan adds a number of custom OID trusted facts to the certificates of PE infrastructure nodes as it deploys them. These trusted facts are later used by the plans to quickly and correctly identify nodes in particular roles.
34+
* Up to four node groups may be created to help configure `puppet_enterprise` class parameters for PE infrastructure roles. The most notable configuration is the designation of compilers as being either "A" or "B" nodes for availability.
35+
36+
### What peadm does not affect
1237

13-
See this README file and any documents in the [documentation](documentation) directory.
38+
* The peadm module is not required to exist or be present outside of the point(s) in time it is used to create a new PE deployment, or upgrade an existing deployment. No new Puppet classes or other persistent content not provided out-of-box by PE itself is applied to PE infrastructure nodes by the peadm module.
39+
* Having used the peadm module to provision or to upgrade a PE deployment is not known to affect or curtail the ability to use any normal, documented PE procedures, e.g. failover to a replica, or manual upgrade of a deployment.
1440

15-
Plans:
41+
### Requirements
42+
43+
* Puppet Enterprise 2019.8.1 or newer (tested with PE 2019.8.1)
44+
* Bolt 2.27.0 or newer (tested with Bolt 2.27.0)
45+
* EL 7, EL 8, Ubuntu 18.04, or Ubuntu 20.04
46+
* Classifier Data enabled. This PE feature is enabled by default on new installs, but can be disabled by users if they remove the relevant configuration from their global hiera.yaml file. See the [PE docs](https://puppet.com/docs/pe/latest/config_console.html#task-5039) for more information.
47+
48+
## Usage
49+
50+
Follow the links below to usage instructions for each peadm plan.
1651

1752
* [Provision](documentation/provision.md)
1853
* [Upgrade](documentation/upgrade.md)
1954
* [Convert](documentation/convert.md)
2055
* [Status](documentation/status.md)
2156

22-
Reference:
57+
## Reference
58+
59+
Additional documentation and information pertaining to various aspects or elements of peadm.
2360

2461
* [PE Architecture Documentation](https://puppet.com/docs/pe/latest/choosing_an_architecture.html)
2562
* [Classification](documentation/classification.md)
2663
* [Architectures](documentation/architectures.md)
2764
* [Testing](documentation/pre_post_checks.md)
2865
* [Docker Based Examples](documentation/docker_examples.md)
2966

30-
## Requirements
31-
32-
Normally, if you are able to use peadm to set up an infrastructure and Puppet agent runs are all working, chances are you met all the requirements and don't have to worry. Sometimes Some notable requirements are highlighted below which may accidentally be adjusted by users, but which architectures deployed by this module rely on. These configuration requirements need to be maintained for the infrastructure to operate correctly.
33-
34-
* Classifier Data needs to be enabled. This feature is enabled by default on new installs, but can be disabled by users if they remove the relevant configuration from their global hiera.yaml file. See the [PE docs](https://puppet.com/docs/pe/latest/config_console.html#task-5039) for more information.
35-
3667
## Getting Help
3768

38-
To get help with issues concerning this module, please make use of [issues](https://github.com/puppetlabs/puppetlabs-peadm/issues) in the project on GitHub.
69+
To get help with issues concerning this module, please make use of [issues](https://github.com/puppetlabs/puppetlabs-peadm/issues) in the project on GitHub.

0 commit comments

Comments
 (0)