Skip to main content

VM Creation: Custom Scrips vs Custom Images

By
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.
Labels:

Comments

Post a Comment

Popular posts from this blog

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

By
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(...
Post a Comment
Read more

How to audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

By
Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...
Post a Comment
Read more