Switch windows VM to East US region

[h-vetinari]

As I said in #157

Move windows VM images to Azure region "East US"; the fact that they're currently in "UK South" was suspected to be the reason for the upload issues to the Anaconda CDN that have plagued us for a long time.

However, this didn't work, but runs into

==> azure-arm.windows: Validating deployment template ...
==> azure-arm.windows:  -> ResourceGroupName : 'pkr-Resource-Group-8aw7orn99w'
==> azure-arm.windows:  -> DeploymentName    : 'kvpkrdp8aw7orn99w'
==> azure-arm.windows: Deploying deployment template ...
==> azure-arm.windows:  -> ResourceGroupName : 'pkr-Resource-Group-8aw7orn99w'
==> azure-arm.windows:  -> DeploymentName    : 'kvpkrdp8aw7orn99w'
==> azure-arm.windows: Getting the certificate's URL ...
==> azure-arm.windows:  -> Key Vault Name        : 'pkrkv8aw7orn99w'
==> azure-arm.windows:  -> Key Vault Secret Name : 'packerKeyVaultSecret'
==> azure-arm.windows:  -> Certificate URL       : 'https://pkrkv8aw7orn99w.vault.azure.net/secrets/packerKeyVaultSecret/1c5601dc059d4bb6b7b025286db5cc46'
==> azure-arm.windows: Setting the certificate's URL ...
==> azure-arm.windows: Validating deployment template ...
==> azure-arm.windows:  -> ResourceGroupName : 'pkr-Resource-Group-8aw7orn99w'
==> azure-arm.windows:  -> DeploymentName    : 'pkrdp8aw7orn99w'
==> azure-arm.windows: ERROR: -> InvalidTemplateDeployment : The template deployment 'pkrdp8aw7orn99w' is not valid according to the validation procedure. The tracking id is '73daf336-def7-40df-9e66-8346d9e3bb36'. See inner errors for details.
==> azure-arm.windows: ERROR:   -> QuotaExceeded : Operation could not be completed as it results in exceeding approved Total Regional Cores quota. Additional details - Deployment Model: Resource Manager, Location: eastus, Current Limit: 10, Current Usage: 0, Additional Required: 16, (Minimum) New Limit Required: 16. Setup Alerts when Quota reaches threshold. Learn more at https://aka.ms/quotamonitoringalerting . Submit a request for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%22***%22,%22command%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22eastus%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22cores%22,%22quotaRequest%22:%7B%22properties%22:%7B%22limit%22:16,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22cores%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ‘Details’ section for deployment to succeed. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/regional-quota-requests
==> azure-arm.windows:
==> azure-arm.windows: unexpected status 400 (400 Bad Request) with error: InvalidTemplateDeployment: The template deployment 'pkrdp8aw7orn99w' is not valid according to the validation procedure. The tracking id is '73daf336-def7-40df-9e66-8346d9e3bb36'. See inner errors for details.

Another issue here is that the respective build job seemingly passed.

[aktech]

Before increase

❯ az vm list-usage --location eastus --output table | grep -i "total regional"
Total Regional Low-priority vCPUs         0               3
Total Regional vCPUs                      0               10

Sent a quota increase request:

❯   az extension add --name quota --yes && \
  az quota update \
    --resource-name cores \
    --scope /subscriptions/df033e15-d7e5-43a0-88b8-95b833d272f9/providers/Microsoft.Compute/locations/eastus \
    --limit-object value=32 \
    --resource-type dedicated
{
  "id": "/subscriptions/df033e15-d7e5-43a0-88b8-95b833d272f9/providers/Microsoft.Compute/locations/eastus/providers/Microsoft.Quota/quotas/cores",
  "name": "cores",
  "properties": {
    "isQuotaApplicable": true,
    "limit": {
      "limitObjectType": "LimitValue",
      "limitType": "Independent",
      "value": 32
    },
    "name": {
      "localizedValue": "Total Regional vCPUs",
      "value": "cores"
    },
    "properties": {},
    "unit": "Count"
  },
  "type": "Microsoft.Quota/Quotas"
}

After increase

❯ az vm list-usage --location eastus --output table --subscription df033e15-d7e5-43a0-88b8-95b833d272f9 | grep -i "total regional"
Total Regional Low-priority vCPUs         0               3
Total Regional vCPUs                      0               32

We'd further need to increase it to support parallel CI runner VMs, but this will do for the packer image build.

[h-vetinari]

Thanks a lot @aktech! Unfortunately, the new quota does not seem to have taken effect. After merging #165, I still get

==> azure-arm.windows: ERROR: -> InvalidTemplateDeployment : The template deployment 'pkrdp2cuae1pvob' is not valid according to the validation procedure. The tracking id is '850f4dd2-8603-4df8-8028-26fc4362696f'. See inner errors for details.
==> azure-arm.windows: ERROR:   -> QuotaExceeded : Operation could not be completed as it results in exceeding approved standardDADSv5Family Cores quota. Additional details - Deployment Model: Resource Manager, Location: eastus, Current Limit: 0, Current Usage: 0, Additional Required: 16, (Minimum) New Limit Required: 16. Setup Alerts when Quota reaches threshold. Learn more at https://aka.ms/quotamonitoringalerting . Submit a request for Quota increase at https://aka.ms/ProdportalCRP/#blade/Microsoft_Azure_Capacity/UsageAndQuota.ReactView/Parameters/%7B%22subscriptionId%22:%22***%22,%22command%22:%22openQuotaApprovalBlade%22,%22quotas%22:[%7B%22location%22:%22eastus%22,%22providerId%22:%22Microsoft.Compute%22,%22resourceName%22:%22standardDADSv5Family%22,%22quotaRequest%22:%7B%22properties%22:%7B%22limit%22:16,%22unit%22:%22Count%22,%22name%22:%7B%22value%22:%22standardDADSv5Family%22%7D%7D%7D%7D]%7D by specifying parameters listed in the ‘Details’ section for deployment to succeed. Please read more about quota limits at https://docs.microsoft.com/en-us/azure/azure-supportability/per-vm-quota-requests

Also, would be nice to fail the GHA for building the VM if that happens

[h-vetinari]

Looks like there's more than one quota at play!

Before:

exceeding approved Total Regional Cores quota

Now:

exceeding approved standardDADSv5Family Cores quota

[aktech]

Looks like quota not available for the resource currently, let me try again.

❯   az quota update \
    --resource-name standardDADSv5Family \
    --scope /subscriptions/df033e15-d7e5-43a0-88b8-95b833d272f9/providers/Microsoft.Compute/locations/eastus \
    --limit-object value=32 \
    --resource-type dedicated
(QuotaNotAvailableForResource) Request failed.
Code: QuotaNotAvailableForResource
Message: Request failed.