Availability Zones - settings controlled in Nerdio or in Azure?

Avatar
Ron Wortz

When Auto-scale attempts to create a new AVD, I'm frequently seeing the error message “Error: Allocation failed. We do not have sufficient capacity for the requested VM size in this zone.” 

Is there a way to change this so the process tries a different Availability Zone?

We have Azure Capacity Extender enabled and have alternate VM sizes specified if the default isn't available.

I did not build the Nerdio environment and am trying to get a better understanding of some of the foundational things.

We're on Nerdio Manager for Enterprise 7.3.5.

Thank you.


 

0

Comments (1 comment)

Sort by
0
Avatar
Anthony Sequeira

Hi Ron! Thank you so much for posting your great question here. By default, the host pool gets deployed to a region and if that region has multiple AZs (as most do!), then VMs are spun up from whatever AZ has resources. 

What can happen is sometimes people will customize configs (perhaps outside of Nerdio) and end up “pinning” VMs into a single AZ. This can cause resource alerts for obvious reasons. 

I am thrilled to learn you are taking advantage of the Capacity Extender. That is an excellent step. Something else you need to examine is capacity reservations in Azure for compute. These are wonderful and it sounds like just what you need. You reserve your scale out capacity with Azure, and you only pay for what you use (just like before). It is your way of letting Microsoft know - “hey, my VMs are going to scale out, and it would be really nice if you had capacity for me!” 

By the way, AWS, GCP, and Azure are all STARVING for compute in this AI frenzied world! My team inside Nerdio keeps running into resource challenges for compute as well. 

Thanks again for the post and keep up the great work. 

Please sign in to leave a comment.