Open gauthamr05 opened 7 years ago
This template should be edited in many locations to be able to create a VMSS from a user image. The source image should be in the same storage account than the target VHD files for example.
Ok. In such case how do I go ahead and configure this ? As I also have to set up an autoscale rule over this. Hence need to use the image to create VMs dynamically without any manual intervention.
You should try to combine existing templates. For example:
Ok let me give this a try.
Apart from that is it possible to define an autoscaling rule based on the parameter like requests/sec; that came in to the loadbalancer in a VMSS ? What will be the metric for this ? The following link do not give any information on this https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/insights-advanced-autoscale-virtual-machine-scale-sets https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/insights-autoscale-common-metrics
You can find the available metrics you can use on this page: https://docs.microsoft.com/en-us/azure/monitoring-and-diagnostics/insights-autoscale-common-metrics#compute-metrics-for-resource-manager-based-vms It is also mentioned the following:
By default, Resource Manager-based Virtual Machines and Virtual Machine Scale Sets emit basic (host-level) metrics. In addition, when you configure diagnostics data collection for an Azure VM and VMSS, the Azure diagnostic extension also emits guest-OS performance counters (commonly known as "guest-OS metrics"). You use all these metrics in autoscale rules.
I'm trying to create a VMSS using a VM image, was trying to use 201-vmss-linux-nat for this.
While doing this I was facing error as : "code": "StorageAccountTypeNotSupported", "message": "Storage account is of Premium_LRS type. Boot Diagnostics supports Standard_GRS,Standard_LRS,Standard_RAGRS storage account types."
In 201-vmss-linux-nat I have defined 'image.uri' instead of 'vhdContainers' under 'virtualMachineProfile'.
I also tried to create a VM from this image using 101-vm-from-user-image but faced the same error as above.