![ARM template structure
{
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
"contentVersion": "1.0.0.0",
"parameters": {
// Parameters referenced by resources (parameterize your template)
},
"variables": {
// Variables referenced by resources
},
"resources": [
// Virtual Machine, Web App, Virtual Network, SQL Azure, Storage Account, etc.
],
"outputs": {
// Optional outputs from deployment
}
}](https://image.slidesharecdn.com/mypersonalstoryfromazureitprotoazuredevops-170424210629/85/My-personal-story-from-azure-it-pro-to-azure-dev-ops-26-320.jpg)
Ad
More Related Content
What's hot (9)
Similar to My personal story from azure it pro to azure dev ops (20)
Ad
Recently uploaded (20)
Ad
My personal story from azure it pro to azure dev ops
- 1. Welcome to the Iselin, New Jersey
- 2. My personal story from azure it pro to Azure devops
- 3. Agenda • What makes you an Azure IT Pro? • What is DevOps • How embracing DevOps changed my (Azure) life • Demos and Q&A
- 4. Peter De Tender Twitter: @pdtit Email: [email protected] Microsoft Cloud Infrastructure Expert Microsoft Certified Trainer – MCT Microsoft Learning Regional Lead - BE Microsoft Azure MVP (Reconnect) Ex-Microsoft Azure Engineering PM Azure Certified Architect Azure Advisors member Book author for Packt Publishing & Apress Courseware Author and Trainer for Opsgility Technical Writer
- 5. What makes you an azure it pro
- 6. What is an Azure IT Pro: • A person who manages and maintains IT infrastructure in Azure • Deploying compute, storage, networking, identity, websites, backup & DR solutions • An individual who doesn’t know “development” • A person who gets Azure benefits: https://www.microsoft.com/itprocloudessentials/en-US
- 8. My personal story – part 1 • Started with DOS 4.2 in 1987 at home. • Started professionally with NT4/Exchange 5.5 in 1996 at P&G. • 15y Exchange SME > version 2013. (Wrote a book and never touched Ex again ) • BPOS, BPOS, BPOS… • Office 365, Office 365, Office 365,… • Azure AD, Intune • Azure
- 9. How does an IT Pro look at Azure? • I can build Virtual Machines, I manage storage, networking,… • Azure is just a larger IT infrastructure, but it’s still IT infrastructure • I can easily build stuff and destroy it • My manager approves quicker, because the bill is lot less for ‘resources’ • “… if only I had some development skills…”, there is so much cool stuff in there
- 10. What is devops
- 11. What is DevOps and Why Now? • Isn’t DevOps another phrase for Agile? • Who is responsible for deploying code? • When deployments fail, who gets blamed? • How many production deployments do you perform per year? Month? Day? Hour? • What is stopping you from deploying faster?
- 13. CommonMisconceptions • DevOps is for cloud only companies • DevOps is for developers • Operations resources need to learn how to code • DevOps is only for cloud deployments • It works for small deployments but ours is complex
- 14. Traditional Development and Operations
- 15. DevOps: the three stage conversation
- 16. DevOps basics 2) Code Repository 1) Developers 3) Build 4) Test 5) Deploy to Cloud 6) Monitor and Improve Contoso App Azure
- 17. My personal story – part 2 • 2012: Azure Classic > great, but ugly portal • 2012: Azure Classic > Mainly around platform services • 2015: Azure Resource Manager > great portal • 2015: Azure Resource Manager > Azure Resource Manager Templates • 2015: Azure Resource Manager > Both IaaS and PaaS
- 18. Azure Resource Manager & Infrastructure as code
- 20. Challenges • Set Permissions • Monitor and alerting rules • Billing • Deployment • Communication ?
- 21. Resource Groups • Tightly coupled containers of multiple resources of similar or different types • Every resource *must* exist in one and only one resource group • Resource groups can span regions RESOURCE GROUP
- 22. Deployment • Tracks template execution • Created within a resource group • Allows nested deployments RESOURCE GROUP
- 23. Artifacts of a template JSON Files—Infrastructure as Code (IaC) Artifacts (optional depending on resources)
- 24. Taking advantage of existing templates Azure quick-start templates Azure Marketplace (portal)
- 26. ARM template structure { "$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#", "contentVersion": "1.0.0.0", "parameters": { // Parameters referenced by resources (parameterize your template) }, "variables": { // Variables referenced by resources }, "resources": [ // Virtual Machine, Web App, Virtual Network, SQL Azure, Storage Account, etc. ], "outputs": { // Optional outputs from deployment } }
- 27. Deployment template Deployment template parameters Deployment script Using Visual Studio / Visual Studio Code to author ARM Templates
- 28. Demo: Authoring aRM Templates using VS2017
- 29. Methods for deploying ARM templates • PowerShell • Azure Command-Line Interface (CLI) • Visual Studio • Azure portal • Continuous deployment
- 30. Deploying ARM templates Resource Group ARM
- 31. Optimizing I-a-C
- 32. ALM Framework Processes Environments Dev/Test Integration Pre-Production Production Develop Build Test Deploy Monitor and Learn
- 33. Microsoft Ecosystem that allows for DevOps Develop Build Test Deploy Environments Monitor and Learn Processes Dev/Test Production/Stage IIS VM SQL VM IaaS PaaS – Web App PaaS – Cloud Service
- 34. Heterogeneous Ecosystem Build Test Deploy Environments Monitor and Learn Processes Dev/Test Production/Stage Develop Alerting Monitor Configuration
- 35. Demo: “Devops-ing” a web app
- 36. Free Resources for DevOps Practices • Optimize your DevOps practices and tools: http://aka.ms/iac_tlp • Technical resources for Practitioners: • Get access to free online training: http://aka.ms/devopsmva • Trial of Visual Studio Online • Get started with a free Visual Studio Online account: http://aka.ms/vsotrial • Learn DevOps Practices hands-on with PartsUnlimited apps
- 37. The Phoenix Project Bill is an IT manager at Parts Unlimited. It's Tuesday morning and on his drive into the office, Bill gets a call from the CEO. The company's new IT initiative, code named Phoenix Project, is critical to the future of Parts Unlimited, but the project is massively over budget and very late. The CEO wants Bill to report directly to him and fix the mess in ninety days or else Bill's entire department will be outsourced. With the help of a prospective board member and his mysterious philosophy of The Three Ways, Bill starts to see that IT work has more in common with manufacturing plant work than he ever imagined
- 38. My personal story – part 3 • I love ARM Templates • I use Visual Studio 70% of my time, when working with Azure • I deploy, destroy, redeploy,… Azure resources • I use logic • …Over and over and over and over and over and over and over and over and over and over and over and over and over and over again…
- 39. Thank you for attending my session, have a great… Iselin, New Jersey
Editor's Notes
- #4: Title: Objectives Length: 2 minutes Participant Notes: After completing this module, you will be able to: Disaster Recovery features available in Azure Integrating Azure Disaster Recovery features in an SAP infrastructure Azure Site Recovery Azure Site Recovery for SAP VM infrastructure Make sure you address what this course will NOT cover based on experience.
- #5: Title: Objectives Length: 2 minutes Participant Notes: After completing this module, you will be able to: Disaster Recovery features available in Azure Integrating Azure Disaster Recovery features in an SAP infrastructure Azure Site Recovery Azure Site Recovery for SAP VM infrastructure Make sure you address what this course will NOT cover based on experience.
- #7: Title: Objectives Length: 2 minutes Participant Notes: After completing this module, you will be able to: Disaster Recovery features available in Azure Integrating Azure Disaster Recovery features in an SAP infrastructure Azure Site Recovery Azure Site Recovery for SAP VM infrastructure Make sure you address what this course will NOT cover based on experience.
- #8: Title: Objectives Length: 2 minutes Participant Notes: After completing this module, you will be able to: Disaster Recovery features available in Azure Integrating Azure Disaster Recovery features in an SAP infrastructure Azure Site Recovery Azure Site Recovery for SAP VM infrastructure Make sure you address what this course will NOT cover based on experience.
- #9: Title: Objectives Length: 2 minutes Participant Notes: After completing this module, you will be able to: Disaster Recovery features available in Azure Integrating Azure Disaster Recovery features in an SAP infrastructure Azure Site Recovery Azure Site Recovery for SAP VM infrastructure Make sure you address what this course will NOT cover based on experience.
- #12: Manual Error prone, time consuming, does not scale! Different deployment processes per environment Coordination between Dev, Ops, and stakeholders is difficult
- #13: If several people were to look at dev ops, how would they describe it? Some would say its collaboration Some would say: Infrastructure as Code (IaC) Continuous Integration Automated Testing Continuous Deployment Release Management App Performance Monitoring Load Testing & Auto-Scale Availability Monitoring Capacity Management Change/Configuration Management Feature Flags Automated Environment De-Provisioning Self Service Environments Automated Recovery (Rollback & Roll-Forward) Hypothesis Driven Development Testing in Production Fault Injection Usage Monitoring / User Telemetry And the truth is, that dev ops is all of those things
- #15: Taken from: http://dev2ops.org/2010/02/what-is-devops/ Development kicks things off by “tossing” a software release “over the wall” to Operations. Operations picks up the release artifacts and begins preparing for their deployment. Operations manually hacks the deployment scripts provided by the developers or creates their own scripts. They also hand edit configuration files to reflect the production environment, which is significantly different than the Development or QA environments. At best they are duplicating work that was already done in previous environments, at worst they are about to introduce or uncover new bugs. Operations then embarks on what they understand to be the currently correct deployment process, which at this point is essentially being performed for the first time due to the script, configuration, process, and environment differences between Development and Operations. Of course, somewhere along the way a problem occurs and the developers are called in to help troubleshoot. Operations claims that Development gave them faulty artifacts. Developers respond by pointing out that it worked just fine in their environments, so it must be the case that Operations did something wrong. Developers are having a difficult time even diagnosing the problem because the configuration, file locations, and procedure used to get into this state is different then what they expect (if security policies even allow them to access the production servers!). Time is running out on the change window and, of course, there isn’t a reliable way to roll the environment back to a previously known good state. So what should have been an eventless deployment ended up being an all-hands-on-deck fire drill where a lot of trial and error finally hacked the production environment into a usable state.
- #16: People = Culture Fundamental attributes of successful cultures: Shared mission and incentives: infrastructure as code, apps as services, DevOps/all as teams You need to consider your hardware as a commodity, (don't give your servers names) , servers are like farm animals, it is just harder if you let the ids name them Build deep instrumentation into services, push complexity up the stack Rally around agile, shared metrics, CI, service owners on call, etc. Changing the culture: any change takes time, changing culture is no exception and you can't do it alone, exploit compelling events to change culture: downtimes, cloud adoption, devops buzz PROCESS Definition and design, compliance, and continuous improvement PEOPLE Responsibilities, management, skills development, and discipline Products Tools and infrastructure
- #18: Title: Objectives Length: 2 minutes Participant Notes: After completing this module, you will be able to: Disaster Recovery features available in Azure Integrating Azure Disaster Recovery features in an SAP infrastructure Azure Site Recovery Azure Site Recovery for SAP VM infrastructure Make sure you address what this course will NOT cover based on experience.
- #33: In general, there are several components that make up an Application Lifecycle framework (ALM). You have people from different audiences that are interested in increasing the deployment flow. Underlying any ALM framework will also have processes that govern the application lifecycle. <<CLICK>> As developers create code, the code artifacts need to be tested. Code is integrated and deployed into different environments <<CLICK>> where the code is further tested. Sometimes by internal staff, sometimes by customers. Feedback is than captured as we monitor and learn from the deployments.
- #34: When we overlay the Microsoft ecosystem into this ALM framework, we see that Microsoft has several tools that can be used across the ALM lifecycle. There are also different targets for the deployments on premises. Full lifecycle from development to management. <<CLICK>> And cloud based environments hosted in Azure. These cloud based environments can also be a mix of PAAS and IAAS.
- #35: In a heterogeneous/open source environment, we see a different set of tools across the same landscape. Most of these tools are best of breed and used in most customers and partners today.
- #39: Title: Objectives Length: 2 minutes Participant Notes: After completing this module, you will be able to: Disaster Recovery features available in Azure Integrating Azure Disaster Recovery features in an SAP infrastructure Azure Site Recovery Azure Site Recovery for SAP VM infrastructure Make sure you address what this course will NOT cover based on experience.