added 1.10.1 release notes, help messages, and what's new

content/en/docs/Anka Build Cloud/Controller and Registry/Setup/connect-nodes.md

@@ -40,7 +40,7 @@ Flags:
   -M, --capacity-mode string        Set the capacity mode (resource or number) the Node will use when pulling jobs from the Anka Cloud Cluster queue. 'resource' will look at available resources (see --vcp-override and --ram-override) / 'number' will only accept if --max-vm-count isn't already met (default "number")
   -C, --cert string                 Specify the path to the Node's certificate file (PEM/X509)
   -K, --cert-key string             Specify the path to the Node's certificate key file (PEM/X509)
-      --enable-vm-monitor           Enable VM monitoring
+      --enable-vm-monitor           Enabled unresponsive VM monitoring. This will throw a failure when the VM becomes unresponsive for longer than the --vm-stuck-timeout
   -f, --force-no-sudo               Force the anka_agent to start without sudo
   -g, --global                      DEPRECATED! Install agent into system domain
   -G, --groups string               Specify group name (or multiple names sepearated by ',') to add the current Node to
@@ -59,8 +59,8 @@ Flags:
       --skip-tls-verification       Skip TLS verification
   -t, --tls                         Enable TLS for communicating with the Anka Cloud Cluster
   -V, --vcpu-override int           Set the max vcpus that this Node can handle. (default: {current physical cpu count} * 2)
-      --vm-stuck-delay duration     Delay between vm is stuck health check
-      --vm-stuck-timeout duration   VM response timeout to consider a vm as stuck
+      --vm-stuck-delay duration     The time between unresponsive VM checks (default: 30s - Duration examples: 3500s, 20m, 5h)
+      --vm-stuck-timeout duration   The time to wait until the VM is considered unresponsive (default: 10s - Duration examples: 3500s, 20m, 5h)
   ```
 
 ## Disjoining

content/en/docs/Release Notes/_index.md

@@ -11,10 +11,8 @@ description: >
 
 ## Current Versions
 
-### Anka Build Cloud Controller & Registry 1.10.0 - August 5, 2020
-- Bug Fix : Central Logging was preventing nodes from joining
-- Bug Fix : Certificates with a space in the Organization (O=) were not supported when trying to set permission groups.
-- Bug Fix : Controller crashes if client tries to show permission group after deletion
+### Anka Build Cloud Controller & Registry 1.10.1 - August 20, 2020
+- New feature : Unresponsive VM monitoring with `ankacluster join --enable-vm-monitor`
 
 ### TeamCity Plugin version 1.7.1 - July 7, 2020
 - Bug Fix : Long-running threads were being created
@@ -64,6 +62,11 @@ description: >
 
 ## Previous Versions
 
+### Anka Build Cloud Controller & Registry 1.10.0 - August 5, 2020
+- Bug Fix : Central Logging was preventing nodes from joining
+- Bug Fix : Certificates with a space in the Organization (O=) were not supported when trying to set permission groups.
+- Bug Fix : Controller crashes if client tries to show permission group after deletion
+
 ### Anka Build Cloud Controller & Registry 1.9.1 - June 23, 2020
 - Bug Fix : When a user sets a custom img_lib_dir location, the anka agent doesn't calculate disk usage for the new location
 

content/en/docs/Whats New/_index.md

@@ -7,6 +7,29 @@ description: >
   Description of new Anka software features
 ---
 
+## What's New in Anka Build Cloud Controller & Registry Version 1.10.1
+
+### Unresponsive VM Monitor
+
+Rarely we see certain dependencies installed inside of VMs causing the entire VM to become unresponsive. Unresponsive or "stuck" VMs can run indefinitely and therefore cause CI/CD jobs to run until they hit timeouts. This is a bad experience for users, so we've added a feature which constantly checks whether or not the command-line inside of VM is responding to `pwd`. You can enable it when you join your Node to the Anka Cloud with: `sudo ankacluster join --enable-vm-monitor http://anka.controller:8090`
+
+You can see the flags and options with:
+
+```
+❯ ankacluster join --help
+Joins the current machine to one or many Anka Build Cloud Controllers
+
+Usage:
+  ankacluster join CONTROLLER_ADDRESS[,CONTROLLER_ADDRESS2] [flags]
+
+Flags:
+...
+  --enable-vm-monitor           Enabled unresponsive VM monitoring. This will throw a failure when the VM becomes unresponsive for longer than the --vm-stuck-timeout
+...
+  --vm-stuck-delay duration     The time between unresponsive VM checks (default: 30s - Duration examples: 3500s, 20m, 5h)
+  --vm-stuck-timeout duration   The time to wait until the VM is considered unresponsive (default: 10s - Duration examples: 3500s, 20m, 5h)
+```
+
 ## What's New in Anka Build Cloud Controller & Registry Version 1.9.0
 
 ### Track MAC Addresses for VMs and prevent rare collision situations