From d1aed92270ef759660a394a891c841673f24a7cc Mon Sep 17 00:00:00 2001 From: Brittany Rowe <75815751+brittanyrowe@users.noreply.github.com> Date: Fri, 10 Jan 2025 15:16:08 -0800 Subject: [PATCH 1/5] End table --- articles/virtual-machine-scale-sets/instance-mix-update.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/virtual-machine-scale-sets/instance-mix-update.md b/articles/virtual-machine-scale-sets/instance-mix-update.md index 4acea16901..a00ad8666e 100644 --- a/articles/virtual-machine-scale-sets/instance-mix-update.md +++ b/articles/virtual-machine-scale-sets/instance-mix-update.md @@ -236,7 +236,7 @@ In the body, be sure to set `sku.name` to `"Mix"` and include the `skuProfile` w } ``` - +--- ## Next steps Learn how to [troubleshoot](instance-mix-faq-troubleshooting.md) your instance mix enabled scale set. \ No newline at end of file From f8ef69588907acffea2d3933158df41b345568ea Mon Sep 17 00:00:00 2001 From: Brittany Rowe <75815751+brittanyrowe@users.noreply.github.com> Date: Fri, 10 Jan 2025 15:16:44 -0800 Subject: [PATCH 2/5] Removed old FAQ --- .../instance-mix-faq-troubleshooting.md | 3 --- 1 file changed, 3 deletions(-) diff --git a/articles/virtual-machine-scale-sets/instance-mix-faq-troubleshooting.md b/articles/virtual-machine-scale-sets/instance-mix-faq-troubleshooting.md index 23734596f0..e08f883718 100644 --- a/articles/virtual-machine-scale-sets/instance-mix-faq-troubleshooting.md +++ b/articles/virtual-machine-scale-sets/instance-mix-faq-troubleshooting.md @@ -15,9 +15,6 @@ ms.reviewer: jushiman ### Can I use Spot and Standard VMs with Instance Mix? 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. -### My region doesn't support Instance Mix today. Will it support Instance Mix in the future? -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, East US, and East US2. - ## Troubleshooting | Error Code | Error Message | Troubleshooting options | | ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | From 7e87388dd2e457b059977b3de4fc1ead534608f8 Mon Sep 17 00:00:00 2001 From: Brittany Rowe <75815751+brittanyrowe@users.noreply.github.com> Date: Fri, 10 Jan 2025 15:17:46 -0800 Subject: [PATCH 3/5] being grammatically accurate with name --- .../instance-mix-faq-troubleshooting.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/articles/virtual-machine-scale-sets/instance-mix-faq-troubleshooting.md b/articles/virtual-machine-scale-sets/instance-mix-faq-troubleshooting.md index e08f883718..60e8c84e86 100644 --- a/articles/virtual-machine-scale-sets/instance-mix-faq-troubleshooting.md +++ b/articles/virtual-machine-scale-sets/instance-mix-faq-troubleshooting.md @@ -1,6 +1,6 @@ --- title: Frequently Asked Questions and Troubleshooting -description: Frequently asked questions and troubleshooting for Instance Mix on virtual machine scale sets. +description: Frequently asked questions and troubleshooting for instance mix on virtual machine scale sets. author: brittanyrowe ms.author: brittanyrowe ms.topic: conceptual @@ -12,18 +12,18 @@ ms.reviewer: jushiman # Virtual machine scale sets with instance mix frequently asked questions and troubleshooting ## Frequently Asked Questions -### Can I use Spot and Standard VMs with Instance Mix? -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. +### Can I use Spot and Standard VMs with instance mix? +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. ## Troubleshooting | Error Code | Error Message | Troubleshooting options | | ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `SkuProfileAllocationStrategyInvalid` | `Sku Profile’s Allocation Strategy is invalid.` | Ensure that you're using either `CapacityOptimized` or `LowestPrice` as the `allocationStrategy` | | `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`. | -| `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. | +| `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. | | `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. | -| `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. | -| `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. | +| `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. | +| `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. | | `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"`. | -| `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. | -| `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. | \ No newline at end of file +| `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. | +| `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. | \ No newline at end of file From c96094acc4779b5a5d6451df0dbb72a07ebc357b Mon Sep 17 00:00:00 2001 From: Brittany Rowe <75815751+brittanyrowe@users.noreply.github.com> Date: Fri, 10 Jan 2025 15:19:11 -0800 Subject: [PATCH 4/5] Updated troubleshooting --- .../instance-mix-faq-troubleshooting.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/articles/virtual-machine-scale-sets/instance-mix-faq-troubleshooting.md b/articles/virtual-machine-scale-sets/instance-mix-faq-troubleshooting.md index 60e8c84e86..a2514ff558 100644 --- a/articles/virtual-machine-scale-sets/instance-mix-faq-troubleshooting.md +++ b/articles/virtual-machine-scale-sets/instance-mix-faq-troubleshooting.md @@ -18,11 +18,10 @@ Yes, you can use both Spot and Standard VMs in your scale set deployments using ## Troubleshooting | Error Code | Error Message | Troubleshooting options | | ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `SkuProfileAllocationStrategyInvalid` | `Sku Profile’s Allocation Strategy is invalid.` | Ensure that you're using either `CapacityOptimized` or `LowestPrice` as the `allocationStrategy` | +| `SkuProfileAllocationStrategyInvalid` | `Sku Profile’s Allocation Strategy is invalid.` | Ensure that you're using `CapacityOptimized`, `Prioritized`, or `LowestPrice` as the `allocationStrategy` | | `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`. | | `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. | | `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. | -| `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. | | `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. | | `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"`. | | `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. | From ad6542e5fbd6428ddd85e690bfe58fc882da6771 Mon Sep 17 00:00:00 2001 From: Megan Bradley Date: Sat, 11 Jan 2025 05:40:48 -0700 Subject: [PATCH 5/5] status --- .../service-fabric/how-to-managed-cluster-modify-node-type.md | 2 +- articles/virtual-machines/prepay-reserved-vm-instances.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/articles/service-fabric/how-to-managed-cluster-modify-node-type.md b/articles/service-fabric/how-to-managed-cluster-modify-node-type.md index cfbe29c024..8486bd2766 100644 --- a/articles/service-fabric/how-to-managed-cluster-modify-node-type.md +++ b/articles/service-fabric/how-to-managed-cluster-modify-node-type.md @@ -163,7 +163,7 @@ In this walkthrough, you learn how to modify the node count for a node type usin ![Sample showing a node count increase][adjust-node-count] -6) Select `Manage node type scaling` to configure the scaling settings and choose between custom autoscale and manual scale options. Autoscale is a built-in feature that helps applications perform their best when demand changes. You can choose to scale your resource manually to a specific instance count or via a custom autoscale policy that scales based on metric thresholds. You can also schedule instance counts to scale during designated time windows. [Learn more about Azure Autoscale](/azure/azure-monitor/platform/autoscale-get-started?WT.mc_id=Portal-Microsoft_Azure_Monitoring) or [view the how-to video](https://www.microsoft.com/videoplayer/embed/RE4u7ts). +6) Select `Manage node type scaling` to configure the scaling settings and choose between custom autoscale and manual scale options. Autoscale is a built-in feature that helps applications perform their best when demand changes. You can choose to scale your resource manually to a specific instance count or via a custom autoscale policy that scales based on metric thresholds. You can also schedule instance counts to scale during designated time windows. [Learn more about Azure Autoscale](/azure/azure-monitor/platform/autoscale-get-started?WT.mc_id=Portal-Microsoft_Azure_Monitoring) or [view the how-to video](https://learn-video.azurefd.net/vod/player?id=125ecef8-c287-4a81-9001-69c01558398c). * **Custom autoscale**: Select the appropriate `scale mode` to define the custom Autoscale policy - `Scale to a specific instance count`or `Scale based on a metric`. The latter is based on metric trigger rules, for example, increase instance count by 1 when CPU Percentage is above 70%. Once you define the policy, select `Save` at the top. diff --git a/articles/virtual-machines/prepay-reserved-vm-instances.md b/articles/virtual-machines/prepay-reserved-vm-instances.md index 3485eba01b..400d3de02f 100644 --- a/articles/virtual-machines/prepay-reserved-vm-instances.md +++ b/articles/virtual-machines/prepay-reserved-vm-instances.md @@ -107,7 +107,7 @@ If you have an EA agreement, you can use the **Add more option** to quickly add |Term |One year or three years. There's also a 5-year term available only for HBv2 VMs.| |Quantity |The number of instances being purchased within the reservation. The quantity is the number of running VM instances that can get the billing discount. For example, if you are running 10 Standard_D2 VMs in the East US, then you would specify quantity as 10 to maximize the benefit for all running VMs. | -> [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE2PjmT] +> [!VIDEO https://learn-video.azurefd.net/vod/player?id=4e688b15-2bc8-47b5-b67e-16ea39397709] ## Usage data and reservation utilization