Improve autotest system

docs/dashboard.md

@@ -91,6 +91,8 @@ The goo.gl URL expands to:
 
   (You will have to work around the TLS certificate validation warning)
 
+<!-- ```open https://node1:3xxxx/``` -->
+
 ]
 
 - We have three authentication options at this point:

docs/kubectlexpose.md

@@ -69,6 +69,8 @@ The `LoadBalancer` type is currently only available on AWS, Azure, and GCE.
   kubectl get pods -w
   ```
 
+<!-- ```keys ^C``` -->
+
 ]
 
 The `-w` option "watches" events happening on the specified resources.

docs/kubectlscale.md

@@ -10,6 +10,8 @@
   kubectl get deployments -w
   ```
 
+<!-- ```keys ^C``` -->
+
 - Now, create more `worker` replicas:
   ```bash
   kubectl scale deploy/worker --replicas=10

docs/ourapponkube.md

@@ -348,6 +348,8 @@ We should now see the `worker`, well, working happily.
 
 - Open the web UI in your browser (http://node-ip-address:3xxxx/)
 
+<!-- ```open http://node1:3xxxx/``` -->
+
 ]
 
 --

docs/prereqs-k8s.md

@@ -65,6 +65,8 @@ class: extra-details
 - Go to [container.training](http://container.training/) to view these slides
 - Join the chat room on @@CHAT@@
 
+<!-- ```open http://container.training/``` -->
+
 ]
 
 ---
@@ -73,6 +75,12 @@ class: pic, in-person
 
 ![You get five VMs](you-get-five-vms.jpg)
 
+<!--
+```bash
+kubectl get all -o name | grep -v services/kubernetes | xargs -n1 kubectl delete
+```
+-->
+
 ---
 
 class: in-person
@@ -102,11 +110,7 @@ done
   ```
 - Type `exit` or `^D` to come back to node1
 
-<!--
-```keys
-exit
-```
--->
+<!-- ```keys exit``` -->
 
 ]
 

docs/rollout.md

@@ -79,6 +79,8 @@
   kubectl get deployments -w
   ```
 
+<!-- ```keys ^C``` -->
+
 - Update `worker` either with `kubectl edit`, or by running:
   ```bash
   kubectl set image deploy worker worker=$REGISTRY/worker:$TAG

docs/sampleapp.md

@@ -264,6 +264,8 @@ class: extra-details
 
 - In your browser, you need to enter the IP address of your node
 
+<!-- ```open http://node1:8000``` -->
+
 ]
 
 You should see a speed of approximately 4 hashes/second.
@@ -316,9 +318,25 @@ class: extra-details
 
 - run `top` to see CPU and memory usage (you should see idle cycles)
 
-- run `vmstat 3` to see I/O usage (si/so/bi/bo)
+<!--
+```bash
+top
+```
+
+```keys ^C```
+-->
+
+- run `vmstat 1` to see I/O usage (si/so/bi/bo)
   <br/>(the 4 numbers should be almost zero, except `bo` for logging)
 
+<!--
+```bash
+vmstat 1
+```
+
+```keys ^C```
+-->
+
 ]
 
 We have available resources.