© Copyright SELA Software & Education Labs Ltd. | 14-18 Baruch Hirsch St Bnei Brak, 51202 Israel | www.selagroup.com

SELA DEVELOPER PRACTICEJUNE 19-23, 2016

Ido Katz, Microsoft Azure MVPCloud Infrastructure Technical LeadSela Group

Azure Service Management Vs. Azure Resource ManagerMail: idok@sela.co.ilBlog: blogs.microsoft.co.il/idokatzTwitter: @send2katz

AgendaWhat is Cloud?Azure Service ManagementDemo – ASM – IaaS Deployment ProcessAzure Resource ManagerDemo – ARM – IaaS Deployment ProcessPros – ASM & ARMCons – ASM & ARMWhy should I use them both?Questions

What is Cloud?Packaged Software

Storage

Servers

Networking

O/S

Middleware

Virtualization

Data

Applications

Runtime

You

man

age

Infrastructure(as a Service)

Storage

Servers

Networking

O/S

Middleware

Virtualization

Data

Applications

Runtime

Managed by vendor

You

man

age

Platform(as a Service)

Managed by vendor

You

man

age

Storage

Servers

Networking

O/S

Middleware

Virtualization

Applications

Runtime

Data

Software(as a Service)

Managed by vendor

Storage

Servers

O/S

Middleware

Virtualization

Applications

Runtime

Data

Networking

Azure Service ManagementAzure Service Management (A.K.A ASM/V1/Classic) was there from the beginning of Azure but he started as an API for PaaS Services as Azure started as PaaS ServicesASM operations are based on the Cloud ServiceASM is based on XML SchemeYou can use ASM for the old portal and the new portal as well

Demo

ASM – IaaS Deployment Process

Azure Resource ManagerAzure Resource Manager was announced 2 Years agoThe objective of the ARM is to remove dependencies of the cloud service operations.Each component will be located under Resource Group.ARM is based on JSON Scheme.Resource Group can be exported and than you can the JSON file and deployment file.

Demo

ARM – IaaS Deployment Process

Why should I use them both?ASM-

supported by most existing Azure resources customer already invested in the ASM deploymentNew resources added to Azure will not support this model (Azure Active Directory, Media Services and a lot of Marketplace Solutions such as Kemp, Couch Base, etc.)

ARM-Most of the resources already supportedNew Customer should use ARM as the default deploymentThere are some resources that available only on this model (Scale Sets, Cool Storage, RBAC, etc.)

Pros – ASM & ARMARM ASM

Work in Parallel Visualization

JSON Based Easy to navigate

New Features!!! Well Known Structure

Cons – ASM & ARMARM ASM

Hard to navigate Dependencies

There are components that aren’t supported yet

XML Based

Can’t Communicate with ASM Components unavailable

A whole different structure Cannot communicate with ARM

Things you should knowASM Resources cannot communicate with ARM ResourcesASM was based on cloud service operations and because cloud service cannot do two operations in a time you couldn’t work in parallel.(For example you couldn’t deploy two VM’s under the same cloud service)ASM & ARM got two different API’s so if you're using PS there are commands for ASM (for example: Get-AzureVM) and for ARM (for example: Get-AzureRMvm)If you starting using Azure today start working with the ARM right away.There is no migration tool for moving from ASM to ARM – you can use PowerShell script to automate it. There is a community GitHub repository by Microsoft which got a lot of JSON deployment file that you can use and customize it to your own environment.

Questions