When we create Capacity Reservations for Host Pools in Azure, we specify the number of VMs per Availability Zone. Both the AVD native and Nerdio autoscale do not reference the capacity reservations to confirm they are filled in all AZs before powering on a VM in a zone that would exceed the limit.
Current State:
Demand for 3 VMs, 1 Capacity Reservation in each Availability Zone
AZ 1: 1 Capacity Reservation, 0 VMs powered on
AZ 2: 1 Capacity Reservation, 1 VMs powered on
AZ 3: 1 Capacity Reservation, 2 VMs powered on
End result is paying for 4 VMs while only 3 running
Desired Future State:
Demand for 3 VMs, 1 Capacity Reservation in each Availability Zone
AZ 1: 1 Capacity Reservation, 1 VMs powered on
AZ 2: 1 Capacity Reservation, 1 VMs powered on
AZ 3: 1 Capacity Reservation, 3 VMs powered on
End result is paying for 3 VMs while only 3 running
Comments (0 comments)