That "howto" section was getting really unwieldy.

Before:

 - Modifying an existing configuration
 - Adding a new module
 - Contributing changes back upstream
 - Running tests
 - Validating Puppet code
 - Listing all hosts under puppet
     - Other ways of extracting a host list
 - Running Puppet everywhere
 - Batch jobs on all hosts
 - Progressive deployment
 - Adding/removing a global admin
 - Examining a Puppet catalog
     - List resources by type
     - View/filter full catalog
 - Troubleshooting
 - Consult the logs of past local Puppet agent runs
     - Running Puppet by hand and logging
     - Finding exported resources with SQL queries
     - Finding exported resources with PuppetDB
 - Password management
 - Getting information from other nodes
     - Exported resources
     - PuppetDB lookups
     - Puppet query language
     - LDAP lookups
     - Hiera lookups
 - Revoking and generating a new certificate for a host
 - Pager playbook
     - [catalog run: PuppetDB warning: did not update since \...\]
     - Problems pushing to the Puppet server
 - Disaster recovery

31 entries, 17 top level, 14 second.

After:

 - Programming workflow
     - Modifying an existing configuration
     - Adding a new module
     - Contributing changes back upstream
     - Running tests
     - Validating Puppet code
 - Puppet tricks
     - Password management
     - Getting information from other nodes
         - Exported resources
         - PuppetDB lookups
         - Puppet query language
         - LDAP lookups
         - Hiera lookups
     - Revoking and generating a new certificate for a host
 - Deployments
     - Listing all hosts under puppet
     - Other ways of extracting a host list
     - Running Puppet everywhere
     - Batch jobs on all hosts
     - Progressive deployment
     - Adding/removing a global admin
 - Troubleshooting
     - Consult the logs of past local Puppet agent runs
     - Running Puppet by hand and logging
     - Finding exported resources with SQL queries
     - Finding exported resources with PuppetDB
     - Examining a Puppet catalog
         - List resources by type
         - View/filter full catalog
 - Pager playbook
     - [catalog run: PuppetDB warning: did not update since \...\]
     - Problems pushing to the Puppet server
 - Disaster recovery

34 entries, 6 top level, 23 second level, 7 third level

The caveat here is that the "third level" here is actually a *fourth*
level, something which we're typically trying to avoid, but in this
case this is not really a possibility.

and puppet itself takes care of reloading multipath when adding a new
alias

See #40363

See: team#40363

Instead of mucking around with the awful iscsi target names we're
stuck with, just go ahead and rescan all the LUNs. There doesn't seem to
be a difference in the delay between rescanning a signal target versus
all targets (almost none).

Also, the previous version failed to include the instructions to
rescan/resize on *all* the cluster nodes, because that doesn't happen
automatically and if the instance is happens to be restarted on another
node, it could fail to boot or worse, cause io errors.

This actually impacts a lot of things, as we need to take those
servers into account when we do SPF and DKIM. Right now, I think the
plan is to grant those servers their own DKIM keys.

Also note the confusion about the name of `relay` which I thought I
already did cover, but now that becomes a little more obvious as we
start to refer to those things.