System Center 2012 R2
Windows Azure Pack
Service Management Automation 101
Who am I
•
Jakob Gottlieb Svendsen - @JakobGSvendsen
•
Profession
Chief Developer, Coretech A/S, System Center Gold Partner
•
Titles
•
•
System Center Cloud and Data Center Management MVP
•
Windows Azure Pack / SMA
•
Orchestrator + Extensions for SCSM + SCOM
•
VBScript / PowerShell / VB.NET / C#.NET
Communities
•
•
Co-Founder of the Danish PowerShell User Group (www.psug.dk)
•
Moderator on Microsoft TechNet Forums
Author
•
•
Service Manager 2012 Unleashed (contributing author – Release June 2014)
•
Mastering System Center Orchestrator 2012 – 3 day workshop
•
Windows Azure Pack - SMA Workshop/course (in development)
•
Advanced SCOM management pack design/development Workshop/course (in development)
Service Management Automation (SMA)

System Center 2012 R2 Orchestrator adds support for
PowerShell Workflows through the SMA feature

Browser-based runbook authoring integrated into the WAP Admin Portal

Supports requirements for scale and high availability

Import PS modules and create additional modules and runbooks

Check out the Building Clouds Blog for an Introduction to SMA
http://aka.ms/IntroToSMA
Service Management Automation
Demo
Introduction
Introducing PowerShell Workflows

Workflows are a PS construct similar to a function or cmdlet

Converted to and executed as a Windows Workflow Foundation workflow

Workflows are different from a function/script/cmdlet

Workflows can execute commands in parallel or in sequence

Workflows can persist state

You can suspend/resume a workflow

Workflows “survive” OS shutdowns or network outages

Runs activities. Cmdlets are run inside of an InlineScript block
Service Management Automation
Demo
First runbook
SMA enhancements to PowerShell Workflow

High availability workflow execution backed by SQL Server

Centralized, machine-independent store
 Variables,
Credentials, Connections, Certificates
 Schedules,
 Modules,
 Built-in
Actions (Trigger on Events)
Workflows, Checkpoints
versioning for workflows and modules

API interface over HTTP (Odata web service)

Historical view of all workflow jobs and their output
Service Management Automation
Demo
Triggers
+
Schedules
SMA : Architecture and Installation
Web Service
•
Standard interface for all of SMA
•
Security group controls access
•
HTTPS support to secure connection to clients
Runbook Worker
•
All runbook jobs are picked up by one or more runbook workers
•
Runs under a service account
PowerShell Module
•
SMA PowerShell module to enable management of SMA through
cmdlets
Service Admin Portal integration
•
Connect the Service Admin portal to the SMA web service
SMA : Architecture and Installation
Service Management Portal
Service Management Portal
Http Response
• Authoring
• Debugging
• Operating
Http Request
Runbook Workers
ODATA REST Web
Service
Return results
• Runbook service
• PowerShell Modules
Web Service
SQL
Database
Runbook Workers
• REST oData web service
• Authorizes users
SMA Database
Submit requests
Runbooks
Pick up Jobs
Jobs
Persist State
Modules & Activies
• Runbooks
• Runbook Resources
• Tracks runbook job state
Service Management Automation – Minimum Setup
WAP Database
WAP
Admin API
Admin Portal
Orchestrator/SMA
Web Service
Runbook Worker
Powershell Module
http://technet.microsoft.com/en-us/library/dn296433.aspx
SMA Database
Service Management Automation
Demo
Check Points
SMA Architecture with Service Manager
Cireson SMA Connector
SCSM Console
SCSM Workflows
Cireson SMA Connector
Windows Azure Pack Admin Portal
SMA PowerShell Module/Cmdlets
Service Management Automation Web Service API
SMA
Service Management Automation Runtime
PowerShell
Windows Workflow Foundation
SMA : Runbook Authoring and Tools
 Things
to consider when creating SMA Runbooks
 Check
Out: http://aka.ms/IntroToSMA
 Tags
 Logging
 Progress
 “Atomic”
Runbooks that are modular in nature
Service Management Automation
Demo
Logging / Progress
SMA : Runbook Authoring and Tools

Easy Import / Export

Use SMART for Runbook Import and Export

http://blogs.technet.com/b/privatecloud/archive/2013/10/23/automationservice-management-automation-sma-runbook-toolkit-spotlight-smart-forrunbook-import-and-export.aspx
Service Management Automation
Demo
Import Export
SMA : Working with modules
Creating SMA friendly PowerShell modules
•
Include for every cmdlets
•
Synopsis
•
Description
•
Help uri
•
Cmdlet should be able to take in a connection object as a parameter.
•
Cmdlets in the module should be stateless
•
Define output type for all cmdlets (IntelliSense)
SMA Advantages Over “Classic” Orchestrator

64-bit support

Native PowerShell execution and PowerShell 3+ support

Checkpoint/Resume inside runbooks

Runbook servers architecture is more scalable

Save/Test drafts

Versioned runbooks

Schedule runbooks

Parallel processing inside runbooks
Text authoring vs. Visual Designer
Integration of Orchestrator and SMA

Orchestrator
supports

PowerShell Workflow

Graphical Authoring

Call SMA from Orchestrator

Call Orchestrator from SMA
http://bit.ly/1ciQZZc
Moving Runbooks and Concepts
from Orchestrator to SMA

Sample migration case & Tools available to help

2-part blog post series about calling an Orchestrator Runbook from SMA, and integrating with Service
Manager


Orchestrator and SMA integration in action


http://blogs.technet.com/b/privatecloud/archive/2013/11/01/calling-an-orchestrator-runbook-from-smapart-1.aspx
http://blogs.technet.com/b/privatecloud/archive/2013/12/11/automation-fun-with-orchestrator-and-smaintegration-points.aspx
Smart for Runbook Conversion

http://blogs.technet.com/b/privatecloud/archive/2013/11/25/automation-service-management-automationsma-runbook-toolkit-spotlight-smart-runbook-conversion-helper.asp
Thank You

Jakob Gottlieb Svendsen - @JakobGSvendsen


http://blog.coretech.dk/jgs
PowerShell User Group

http://www.psug.dk