gbowerman/azure-myriad

Templates for VM Scale Sets

azure-myriad's Issues

How can we enableIPForwarding to true in vmss ?

I'm struggling to enable IPForwarding on a VMSS for a Virtual Appliance use case.

      "networkProfile": {
        "networkInterfaceConfigurations": [
          {
            "name": "[variables('vmss').nicname]",
            "properties": {
              "primary": true,
              "enableIPForwarding" : true,
              "enableAcceleratedNetworking" : false,

but that doesn't seem to be working

Static Public IP

The example suggests Public IPs are assigned dynamically. Is there a possibility to create static IP instead?

Can I combine VMSS custom image with multiple account storages?

Hi, I want take golden vhd image and spread VMSS creation to multiple storage accounts, is it possible?
I'm trying do it, but no success.
Template does not accept "vhdContainers" with custom image.

{ "type": "Microsoft.Compute/virtualMachineScaleSets", ... "virtualMachineProfile": { "storageProfile": { "osDisk": { ... "image": { "uri": "[parameters('imageSource')]" }

Some demos are not working

I looks that the image was removed.

{
"error": {
"code": "ImageNotFound",
"target": "imageReference",
"message": "The platform image 'Canonical:UbuntuServer:15.04:latest' is not available. Verify that all fields in the storage profile are correct."
}
}

Error deploying autoscale\vmss-win-autoscale

Hi,

I'm trying to deploy the template, but I still getting the error:

ERROR TYPE
Deployment template validation failed: 'The template variable 'storageApi' is not found. Please see https://aka.ms/arm-template/#variables for usage details.'. (Code: InvalidTemplate)

I really need some help on solving this.

Thanks in advance!

why vmss-linux-custionimage always chose the first subnet

"variables": {
"namingInfix": "[toLower(substring(concat(parameters('vmssName'), uniqueString(resourceGroup().id)), 0, 11))]",
"longNamingInfix": "[toLower(parameters('vmssName'))]",
"addressPrefix": "10.1.0.0/16",
"subnetPrefix": "10.1.5.0/24",
"virtualNetworkName": "mtbox-vnet",
"publicIPAddressName": "[concat(variables('namingInfix'), 'pip')]",
"subnetName": "mtupload01",
"loadBalancerName": "[concat(variables('namingInfix'), 'lb')]",
"publicIPAddressID": "[resourceId('Microsoft.Network/publicIPAddresses',variables('publicIPAddressName'))]",
"lbID": "[resourceId('Microsoft.Network/loadBalancers',variables('loadBalancerName'))]",
"natPoolName": "[concat(variables('namingInfix'), 'natpool')]",
"bePoolName": "[concat(variables('namingInfix'), 'bepool')]",
"natStartPort": 50000,
"natEndPort": 50119,
"natBackendPort": 22,
"nicName": "[concat(variables('namingInfix'), 'nic')]",
"ipConfigName": "[concat(variables('namingInfix'), 'ipconfig')]",
"frontEndIPConfigID": "[concat(variables('lbID'),'/frontendIPConfigurations/loadBalancerFrontEnd')]",
"computeApiVersion": "2016-03-30",
"networkApiVersion": "2016-03-30"
},

error output:
Subnet mtsandbox01 is in use by

mtsandbox01 10.1.0.0/24 52 -

mtsandbox02 10.1.2.0/24 251

mtsandbox03 10.1.3.0/24 251

mtsandbox04 10.1.4.0/24 251

mtupload01 10.1.5.0/24 251

i chose mtupload01 subnet.But it is output error

Health Probe Missing

When you use the "Rolling" setting for the UpgradePolicy, you need to specify a Health Probe for the Scale set. This is not configured in the example:

"error": {
"code": "BadRequest",
"message": "Rolling Upgrade mode is not supported for this Virtual Machine Scale Set because a health probe or health extension was not provided."

Looking at this article:
https://docs.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-upgrade#configuring-a-custom-load-balancer-probe-as-application-health-probe-on-a-scale-set

And adding the health probe with the same syntax as there, I still have an error:
"error": {
"details": [],
"code": "NetworkingInternalOperationError",
"message": "An error occurred."