Skip to content

Commit 9d3e716

Browse files
Merge pull request #235697 from mattmcinnes/patch-73
Update capacity-reservation-create.md
2 parents e50a247 + 54dd63f commit 9d3e716

File tree

1 file changed

+18
-18
lines changed

1 file changed

+18
-18
lines changed

articles/virtual-machines/capacity-reservation-create.md

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -5,31 +5,31 @@ author: bdeforeest
55
ms.author: bidefore
66
ms.service: virtual-machines
77
ms.topic: how-to
8-
ms.date: 11/22/2022
9-
ms.reviewer: cynthn, jushiman
8+
ms.date: 04/24/2023
9+
ms.reviewer: cynthn, jushiman, mattmcinnes
1010
ms.custom: template-how-to, devx-track-azurecli, devx-track-azurepowershell
1111
---
1212

1313
# Create a Capacity Reservation
1414

1515
**Applies to:** :heavy_check_mark: Linux VMs :heavy_check_mark: Windows VMs :heavy_check_mark: Uniform scale set :heavy_check_mark: Flexible scale sets
1616

17-
Capacity Reservation is always created as part of a Capacity Reservation group. The first step is to create a group if a suitable one doesn’t exist already, then create reservations. Once successfully created, reservations are immediately available for use with virtual machines. The capacity is reserved for your use as long as the reservation is not deleted.
17+
Capacity Reservation is always created as part of a Capacity Reservation group. The first step is to create a group if a suitable one doesn’t exist already, then create reservations. Once successfully created, reservations are immediately available for use with virtual machines. The capacity is reserved for your use as long as the reservation isn't deleted.
1818

19-
A well-formed request for Capacity Reservation group should always succeed as it does not reserve any capacity. It just acts as a container for reservations. However, a request for Capacity Reservation could fail if you do not have the required quota for the VM series or if Azure doesn’t have enough capacity to fulfill the request. Either request more quota or try a different VM size, location, or zone combination.
19+
A well-formed request for Capacity Reservation group should always succeed as it doesn't reserve any capacity. It just acts as a container for reservations. However, a request for Capacity Reservation could fail if you don't have the required quota for the VM series or if Azure doesn’t have enough capacity to fulfill the request. Either request more quota or try a different VM size, location, or zone combination.
2020

21-
A Capacity Reservation creation succeeds or fails in its entirety. For a request to reserve 10 instances, success is returned only if all 10 could be allocated. Otherwise, the Capacity Reservation creation will fail.
21+
A Capacity Reservation creation succeeds or fails in its entirety. For a request to reserve 10 instances, success is returned only if all 10 could be allocated. Otherwise, the Capacity Reservation creation fails.
2222

2323

2424
## Considerations
2525

2626
The Capacity Reservation must meet the following rules:
27-
- The location parameter must match the location property for the parent Capacity Reservation group. A mismatch will result in an error.
28-
- The VM size must be available in the target region. Otherwise, the reservation creation will fail.
27+
- The location parameter must match the location property for the parent Capacity Reservation group. A mismatch results in an error.
28+
- The VM size must be available in the target region. Otherwise, the reservation creation fails.
2929
- The subscription must have available quota equal to or more than the quantity of VMs being reserved for the VM series and for the region overall. If needed, [request more quota](../azure-portal/supportability/per-vm-quota-requests.md).
30-
- As needed to satisfy existing quota limits, single VMs can be done in stages. Create a capacity reservation with a smaller quantity and reallocate that quantity of virtual machines. This will free up quota to increase the quantity reserved and add more virtual machines. Alternatively, if the subscription uses different VM sizes in the same series, reserve and redeploy VMs for the first size. Then add a reservation to the group for another size and redeploy the VMs for the new size to the reservation group. Repeat until complete.
31-
- For Scale Sets, available quota will be required unless the Scale Set or its VM instances are deleted, capacity is reserved, and the Scale Set instances are added using reserved capacity. If the Scale Set is updated using blue green deployment, then reserve the capacity and deploy the new Scale Set to the reserved capacity at the next update.
32-
- Each Capacity Reservation group can have exactly one reservation for a given VM size. For example, only one Capacity Reservation can be created for the VM size `Standard_D2s_v3`. Attempt to create a second reservation for `Standard_D2s_v3` in the same Capacity Reservation group will result in an error. However, another reservation can be created in the same group for other VM sizes, such as `Standard_D4s_v3`, `Standard_D8s_v3`, and so on.
30+
- As needed to satisfy existing quota limits, single VMs can be done in stages. Create a capacity reservation with a smaller quantity and reallocate that quantity of virtual machines. This frees up quota to increase the quantity reserved and add more virtual machines. Alternatively, if the subscription uses different VM sizes in the same series, reserve and redeploy VMs for the first size. Then add a reservation to the group for another size and redeploy the VMs for the new size to the reservation group. Repeat until complete.
31+
- For Scale Sets, available quota is required unless the Scale Set or you delete its VM instances, capacity is reserved, and the Scale Set instances are added using reserved capacity. If the Scale Set is updated using blue green deployment, then reserve the capacity and deploy the new Scale Set to the reserved capacity at the next update.
32+
- Each Capacity Reservation group can have exactly one reservation for a given VM size. For example, only one Capacity Reservation can be created for the VM size `Standard_D2s_v3`. Attempt to create a second reservation for `Standard_D2s_v3` in the same Capacity Reservation group results in an error. However, another reservation can be created in the same group for other VM sizes, such as `Standard_D4s_v3`, `Standard_D8s_v3`, and so on.
3333
- For a Capacity Reservation group that supports zones, each reservation type is defined by the combination of **VM size** and **zone**. For example, one Capacity Reservation for `Standard_D2s_v3` in `Zone 1`, another Capacity Reservation for `Standard_D2s_v3` in `Zone 2`, and a third Capacity Reservation for `Standard_D2s_v3` in `Zone 3` is supported.
3434

