Add comments

manuscript/ha-docker-swarm/design.md

@@ -86,3 +86,6 @@ Upon restore, docker failed to start on one of the VMs due to local disk space i
 In summary, although I suffered an **unplanned power outage to all of my infrastructure**, followed by a **failure of a third of my hosts**... ==all my platforms are 100% available with **absolutely no manual intervention**==.
 
 [^1]: Since there's no impact to availability, I can fix (or just reinstall) the failed node whenever convenient.
+
+
+## Your comments?

manuscript/ha-docker-swarm/docker-swarm-mode.md

@@ -233,3 +233,6 @@ cd ~
 curl -O https://raw.githubusercontent.com/funkypenguin/geek-cookbook/master/examples/scripts/gcb-aliases.sh
 echo 'source ~/gcb-aliases.sh' >> ~/.bash_profile
 ```
+
+
+## Your comments?

manuscript/ha-docker-swarm/keepalived.md

@@ -68,3 +68,6 @@ That's it. Each node will talk to the other via unicast (no need to un-firewall
 
 1. Some hosting platforms (OpenStack, for one) won't allow you to simply "claim" a virtual IP. Each node is only able to receive traffic targetted to its unique IP. In this case, keepalived is not the right solution, and a platform-specific load-balancing solution should be used. In OpenStack, this is Neutron's "Load Balancer As A Service" (LBAAS) component. AWS and Azure would likely include similar protections.
 2. More than 2 nodes can participate in keepalived. Simply ensure that each node has the appropriate priority set, and the node with the highest priority will become the master.
+
+
+## Your comments?

manuscript/ha-docker-swarm/shared-storage-ceph.md

@@ -200,3 +200,6 @@ Future enhancements to this recipe include:
 
 1. Rather than pasting a secret key into /etc/fstab (which feels wrong), I'd prefer to be able to set "secretfile" in /etc/fstab (which just points ceph.mount to a file containing the secret), but under the current CentOS Atomic, we're stuck with "secret", per https://bugzilla.redhat.com/show_bug.cgi?id=1030402
 2. This recipe was written with Ceph v11 "Jewel".  Ceph have subsequently releaesd v12 "Kraken". I've updated the recipe for the addition of "Manager" daemons, but it should be noted that the [only reader so far](https://discourse.geek-kitchen.funkypenguin.co.nz/u/ggilley) to attempt a Ceph install using CentOS Atomic and Ceph v12 had issues with OSDs, which lead him to [move to Ubuntu 1604](https://discourse.geek-kitchen.funkypenguin.co.nz/t/shared-storage-ceph-funky-penguins-geek-cookbook/47/24?u=funkypenguin) instead.
+
+
+## Your comments?

manuscript/ha-docker-swarm/shared-storage-gluster.md

@@ -162,3 +162,6 @@ Future enhancements to this recipe include:
 
 1. Migration of shared storage from GlusterFS to Ceph ()[#2](https://gitlab.funkypenguin.co.nz/funkypenguin/geeks-cookbook/issues/2))
 2. Correct the fact that volumes don't automount on boot ([#3](https://gitlab.funkypenguin.co.nz/funkypenguin/geeks-cookbook/issues/3))
+
+
+## Your comments?

manuscript/ha-docker-swarm/traefik.md

@@ -144,3 +144,6 @@ Additional features I'd like to see in this recipe are:
 1. Include documentation of oauth2_proxy container for protecting individual backends
 2. Traefik webUI is available via HTTPS, protected with oauth_proxy
 3. Pending a feature in docker-swarm to avoid NAT on routing-mesh-delivered traffic, update the design
+
+
+## Your comments?

manuscript/ha-docker-swarm/vms.md

@@ -83,3 +83,6 @@ After completing the above, you should have:
 [X] 3 x fresh atomic instances, at the latest releases,
     running Docker v1.13 (docker-latest)
 ```
+
+
+## Your comments?