Skip to content

Commit

Permalink
Merge pull request #833 from MicrosoftDocs/main
Browse files Browse the repository at this point in the history 
Publish to live, Sunday 4 AM PST, 1/12
  • Loading branch information
@ttorble
ttorble authored Jan 12, 2025
2 parents 2e1f03a + 2de4f97 commit e0fcbf0
Show file tree
Hide file tree
Showing 4 changed files with 11 additions and 15 deletions.
2 changes: 1 addition & 1 deletion articles/service-fabric/how-to-managed-cluster-modify-node-type.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
20 changes: 8 additions & 12 deletions articles/virtual-machine-scale-sets/instance-mix-faq-troubleshooting.md
View file
Original file line number Diff line number Diff line change
@@ -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
Expand All @@ -12,21 +12,17 @@ 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.

### 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.
### 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` |
| `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. |
| `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. |
| `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. |
| `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. |
2 changes: 1 addition & 1 deletion articles/virtual-machine-scale-sets/instance-mix-update.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.
2 changes: 1 addition & 1 deletion articles/virtual-machines/prepay-reserved-vm-instances.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down

0 comments on commit e0fcbf0

Please sign in to comment.