Declarative Configuration Management with Azure Automation DSC and ARM Nathan Lasnoski Vice President of blog.concurrency.com Concurrency Christopher Mank blog.concurrency.com Concurrency

@cmank7 Microsoft MVP 5 years in consulting Hot dogs and mac and Microsoft MVP 15 years in consulting My wife’s meatloaf Christopher Mank Nathan Lasnoski

Presentation Just a placeholder slide. Please use the example slides in the “Template Example Slides” Section. Questions?

@cmank7 Microsoft MVP 5 years in consulting Hot dogs and mac and Microsoft MVP 15 years in consulting My wife’s meatloaf Christopher Mank Nathan Lasnoski

Presentation Just a placeholder slide. Please use the example slides in the “Template Example Slides” Section. Questions?

The industry is moving toward DevOps PEOPLE Collaborate more Share common goals Focus on improvement BRINGING PEOPLE TOGETHER PROCESS Eliminate waste Increase efficiency Streamline feedback DELIVERING VALUE FASTER TOOLS Enhance productivity Enable collaboration Facilitate experimentation EXECUTING A DEVOPS STRATEGY

What is DevOps? “It’s Development and Operations collaboration” “It’s a job title” “It means faster and smaller releases” “It’s automation”

PRACTICES Automated Testing Continuous Integration Continuous Deployment Release Management PRACTICES Usage Monitoring Telemetry Collection Testing in Production Stakeholder Feedback PRACTICES Testing in Production Usage Monitoring User Telemetry Stakeholder feedback Feature flags PRACTICES Code Reviews Automated Testing Continuous Measurement PRACTICES Application Performance Management Infrastructure as Code Continuous Delivery Release Management Configuration Management Automated Recovery PRACTICES Application Performance Management Infrastructure as Code Continuous Deployment Release Management Configuration Management Automated Recovery PRACTICES Enterprise Agile Continuous Integration Continuous Deployment Release Management FLOW OF CUSTOMER VALUE TEAM AUTONOMY & ENTERPRISE ALIGNMENT BACKLOG refined with LEARNING EVIDENCE gathered in PRODUCTION MANAGED TECHNICAL DEBT PRODUCTION FIRST MINDSET INFRASTRUCTURE is a FLEXIBLE RESOURCE DevOps habits and practices

Microsoft’s ALM framework

Configuration Management v1 What it does Facilitates asset and inventory functions How it works Manual tracking of configuration data Gathered from tools or physical inventory Lives in spreadsheet or light CMDB

Configuration Management v2 What it does Facilitates asset and inventory functions Informs change management Automation against CMDB data How it works Automated tracking of configuration data (connectors) Gathered exclusively from tools Lives in a CMDB

Configuration Management v3 What it does Declaratively defined configuration deployment Validation of deployed configurations based on tooling Automation against CMDB data Informs change management How it works Declarative configuration push / pull to targets based on a configuration file Tracking of configuration data through tooling Declarative configurations live in source control Configuration database provides inventory data

Microsoft’s ALM framework

How to build Configuration Management v3 Source Control (VSO, GIT, etc.) Infrastructure as Code (ARM) Configuration Language (PowerShell DSC, ARM) Configuration Tooling (Azure Automation DSC) Configuration Repository (Azure Automation DSC) Configuration Deployment Mechanism (PowerShell DSC) Configuration Management Database (OMS / SCSM)

Azure Resource Manager (ARM) Infrastructure-as-code language and platform for: Azure cloud Azure stack on-premise Provisions infrastructure based on JSON template Can be combined with PowerShell DSC configurations Gallery of templates ready to work with Best edited within Visual Studio

Demo ARM Templates

PowerShell DSC Microsoft’s platform for configuration management replacing: Group policy Manual configuration Non-declarative scripting, batch files, etc. Declarative configuration is applied on push or pull Multi-platform (Microsoft, Linux) Multi-location (on-prem, Azure, AWS) Facilitates re-application of configuration

Components of PowerShell DSC Authoring Written in PowerShell DSC syntax Stored in a source repository Staging Declarative configuration creates MOF files (stored in Azure Automation DSC) Configuration is built for all nodes requiring MOF Apply Configuration is “pulled” or “pushed” to targets of MOFs Each configuration is declarative and will overwrite previous settings

DSC Configuration Traditional Scripts (Imperative) Configuration (Declarative)

DSC Configuration

Azure Automation DSC Configuration Tooling Stores the compiled PowerShell DSC configurations (MOFs) Deployment mechanism to deploy PowerShell DSC configurations Reporting of deployed configurations

Demo PowerShell DSC

Putting it all together Source Control (VSO, GIT, etc.) Infrastructure as Code (ARM) Configuration Language (PowerShell DSC, ARM) Configuration Tooling (Azure Automation DSC) Configuration Repository (Azure Automation DSC) Configuration Deployment Mechanism (PowerShell DSC) Configuration Management Database (OMS / SCSM)

Demo ARM + DSC

How do I get started? Getting off the ground Create a free OMS instance and enable Azure Automation DSC Check our getting started blog Determine your ideas Low hanging fruit you can accomplish in a couple days A single configuration setting you desire to distribute

And Then …

Section HeaderSection Header This is the next section

Title Line1 Line2 Line3 Line4 Line5 Line6 Bullet Level 1 Bullet Level 2 Bullet Level 3

Title Code

Text Only with Border Level 1 Level 2 Level 3

Text Only without Border Level 1 Level 2 Level 3

Title Text 1 Level 1 Level 2 Level 3 Text 2 Level 1 Level 2 Level 3

Section 1 Text Level 1 Level 2 Level 3 Section 2 Text Level 1 Level 2 Level 3 Title

Demo Demo Title