You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-machine-scale-sets/virtual-machine-scale-sets-instance-mix.md
+32-32Lines changed: 32 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: Use multiple Virtual Machine sizes with Instance Flexibility
3
-
description: Use multiple Virtual Machine sizes in a scale set using Instance Flexibility. Optimize deployments using allocation strategies.
2
+
title: Use multiple Virtual Machine sizes with Instance Mix
3
+
description: Use multiple Virtual Machine sizes in a scale set using Instance Mix. Optimize deployments using allocation strategies.
4
4
author: brittanyrowe
5
5
ms.author: brittanyrowe
6
6
ms.topic: conceptual
@@ -9,13 +9,13 @@ ms.date: 06/26/2024
9
9
ms.reviewer: jushiman
10
10
---
11
11
12
-
# Use Multiple Virtual Machine Sizes with Instance Flexibility (Preview)
12
+
# Use Multiple Virtual Machine Sizes with Instance Mix (Preview)
13
13
> [!IMPORTANT]
14
-
> Instance Flexibility for Virtual Machine Scale Sets with Flexible Orchestration Mode is currently in preview. Previews are made available to you on the condition that you agree to the [supplemental terms of use](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). Some aspects of this feature may change prior to general availability (GA).
14
+
> Instance Mix for Virtual Machine Scale Sets with Flexible Orchestration Mode is currently in preview. Previews are made available to you on the condition that you agree to the [supplemental terms of use](https://azure.microsoft.com/support/legal/preview-supplemental-terms/). Some aspects of this feature may change prior to general availability (GA).
15
15
16
-
Instance Flexibility enables you to specify multiple different Virtual Machine (VM) sizes in your Virtual Machine Scale Set with Flexible Orchestration Mode, and an allocation strategy to further optimize your deployments.
16
+
Instance Mix enables you to specify multiple different Virtual Machine (VM) sizes in your Virtual Machine Scale Set with Flexible Orchestration Mode, and an allocation strategy to further optimize your deployments.
17
17
18
-
Instance Flexibility is best suited for workloads that are flexible in compute requirements and can be run on various different sized VMs. Using Instance Flexibility you can:
18
+
Instance Mix is best suited for workloads that are flexible in compute requirements and can be run on various different sized VMs. Using Instance Mix you can:
19
19
- Deploy a heterogeneous mix of VM sizes in a single scale set. You can view max scale set instance counts in the [documentation](./virtual-machine-scale-sets-orchestration-modes.md#what-has-changed-with-flexible-orchestration-mode).
20
20
- Optimize your deployments for cost or capacity through allocation strategies.
21
21
- Continue to make use of scale set features, like [Spot Priority Mix](./spot-priority-mix.md), [Autoscale](./virtual-machine-scale-sets-autoscale-overview.md), or [Upgrade Policies](./virtual-machine-scale-sets-set-upgrade-policy.md).
@@ -36,23 +36,23 @@ az feature show --namespace "Microsoft.Compute" --name "FlexVMScaleSetSkuProfile
36
36
37
37
## Changes to existing scale set properties
38
38
### sku.tier
39
-
The `sku.tier` property is currently an optional scale set property and will be `null` for Instance Flexibility scenarios.
39
+
The `sku.tier` property is currently an optional scale set property and will be `null` for Instance Mix scenarios.
40
40
41
41
### sku.capacity
42
42
The `sku.capacity` property continues to represent the overall size of the scale set in terms of the total number of VMs.
43
43
44
44
### scaleInPolicy
45
-
The optional scale-in property isn't needed for scale set deployments using Instance Flexibility. During scaling in events, the scale set utilizes the allocation strategy to inform the decision on which VMs should be scaled in. For example, when you use `LowestPrice`, the scale set scales in by removing the more expensive VMs first.
45
+
The optional scale-in property isn't needed for scale set deployments using Instance Mix. During scaling in events, the scale set utilizes the allocation strategy to inform the decision on which VMs should be scaled in. For example, when you use `LowestPrice`, the scale set scales in by removing the more expensive VMs first.
46
46
47
47
## New scale set properties
48
48
### skuProfile
49
-
The `skuProfile` property represents the umbrella property for all properties related to Instance Flexibility, including VM sizes and allocation strategy.
49
+
The `skuProfile` property represents the umbrella property for all properties related to Instance Mix, including VM sizes and allocation strategy.
50
50
51
51
### vmSizes
52
-
The `vmSizes` property is where you specify the specific VM sizes that you're using as part of your scale set deployment with Instance Flexibility.
52
+
The `vmSizes` property is where you specify the specific VM sizes that you're using as part of your scale set deployment with Instance Mix.
53
53
54
54
### allocationStrategy
55
-
Instance Flexibility introduces the ability to set allocation strategies for your scale set. The `allocationStrategy` property is where you specify which allocation strategy you'd like to use for your Instance Flexible scale set deployments. There are two options for allocation strategies, `lowestPrice` and `capacityOptimized`. Allocation strategies apply to both Spot and Standard VMs.
55
+
Instance Mix introduces the ability to set allocation strategies for your scale set. The `allocationStrategy` property is where you specify which allocation strategy you'd like to use for your Instance Flexible scale set deployments. There are two options for allocation strategies, `lowestPrice` and `capacityOptimized`. Allocation strategies apply to both Spot and Standard VMs.
56
56
57
57
#### lowestPrice (default)
58
58
This allocation strategy is focused on workloads where cost and cost-optimization are most important. When evaluating what VM split to use, Azure looks at the lowest priced VMs of the VM sizes specified. Azure also considers capacity as part of this allocation strategy. When using the `lowestPrice` allocation strategy, the scale set deploys as many of the lowest priced VMs as it can, depending on available capacity, before moving on to the next lowest priced VM size specified.
@@ -61,20 +61,20 @@ This allocation strategy is focused on workloads where cost and cost-optimizatio
61
61
This allocation strategy is focused on workloads where attaining capacity is the primary concern. When evaluating what VM size split to deploy in the scale set, Azure looks only at the underlying capacity available. It doesn't take price into account when determining what VMs to deploy. Using `capacityOptimized` can result in the scale set deploying the most expensive, but most readily available VMs.
62
62
63
63
## Cost
64
-
Following the scale set cost model, usage of Instance Flexibility is free. You continue to only pay for the underlying resources, like the VM, disk, and networking.
64
+
Following the scale set cost model, usage of Instance Mix is free. You continue to only pay for the underlying resources, like the VM, disk, and networking.
65
65
66
66
## Limitations
67
-
- Instance Flexibility is currently available in the following regions: West US, West US2, West US3, East US, East US2, CentralUS, South Central US, North Central US, West Europe, North Europe, UK South, and France Central.
68
-
- Instance Flexibility is only available for scale sets using Flexible Orchestration Mode.
69
-
- Instance Flexibility is currently only available through ARM template and in the Azure portal.
70
-
- You must have quota for the VM sizes you're requesting with Instance Flexibility.
71
-
- You can specify **up to** five VM sizes with Instance Flexibility at this time.
72
-
- Existing scale sets can't be updated to use Instance Flexibility.
67
+
- Instance Mix is currently available in the following regions: West US, West US2, West US3, East US, East US2, CentralUS, South Central US, North Central US, West Europe, North Europe, UK South, and France Central.
68
+
- Instance Mix is only available for scale sets using Flexible Orchestration Mode.
69
+
- Instance Mix is currently only available through ARM template and in the Azure portal.
70
+
- You must have quota for the VM sizes you're requesting with Instance Mix.
71
+
- You can specify **up to** five VM sizes with Instance Mix at this time.
72
+
- Existing scale sets can't be updated to use Instance Mix.
73
73
- VM sizes can't be changed once the scale set is deployed.
74
-
- For REST API deployments, you must have an existing virtual network inside of the resource group that you're deploying your scale set with Instance Flexibility in.
74
+
- For REST API deployments, you must have an existing virtual network inside of the resource group that you're deploying your scale set with Instance Mix in.
75
75
76
-
## Deploy a scale set using Instance Flexibility
77
-
The following example can be used to deploy a scale set using Instance Flexibility:
76
+
## Deploy a scale set using Instance Mix
77
+
The following example can be used to deploy a scale set using Instance Mix:
78
78
79
79
### [REST API](#tab/arm-1)
80
80
To deploy an Instance Flexible scale set through REST API, use a `PUT` call to and include the following sections in your request body:
@@ -117,7 +117,7 @@ Lastly, be sure to specify the `skuProfile` with **up to five** VM sizes. This s
117
117
1. Go to **Virtual machine scale sets**.
118
118
2. Select the **Create** button to go to the **Create a virtual machine scale set** view.
119
119
3. In the **Basics** tab, fill out the required fields. If the field isn't called out in the next sections, you can set the fields to what works best for your scale set.
120
-
4. Ensure that you select a region that Instance Flexibility is supported in.
120
+
4. Ensure that you select a region that Instance Mix is supported in.
121
121
5. Be sure **Orchestration mode** is set to **Flexible**.
122
122
6. In the **Size** section, click **Select up to 5 sizes (preview)** and the **Select a VM size** page appears.
123
123
7. Use the size picker to select up to five VM sizes. Once you've selected your VM sizes, click the **Select** button at the bottom of the page to return to the scale set Basics tab.
@@ -131,18 +131,18 @@ Lastly, be sure to specify the `skuProfile` with **up to five** VM sizes. This s
| SkuProfileAllocationStrategyInvalid | Sku Profile’s Allocation Strategy is invalid. | Ensure that you're using either `CapacityOptimized` or `LowestPrice` as the `allocationStrategy`|
133
133
| SkuProfileVMSizesCannotBeNullOrEmpty | Sku Profile VM Sizes cannot be null or empty. Please provide a valid list of VM Sizes and retry. | Provide at least one VM size in the `skuProfile`. |
134
-
| SkuProfileHasTooManyVMSizesInRequest | Too many VM Sizes were specified in the request. Please provide no more than 5 VM Sizes. | At this time, you can specify up to five VM sizes with Instance Flexibility. |
134
+
| SkuProfileHasTooManyVMSizesInRequest | Too many VM Sizes were specified in the request. Please provide no more than 5 VM Sizes. | At this time, you can specify up to five VM sizes with Instance Mix. |
135
135
| SkuProfileVMSizesCannotHaveDuplicates | Sku Profile contains duplicate VM Size: {duplicateVmSize}. Please remove any duplicates and retry. | Check the VM SKUs listed in the `skuProfile` and remove the duplicate VM size. |
136
-
| SkuProfileUpdateNotAllowed | Virtual Machine Scale Sets with Sku Profile property cannot be updated. | At this time, you can't update the `skuProfile` of a scale set using Instance Flexibility. |
137
-
| SkuProfileScenarioNotSupported | {propertyName} is not supported on Virtual Machine Scale Sets with Sku Profile | Instance Flexibility doesn’t support certain scenarios today, like Azure Dedicated Host (`properties.hostGroup`), Capacity Reservations (`properties.virtualMachineProfile.capacityReservation`), and StandbyPools (`properties.standbyPoolProfile`). Adjust the template to ensure you’re not using unsupported properties. |
136
+
| SkuProfileUpdateNotAllowed | Virtual Machine Scale Sets with Sku Profile property cannot be updated. | At this time, you can't update the `skuProfile` of a scale set using Instance Mix. |
137
+
| SkuProfileScenarioNotSupported | {propertyName} is not supported on Virtual Machine Scale Sets with Sku Profile | Instance Mix doesn’t support certain scenarios today, like Azure Dedicated Host (`properties.hostGroup`), Capacity Reservations (`properties.virtualMachineProfile.capacityReservation`), and StandbyPools (`properties.standbyPoolProfile`). Adjust the template to ensure you’re not using unsupported properties. |
138
138
| SkuNameMustBeMixIfSkuProfileIsSpecified | Sku name is {skuNameValue}. Virtual Machine Scale Sets with Sku Profile must have the Sku name property set to "Mix" | Ensure that the `sku.name property` is set to `"Mix"`. |
139
-
| SkuTierMustNotBeSetIfSkuProfileIsSpecified | Sku tier is {skuTierValue}. Virtual Machine Scale Sets with Sku Profile must not have the Sku tier property set. |`sku.tier` is an optional property for scale sets. With Instance Flexibility, `sku.tier` must be set to `null` or not specified. |
140
-
| InvalidParameter | The value of parameter skuProfile is invalid. | Your subscription isn't registered for the Instance Flexibility feature. Follow the enrollment instructions to register for the Preview. |
141
-
| FleetRPInternalError | An unexpected error occurred while computing the desired sku split. | Instance Flexibility isn't supported in this region yet. Deploy only in supported regions. |
139
+
| SkuTierMustNotBeSetIfSkuProfileIsSpecified | Sku tier is {skuTierValue}. Virtual Machine Scale Sets with Sku Profile must not have the Sku tier property set. |`sku.tier` is an optional property for scale sets. With Instance Mix, `sku.tier` must be set to `null` or not specified. |
140
+
| InvalidParameter | The value of parameter skuProfile is invalid. | Your subscription isn't registered for the Instance Mix feature. Follow the enrollment instructions to register for the Preview. |
141
+
| FleetRPInternalError | An unexpected error occurred while computing the desired sku split. | Instance Mix isn't supported in this region yet. Deploy only in supported regions. |
142
142
143
143
## FAQs
144
-
### Can I use Spot and Standard VMs with Instance Flexibility?
145
-
Yes, you can use both Spot and Standard VMs in your scale set deployments using Instance Flexibility. To do so, use [Spot Priority Mix](./spot-priority-mix.md) to define a percentage split of Spot and Standard VMs.
144
+
### Can I use Spot and Standard VMs with Instance Mix?
145
+
Yes, you can use both Spot and Standard VMs in your scale set deployments using Instance Mix. To do so, use [Spot Priority Mix](./spot-priority-mix.md) to define a percentage split of Spot and Standard VMs.
146
146
147
-
## My region doesn't support Instance Flexibility today, will it support Instance Flexibility in the future?
148
-
Instance Flexibility is rolling out to all Azure regions during Public Preview. Instance Flexibility is currently available in the following regions: West US, West US2, West US3, East US, East US2, CentralUS, South Central US, North Central US, West Europe, North Europe, UK South, and France Central.
147
+
## My region doesn't support Instance Mix today, will it support Instance Mix in the future?
148
+
Instance Mix is rolling out to all Azure regions during Public Preview. Instance Mix is currently available in the following regions: West US, West US2, West US3, East US, East US2, CentralUS, South Central US, North Central US, West Europe, North Europe, UK South, and France Central.
0 commit comments