IaaS v2: New enhancement with Azure Architecture

October 14, 2015 | Comments(0) |

I will not take up a long time to unfold the facts for which you are eager searching and surfing on the wide internet. If you want to first get a short answer of what exactly is IaaS v2, let me satisfy the hunger of information by the definition I created.

Definition:
IaaS v2 states few architectural changes within Azure, which originated with the introduction of new management framework called Azure Resource Manager (ARM).

Definition Decoded:

So the whole story of ‘IaaS v2’ begins by understanding difference between Azure Service Management (ASM) and Azure Resource Manager (ARM). There is a management framework for almost all IT systems. The management framework was initially designed and used for Azure was Azure Service Management (ASM), which is also now termed as Classic. But now Microsoft has introduced a new framework for Azure, which is known as Azure Resource Manager (ARM). This is the reason we have two management portals for Azure; one, which is the default management portal, which works on ASM framework, and then the next one, which is known as Azure Ibiza preview portal which works on ARM framework. Even the Azure PowerShell CMDLETS works in two different modes; ASM and ARM

ARM framework brings in a lot of architectural changes to improve the way Azure IaaS service is managed today. Hence with ARM framework, the new design is termed as ‘IaaS v2’ defining the older design as ‘IaaS v1’ now.

 

Blog image 1 IaaS v2

 

Changes with IaaS v2:
+ Cloud Service is now replaced with Resource Group. In IaaS v2, the concept of cloud service as a container is completely abolished. Now the virtual machines and any other resources meant for a same department or application could be grouped together under a Resource Group.

+ Load Balancer is now considered an individual or discrete resource and not tightly bound with anyone like in cloud service.

+ We don’t have to give VIP (Virtual IP address). We can assign VMs with Internet routable IPs hence VMs are directly connected to Internet. Only if we are deploying a load balancer, than the VIP can be assigned to the load balancer.

+ Now there will be three fault domain, in IaaS v1 (ASM) there were only two.

+ Virtual Machines will be bounded with Azure Key Vault service which is meant for better security as it encrypts credentials and keys used for storage access.

+ Network Adapters are also now an individual or discrete resource, which is created and managed separately to protect the network configuration from vanishing in case of VM failure. The Network Adapters can be quickly linked to any other VM in case required.

+ VM Endpoints no more required as the same task of allowing incoming traffic from specific port is applied by configuring NAT rules on the load balancer component.

Benefits with IaaS v2:

+ Role Based Access Control.

+ More granular control over IaaS environment.

+ Template based deployment.

The most powerful impacts of IaaS v2 comes into picture when we see the capability to create templates to deploy resource groups and apply the same at a drastically faster pace. With ARM framework, we can now create a JSON (Java Script Object Notation) based templates. So, in real time if we have an application which needs to be deployed which has typical needs like VM, storage, networking, database etc., we can spun up a JSON template stating to create all such resources and build up a Resource Group. Once the task is done, the entire set of resources is deployed in one go on Azure. Also if same application needs to be deployed at different locations, just keep on deploying the same template. This makes application deployment superfast. If you have an idea about AWS platform you can compare this with their feature called Cloud Formation. I hope you have built a good base on IaaS v2 now. If you want to dive deep into the subject, I am also putting up some links for further study.

What Microsoft has explained about ARM?
https://azure.microsoft.com/en-in/documentation/articles/virtual-machines-azurerm-versus-azuresm/

A discussion blog which helps you understand whether to opt for ASM or ARM:
http://trevorsullivan.net/2015/08/10/azure-resource-manager-or-service-management/

Understanding Role Based Access Control:
https://azure.microsoft.com/en-in/documentation/articles/role-based-access-control-configure/

How to create and deploy Resource Manager templates (for faster deployment):
https://azure.microsoft.com/en-in/documentation/articles/resource-group-authoring-templates/

 


Leave a Reply