Updated from feedback

Author: annatisch

batch/manage-pool/manage-pool.sh batch/manage-pool/manage-pool-linux.sh

@@ -3,49 +3,36 @@
 # Authenticate Batch account CLI session.
 az batch account login -g myresource group -n mybatchaccount
 
-# Create a new Windows PaaS pool with 3 Standard A1 VMs.
-az batch pool create \
-    --id mypool-windows \
-    --os-family 4 \
-    --target-dedicated 3 \
-    --vm-size small \
-
-# We can add some metadata to the pool.
-az batch pool set --pool-id mypool-windows --metadata IsWindows=true VMSize=StandardA1
-
-# Retrieve a list of available IaaS images and node agent SKUs
+# Retrieve a list of available images and node agent SKUs.
 az batch pool node-agent-skus list
 
-# Create a new Linux IaaS pool with an application reference and a start task that will
-# copy the application files to a shared directory. The image reference and node agent SKUs
-# ID can be selected from the ouptputs of the above list command.
+# Create a new Linux pool with a virtual machine configuration. The image reference 
+# and node agent SKUs ID can be selected from the ouptputs of the above list command.
 # The image reference is in the format: {publisher}:{offer}:{sku}:{version} where {version} is
 # optional and will default to 'latest'.
 az batch pool create \
     --id mypool-linux \
     --vm-size Standard_A1 \
     --image canonical:ubuntuserver:16.04.0-LTS \
-    --node-agent-sku-id batch.node.ubuntu 16.04 \
-    --start-task-command-line "cmd /c xcopy %AZ_BATCH_APP_PACKAGE_MYAPP% %AZ_BATCH_NODE_SHARED_DIR%" \
-    --start-task-wait-for-success \
-    --application-package-references myapp
+    --node-agent-sku-id batch.node.ubuntu 16.04
 
-# Now lets resize the IaaS pool to start up some VMs.
+# Now let's resize the pool to start up some VMs.
 az batch pool resize --pool-id mypool-linux --target-dedicated 5
 
-# We can check the status of the pool to see when it has finished resizing
+# We can check the status of the pool to see when it has finished resizing.
 az batch pool show --pool-id mypool-linux
 
 # List the compute nodes running in a pool.
 az batch node list --pool-id mypool-linux
 
 # If a particular node in the pool is having issues, it can be rebooted or reimaged.
 # The ID of the node can be retrieved with the list command above.
-az batch node reboot --pool-id mypool-linux --node-id node1
+# A typical node ID will be in the format 'tvm-xxxxxxxxxx_1-<timestamp>'.
+az batch node reboot --pool-id mypool-linux --node-id tvm-123_1-20170316t000000z
 
 # Alternatively, one or more compute nodes can be deleted from the pool, and any
 # work already assigned to it can be re-allocated to another node.
 az batch node delete \
     --pool-id mypool-linux \
-    --node-list node1 node2 \
+    --node-list tvm-123_1-20170316t000000z tvm-123_2-20170316t000000z \
     --node-deallocation-option requeue

batch/manage-pool/manage-pool-windows.sh

@@ -0,0 +1,36 @@
+#!/bin/bash
+
+# Authenticate Batch account CLI session.
+az batch account login -g myresource group -n mybatchaccount
+
+# We want to add an application package reference to the pool, so first
+# we'll list the available applications.
+az batch application summary list
+
+# Create a new Windows cloud service platform pool with 3 Standard A1 VMs.
+# The pool has an application package reference (taken from the output of the
+# above command) and a start task that will copy the application files to a shared directory.
+az batch pool create \
+    --id mypool-windows \
+    --os-family 4 \
+    --target-dedicated 3 \
+    --vm-size small \
+    --start-task-command-line "cmd /c xcopy %AZ_BATCH_APP_PACKAGE_MYAPP% %AZ_BATCH_NODE_SHARED_DIR%" \
+    --start-task-wait-for-success \
+    --application-package-references myapp
+
+# We can add some metadata to the pool.
+az batch pool set --pool-id mypool-windows --metadata IsWindows=true VMSize=StandardA1
+
+# Let's change the pool to enable automatic scaling of compute nodes.
+# This autoscale formula specifies that the number of nodes should be adjusted according
+# to the number of active tasks, up to a maximum of 10 compute nodes.
+az batch pool autoscale enable \
+    --pool-id mypool-windows \
+    --auto-scale-formula "$averageActiveTaskCount = avg($ActiveTasks.GetSample(TimeInterval_Minute * 15));$TargetDedicated = min(10, $averageActiveTaskCount);"
+
+# We can monitor the resizing of the pool.
+az batch pool show --pool-id mypool-windows
+
+# Once we no longer require the pool to automatically scale, we can disable it.
+az batch pool autoscale disable --pool-id mypool-windows

batch/run-job/run-job.sh

@@ -18,7 +18,7 @@ az batch task create \
     --command-line "cmd /c %AZ_BATCH_APP_PACKAGE_MYAPP#1.0%\\myapp.exe"
 
 # If we want to add many tasks at once - this can be done by specifying the tasks
-# in a JSON file, and passing it into the command. See all_tasks.json for formatting.
+# in a JSON file, and passing it into the command. See tasks.json for formatting.
 az batch task create --job-id myjob --json-file tasks.json
 
 # Now that all the tasks are added - we can update the job so that it will automatically