SKUs using old hardware. Please update to allow for modern SKUs.

mundayn commented 1 year ago

Describe the bug

Can't deploy stack via Panorama.

None of the available SKUs listed in the files are available for deployment in SCUS. The template fails as the SKUs are not available in Availability Zone 2 or 3. I tried all the SKUs. Azure Support advised the SKUs listed are older hardware, please update the allowed SKU list for the deployment.

Azure Support advised: "Unfortunately the original “version 1” A, D and DS series VMs do not run on our latest generation infrastructure, so we are directing customers who request additional quota for these Av1, Dv1 or DSv1 virtual machines to utilize the newer Av2, Dv2/DSv2, Dv3/DSv3, Ev3/ESv3 instead – or better still, to consider moving to the newest Dv4 or Ev4 VMs."

Error: "The requested VM size for resource 'Following SKUs have failed for Capacity Restrictions: Standard_DS3_v2' is currently not available in location 'southcentralus'. Please try another size or deploy to a different location or different zone. See https://aka.ms/azureskunotavailable for details."}]}}

Expected behavior

The ability to use the Panorama Palo Alto Stack Deployment

Current behavior

Deployment fails due to SKU not being able to be deployed in Availability Zone 2 or 3.

Possible solution

Change SKUs in vmseries.json to allow for modern SKUs

Steps to reproduce

Deploy Palo Alto via 'Deployments' and try to deploy a Hub or Inbound stack.

Screenshots

n/a

Context

welcome-to-palo-alto-networks[bot] commented 1 year ago

:tada: Thanks for opening your first issue here! Welcome to the community!

mundayn commented 1 year ago

It seems that South Central US has no availability for any SKUs in Availability Zone 2 or 3. I've gone back to Microsoft.

But you still may want to update the SKU list to match the website: https://docs.paloaltonetworks.com/vm-series/9-1/vm-series-performance-capacity/vm-series-performance-capacity/vm-series-on-azure-models-and-vms

Thanks!

rlewandowski-fl commented 1 year ago

I would like to add to this problem since the latest Panorama Plugin for Azure (versions tested: 4.2.0 and 5.1.1) still references this repo. The selection of 'VM Size' needs to be expanded. We are currently working on a project with a Palo-developed TDD where we would like to use the F8s_v2 VM size (for a PA-VM-500 setup) and cannot select it as an option. For reference the region chosen is centralus.

mundayn commented 1 year ago

@jpeezus @prnair355 @skrish-murt

any comments on this?

PaloAltoNetworks / panorama-orchestration