Version 0.2.1

Author: Sharpie

CHANGELOG.md

@@ -2,6 +2,16 @@
 
 All notable changes to this project will be documented in this file.
 
+## [0.2.1] - 2020-01-06
+### Fixed
+
+  - puppet-agent is installed to base images after networking has been
+    configured.
+
+  - Partial fix for the selinux-policy-targeted package causing SELinux
+    to block container operations.
+
+
 ## [0.2.0] - 2020-01-04
 ### Changed
 

README.md

@@ -5,8 +5,8 @@ This module configures a Linux node running SystemD to host a fleet of
 deployment is useful for applying load to Puppet infrastructure servers
 during testing and development.
 
-This module currently only supports PE. Support for Open Source Puppet
-may be added in a future release.
+This module currently only supports PE running on RedHat 7. Support for
+other operating systems and Open Source Puppet may be added in a future release.
 
 The clones run inside `systemd-nspawn` containers that use OverlayFS to
 share a common `puppet-agent` install with container-local modifications.
@@ -15,10 +15,6 @@ the fleet as a whole, or to individual agents by modifying files on the host
 filesystem. The use of SystemD containers also allows both the `puppet`
 and `pxp-agent` services to run, and run "as root" with full functionality.
 
-Currently, RedHat 7 is the only supported operating system for the clones.
-This is expected to change as the module gains support for using `debootstrap`
-and `zypper` to create base images from which the agents are cloned.
-
 
 ## Setup
 
@@ -52,21 +48,42 @@ by 150 MB to determine the number of clones to create.
 
 ### Interacting with Clones
 
-Clones run under `systemd-nspawn` and can be controlled with a variety of tools.
+Individual clones can be controlled using the `puppet-clone-army@<clone name>`
+service template:
+
+```
+systemctl start puppet-clone-army@clone1
+systemctl stop puppet-clone-army@clone1
+```
+
+The entire fleet of clones hosted by a particular node can be controlled
+using the `puppet-clone-army.target` unit:
+
+```
+systemctl start puppet-clone-army.target
+systemctl stop puppet-clone-army.target
+```
+
+`machinectl` can be used to list running clones, as well as gather the
+status of services in an individual clone:
 
-#### Starting and Stopping Clones
+```
+machinectl list
+machinectl status clone1
+```
 
-Individual clones can be started and stopped using the `puppet-clone-army@<clone name>`
-service unit. The entire fleet of clones hosted by a particular node can be
-started and stopped by the `puppet-clone-army.target` unit.
+`machinectl` can also be used to open a shell on a clone:
 
-#### Logging into Running Clones
+```
+machinectl login clone1
+```
 
-All running clones can viewd with `machinectl list` and `machinectl login` can
-be used to open a shell on a clone. The password for the `root` user is set to
-`puppetlabs` and typing `Ctrl-]` three times will close shells created by
+The password for the `root` user is set to `puppetlabs` and typing `Ctrl-]`
+three times will close shells created by `machinectl login`. SELinux may
+have to be set to permissive mode to prevent it from denying access to
 `machinectl login`.
 
+
 #### Editing Filesystems Used by Clones
 
 The module provisions a base OS image under `/var/lib/puppet-clone-army/<base name>`
@@ -80,7 +97,7 @@ while clones are running as this is undefined behavior for OverlayFS. At best,
 the edits will not be visible to the clones.
 
 Stopping a clone by using `puppet-clone-army@<clone name>`, or all clones
-by using `puppet-clone-army.target`, will automatically umount the overlay
+by using `puppet-clone-army.target`, will automatically unmount the overlay
 filesystems and allow for edits to be done safely. Starting the units will
 remount the overlays.
 

manifests/service.pp

@@ -18,6 +18,10 @@
         # by a service unit. This can be corrected by applying some
         # configuration from the container-selinux package.
         #
+        # FIXME: This is sufficient to allow clones to start, stop and
+        #        run, but selinux-policy-targeted still gets in the way
+        #        of `machinectl login` opening shells to clones.
+        #
         # See: https://bugzilla.redhat.com/show_bug.cgi?id=1391118
         # See: https://bugzilla.redhat.com/show_bug.cgi?id=1760146
         ensure_packages(['container-selinux'])

metadata.json

@@ -1,6 +1,6 @@
 {
   "name": "sharpie-clone_army",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "author": "Charlie Sharpsteen",
   "summary": "Manage hordes of containers running puppet-agent for load generation during testing and development",
   "license": "Apache-2.0",