Skip to main content

VM Creation: Custom Scrips vs Custom Images

When we need custom applications or configuration to be done on the VM we can do this on Azure in two ways:
  • Custom ISO
  • Custom scripts extensions (known also as Formula in DevLabs context)
 I noticed that a recurrent questions appears in discussions with different people:
When I should use custom ISO vs custom scripts extensions?

Before jumping to a discussion where we would compare this two options and what are the advantages/disadvantages of each option, let's see what are the steps involved to create a script of an ISO.


Custom ISO 
We can create a custom ISO on our local machine, with all our applications installed on it. Once we have the ISO created we just need to take our VHD and prepared it for Azure. More about this steps can be found on Microsoft documentation (Capture a managed image of a generalized VM in Azure and Create custom VM images).

Custom scripts extensions
Custom scripts are executed after the VHD is deployed on the VM. Using this scripts we can push or install any kind of application or change OS configuration. I would compare custom scripts with post-deployment scripts, that are executed after the VM deployment finish.

Custom ISO vs Custom scripts extensions
Don't expect to have a winner from this fight. Each option has advantages and disadvantageous. The context of your project will define what option best suites your needs.
In the below table I tried to catch the most important things that you need to consider before selecting the provisioning mechanism that you want to use.
  
Custom Image Custom scripts
Pros: Fast deployment Pros: Environment/App updates can be pushed on the fly (artifacts)
Pros: No extra steps after deployment Pros: Last version of VM image, including updates is used
Pros: VMs from same image are identical Pros: Default settings can be specified like VM Size, VNET configuration
Cons: Image needs to be recreated when something change Pros: Default settings are used as default values, but during provisioning other values can be specified
Cons: No dynamic update of the image Cons: Deployment using formulas can take longer time (provisioning+running formula/scripts)
Cons: Windows and other Updates are pushed only after provisioning

What should I use? 
I would say that in most of the cases, custom scrips should be a good option. They are flexible enough to allow you to change or update the artifacts without having to recreate the ISO, offering you a deployment that already contains last updated of OS also. No time wasted for OS updates.
There are some narrow cases when you want to use custom images. The case that I see the most common one is when you want a fast provisioning of the VM. For example when you want to increase the number of VMs in a cluster, where scalability is extremely important.

The winner is...
As you already notice, custom scrips are my favorites and I see them a better solution in most of the cases.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP