VMSS Template for Linux extension and large scale. (#221)

* VMSS Template for Linux extension and large scale.

* Resolving merge conflict.

Author: radhikagupta5

101-vmss-linux-vm/README.md

@@ -6,4 +6,4 @@ PARAMETER RESTRICTIONS
 ======================
 
 vmssName must be 3-10 characters in length. It should also be globally unique across all of AzureStack. If it isn't globally unique, it is possible that this template will still deploy properly, but we don't recommend relying on this pseudo-probabilistic behavior.
-instanceCount must be 100 or less.
+instanceCount must be 20 or less. VM Scale Set supports upto 100 VMs and one should add more storage accounts to support this number.

101-vmss-linux-vm/azuredeploy.json

@@ -2,7 +2,7 @@
     "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json",
     "contentVersion": "1.0.0.0",
     "parameters": {
-        "vmSize": { 
+        "vmSku": { 
             "defaultValue": "Standard_A1",
             "type": "String",
             "metadata": {
@@ -18,10 +18,10 @@
         },
         "instanceCount": {
             "defaultValue": 2,
-            "maxValue": 100,
+            "maxValue": 20,
             "type": "Int",
             "metadata": {
-                "description": "Number of VM instances (100 or less)."
+                "description": "Number of VM instances (20 or less)."
             }
         },
         "adminUsername": {
@@ -183,7 +183,7 @@
                             },
                             "protocol": "tcp",
                             "frontendPortRangeStart": "50000",
-                            "frontendPortRangeEnd": "50099",
+                            "frontendPortRangeEnd": "50019",
                             "backendPort": "3389"
                         }
                     }
@@ -196,7 +196,7 @@
         {
             "type": "Microsoft.Compute/virtualMachineScaleSets",
             "sku": {
-                "name": "[parameters('vmSize')]",
+                "name": "[parameters('vmSku')]",
                 "tier": "Standard",
                 "capacity": "[parameters('instanceCount')]"
             },

101-vmss-windows-vm/README.md

@@ -6,4 +6,4 @@ PARAMETER RESTRICTIONS
 ======================
 
 vmssName must be 3-10 characters in length. It should also be globally unique across all of AzureStack. If it isn't globally unique, it is possible that this template will still deploy properly, but we don't recommend relying on this pseudo-probabilistic behavior.
-instanceCount must be 100 or less.
+instanceCount must be 20 or less. VM Scale Set supports upto 100 VMs and one should add more storage accounts to support this number.

101-vmss-windows-vm/azuredeploy.json

@@ -2,7 +2,7 @@
     "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json",
     "contentVersion": "1.0.0.0",
     "parameters": {
-        "vmSize": { 
+        "vmSku": { 
             "defaultValue": "Standard_A1",
             "type": "String",
             "metadata": {
@@ -18,10 +18,10 @@
         },
         "instanceCount": {
             "defaultValue": 2,
-            "maxValue": 100,
+            "maxValue": 20,
             "type": "Int",
             "metadata": {
-                "description": "Number of VM instances (100 or less)."
+                "description": "Number of VM instances (20 or less)."
             }
         },
         "adminUsername": {
@@ -188,7 +188,7 @@
                             },
                             "protocol": "tcp",
                             "frontendPortRangeStart": "50000",
-                            "frontendPortRangeEnd": "50099",
+                            "frontendPortRangeEnd": "50019",
                             "backendPort": "3389"
                         }
                     }
@@ -201,7 +201,7 @@
         {
             "type": "Microsoft.Compute/virtualMachineScaleSets",
             "sku": {
-                "name": "[parameters('vmSize')]",
+                "name": "[parameters('vmSku')]",
                 "tier": "Standard",
                 "capacity": "[parameters('instanceCount')]"
             },

201-vmss-custom-script-windows/README.md

@@ -6,4 +6,4 @@ PARAMETER RESTRICTIONS
 ======================
 
 vmssName must be 3-10 characters in length. It should also be globally unique across all of AzureStack. If it isn't globally unique, it is possible that this template will still deploy properly, but we don't recommend relying on this pseudo-probabilistic behavior.
-instanceCount must be 100 or less.
+instanceCount must be 20 or less. VM Scale Set supports upto 100 VMs and one should add more storage accounts to support this number.

201-vmss-custom-script-windows/azuredeploy.json

@@ -46,10 +46,10 @@
     },
     "instanceCount": {
       "defaultValue": 2,
-      "maxValue": 100,
+      "maxValue": 20,
       "type": "Int",
       "metadata": {
-        "description": "Number of VM instances (100 or less)."
+        "description": "Number of VM instances (20 or less)."
       }
     },
     "adminUsername": {
@@ -204,7 +204,7 @@
               },
               "protocol": "tcp",
               "frontendPortRangeStart": "50000",
-              "frontendPortRangeEnd": "50099",
+              "frontendPortRangeEnd": "50019",
               "backendPort": "3389"
             }
           }

201-vmss-linux-extention/README.md

@@ -0,0 +1,9 @@
+# Deploy a VM Scale Set of Linux VMs with a custom script extension
+
+This template allows you to deploy a VM Scale Set of Linux VMs with a custom script run on each VM. To connect from the load balancer to a VM in the scale set, you would go to the AzureStack Portal, find the load balancer of your scale set, examine the NAT rules, then connect using the NAT rule you want. For example, if there is a NAT rule on port 50000, you could RDP on port 50000 of the public IP to connect to that VM. Similarly if something is listening on port 80 we can connect to it using port 80.
+
+PARAMETER RESTRICTIONS
+======================
+
+vmssName must be 3-10 characters in length. It should also be globally unique across all of AzureStack. If it isn't globally unique, it is possible that this template will still deploy properly, but we don't recommend relying on this pseudo-probabilistic behavior.
+instanceCount must be 20 or less. VM Scale Set supports upto 100 VMs and one should add more storage accounts to support this number.