Skip to main content
Cool Feature! Virtual Machine Scale Set with spot and standard VMs (Spot Priority Mix)

Hi All!

Azure offers spot and standard mixed virtual machine scale sets feature generally available now.

First, Let us refresh what is meant by spot?

Spot is nothing but azure offers some unused azure capacity VMs with uncertainity i.e for example, azure finds/has some VMs capacity unused which can be assigned/allocated to you based on your request with low cost than PAYG but azure can terminate/discontinue the spot allocated VM when it is requested by Pay-as-you-go-user.

Here before, VMSS had only standard (PAYG) VM without spot but now we can get VMs with both spot and standard mixed.

Please find the below steps and picture

  1. This feature works only in Flexible Orchestration Mode. So choose Flexible instead of Uniform.
  2. Check the "Run with Azure Spot discount"
  3. Click Next "Spot"
  4. Check the "Scale with VMs and Spot VMs"
  5. Mention the total number of VMs count. For example, Here we specify total count as 10
  6. Mention uninterruptible percentage. Here we specify 80%, so 8/10 VMs will be always yours.
  7. Spot VMs % generates automatically once you specified the above. so 2/10 VMs in azure control. Azure charges low cost from you than the previous 8 VMs but if anybody requests for it, that 2 VM will be discontinued from your subscription.

Hope you enjoyed!

Comments

Post a Comment

Popular posts from this blog

Azure Static Web Apps - Plan Comparison #cloud #azure Hi All! Azure Static web app is a good service when we have static web apps like javacript frameworks and libraries applictions (Ex: Angular, React, Svelte, Vue, Blazor). It also supports Python 3.10 based static web app as well as per the latest azure news. Other advantage of it is coupled with your Azure AD. so that your code can be directly pushed to azure static web app via either Azure DevOps or Github whenever code push occurs. At the time of azure static web app creation, it asks for deployment source as any one of the below. Based on the selection, it allows you to select the organization, project and repositories from the source. Azure DevOps - Azure AD connected Devops organizations will be listed out Github Other - For ex: If you want to deploy code from other organization. Below table will be helpful to choose the best pricing plan for your workload. Plan/Feature Free Standard ...
1 comment
Read more
Azure Public IP(s) are zone redundant free of cost natively - Generally Available Availability zone gives high availability to an application as well as information by forestalling the physical datacenter disappointments by involving replication of the asset in extra datacenter. Azure typically has 3 zones per region (and not all regions support zone). Thus, while setting up the environment we really want to pick the right region based on our usecase. Public IP helps to access a resource or an application publicly. Azure offers 2 types of SKU for public IP as below Basic Standard Only Standard SKU gives zone facility. Basic SKU is always non-zonal and this SKU also will be retired 09/2025. Standard public IP can be fell into any of the below category No Zone / Non-Zonal - No availability zone at all Zonal - Our services can be replicated in any one of selected zones from three zones. Zone redundant - Resource will be replicated in all 3 zones. It is opposite of...
Post a Comment
Read more
Avoid YAML Validation error in azure devops pipeline Hi All! Consider a scenario that you committed a YML CI/CD file on the repository with some syntax, indentation and/or other error(s). so that pipeline failed. After you find some errors and rectified in the repository file and committed again but pipeline still gets failed because some errors are still there. Now you afraid that even if you fixed error in all the places, what happens if pipeline failed again because your project lead or manager set up build notification mail trigger for build success and fails. you need to answer them for build fail reason. Azure devops pipelines offers YAML validation feature after altered and before committed and before run pipeline. To utilize this feature, what we do is, Instead of modifying the file from repository, Do as below Go to the specific build click "Edit Pipeline" Modify/fix errors and click "validate" as shown in the picture below ...
Post a Comment
Read more