Trabalhando com
ARM Templates
Lucas A. Romão
Cloud Technical Solution Architect – N3 Results
Microsoft Azure MVP
@LucasRomao
https://www.facebook.com/LucasRomaoMVP/
#AzureTechNights
Agenda
 Qual a diferença entre ASM e ARM?
 Intro ao Resource Manager
 O que compõe o ARM
 Desafios
 ARM Templates….
 Demo, demo, demo…..
#AzureTechNights
Qual a diferença entre ASM e
ARM?
Um pouco de conceito e histórico......
#AzureTechNights
Introdução ao Resource Manager
• Nova Modelo de Gerenciamento de IAAS
• Grupamentos Lógicos
• Tags
• RBAC
• Declarativa ou Imperativa
• Orientada a templates
• Extensível
#AzureTechNights
Modelo Classico (v1) Resource Manager (V2)
Modelo de Gerenciamento IAAS
#AzureTechNights
Desafios
Resource Group é uma unidade de Gerenciamento
 Lifecycle: deployment, update, delete, status
 Identity: Recursos podem conversar entre sí
 Grouping: Métricas, billing, quota: aplicadas ao grupo
#AzureTechNights
O que compõe o ARM?
-Resource;
-Resource Group;
-Resource Provider;
- Resource Manager Template;
#AzureTechNights
Para que serve o ARM Templates
#AzureTechNights
ARM Template + VS
Pré-requisitos: SDK Azure
{
"$schema":
"https://schema.management.azure.com/schemas/201
5-01-01/deploymentTemplate.json#",
"contentVersion": "1.0.0.0",
"parameters": {},
"variables": {},
"resources": [],
"outputs": {}
}
#AzureTechNights
DEMO
#AzureTechNights
E quanto ao Portal do Azure?
DEMO
#AzureTechNights
Referências para Estudo
Disponíveis em http://azure.microsoft.com/en-
us/documentation/templates/
Repositório GitHub em https://github.com/Azure/azure-
quickstart-templates.

Trabalhando com ARM Templates

Notas do Editor

  • #6 IaaS V2 or IaaS under resource manager Today you start off with a cloud service. Some networking, and storage account. This is Azure how it has existed for a while. Classic Compute Model The new model – Componitized model More flexibility and functionality You have a resource group and then you have many serperate resources within that group. It is a decomposed or a separated compontized model. You can see that the NIC is a separate Reource, the Vnet is separate, etc. This allows for a lot more flexibility. Especially when we start to use our new template model to compose or bring all these reources together to create a virtual machine. But when you deploy, you don’t want to deploy all these resources independently. So the Resource manager has the concept of dependencies. The VM is dependant on the storage account. The VM then references the network interface card to run the VM, the NIC references the IP address, the Vnet. The Load balancer references the NIC, etc. etc. All these references and depenedancies are defined in the model. The resource manager goes through and deploys the resources with as much paralism as possible while also ensuring that any dependant resource is deployed before the subsequent resource is deployed. Network Security group can be deployed directly to the VM or the NIC or it can also be deployed to the Subnet . So you can setup subnet acls or directly to the virtual machine. Is this is GA