3535

@@ -95,7 +95,7 @@ Before you create a capacity reservation, you can check the reservation availabl
9595
9696
This group is created to contain reservations for the US East location.
9797
98-
The group in the following example will only support regional reservations, because zones were not specified at the time of creation. To create a zonal group, pass an extra parameter *zones* in the request body:
98+
The group in the following example only supports regional reservations, because zones weren't specified at the time of creation. To create a zonal group, pass an extra parameter *zone* in the request body:
9999
100100
```json
101101
{
@@ -126,7 +126,7 @@ Before you create a capacity reservation, you can check the reservation availabl
126126
}
127127
```
128128
129-
The above request creates a reservation in the East US location for 5 quantities of the D2s_v3 VM size.
129+
The above request creates a reservation in the East US location for five quantities of the D2s_v3 VM size.
130130
131131
132132
### [Portal](#tab/portal2)
@@ -164,7 +164,7 @@ Before you create a capacity reservation, you can check the reservation availabl
164164
-g myResourceGroup
165165
```
166166
167-
1. Now create a Capacity Reservation group with `az capacity reservation group create`. The following example creates a group *myCapacityReservationGroup* in the East US location for all 3 availability zones.
167+
1. Now create a Capacity Reservation group with `az capacity reservation group create`. The following example creates a group *myCapacityReservationGroup* in the East US location for all three availability zones.
168168
169169
```azurecli-interactive
170170
az capacity reservation group create
@@ -174,7 +174,7 @@ Before you create a capacity reservation, you can check the reservation availabl
174174
--zones 1 2 3
175175
```
176176
177-
1. Once the Capacity Reservation group is created, create a new Capacity Reservation with `az capacity reservation create`. The following example creates *myCapacityReservation* for 5 quantities of Standard_D2s_v3 VM size in Zone 1 of East US location.
177+
1. Once the Capacity Reservation group is created, create a new Capacity Reservation with `az capacity reservation create`. The following example creates *myCapacityReservation* for five quantities of Standard_D2s_v3 VM size in Zone 1 of East US location.
178178
179179
```azurecli-interactive
180180
az capacity reservation create
@@ -197,7 +197,7 @@ Before you create a capacity reservation, you can check the reservation availabl
197197
-Location "eastus"
198198
```
199199
200-
1. Now create a Capacity Reservation group with `New-AzCapacityReservationGroup`. The following example creates a group *myCapacityReservationGroup* in the East US location for all 3 availability zones.
200+
1. Now create a Capacity Reservation group with `New-AzCapacityReservationGroup`. The following example creates a group *myCapacityReservationGroup* in the East US location for all three availability zones.
201201
202202
```powershell-interactive
203203
New-AzCapacityReservationGroup
@@ -207,7 +207,7 @@ Before you create a capacity reservation, you can check the reservation availabl
207207
-Name "myCapacityReservationGroup"
208208
```
209209
210-
1. Once the Capacity Reservation group is created, create a new Capacity Reservation with `New-AzCapacityReservation`. The following example creates *myCapacityReservation* for 5 quantities of Standard_D2s_v3 VM size in Zone 1 of East US location.
210+
1. Once the Capacity Reservation group is created, create a new Capacity Reservation with `New-AzCapacityReservation`. The following example creates *myCapacityReservation* for five quantities of Standard_D2s_v3 VM size in Zone 1 of East US location.
211211
212212
```powershell-interactive
213213
New-AzCapacityReservation
@@ -229,7 +229,7 @@ An [ARM template](../azure-resource-manager/templates/overview.md) is a Java
229229
230230
ARM templates let you deploy groups of related resources. In a single template, you can create Capacity Reservation group and Capacity Reservations. You can deploy templates through the Azure portal, Azure CLI, or Azure PowerShell, or from continuous integration/continuous delivery (CI/CD) pipelines.
231231
232-
If your environment meets the prerequisites and you are familiar with using ARM templates, use any of the following templates:
232+
If your environment meets the prerequisites and you're familiar with using ARM templates, use any of the following templates:
233233
234234
- [Create Zonal Capacity Reservation](https://github.com/Azure/on-demand-capacity-reservation/blob/main/ZonalCapacityReservation.json)
235235
- [Create VM with Capacity Reservation](https://github.com/Azure/on-demand-capacity-reservation/blob/main/VirtualMachineWithReservation.json)
@@ -313,7 +313,7 @@ To learn more, go to Azure PowerShell command [Get-AzCapacityReservation](/power
313313
1. From the list, select the Capacity Reservation group name you just created
314314
1. Select **Overview**
315315
1. Select **Reservations**
316-
1. In this view, you will be able to see all the reservations in the group along with the VM size and quantity reserved
316+
1. In this view, you are able to see all the reservations in the group along with the VM size and quantity reserved
317317
---
318318
<!-- The three dashes above show that your section of tabbed content is complete. Do not remove them :) -->
319319

0 commit comments

Comments
 (0)