1. Travis Wright
SCSM SSP WAP SMA PS
How a Bunch of Letters Can Help Deliver
Solutions Faster, with Fewer Issues, Save
Money, Impress the Boss, and Get You a
Promotion
4. Learn PowerShell or practice the
phrase “Would you like fries with
that?”
-Don Jones, PowerShell MVP
Blue Collar IT vs. White Collar IT
Jeffrey Snover, Windows Server Lead Architect, Distinguished Engineer, Father of PowerShell
http://www.youtube.com/watch?v=66cYDdmF9u0#t=64
5. Value of Automation
•
•
•
•
•
Lower costs
Reduce time to completion
Minimize human error
Ensure processes are followed and documented
Abstract away high security operations
7. Introducing PowerShell Workflows
•
•
•
Workflows are a PS construct similar to a function or cmdlet
They are converted to and executed as a Windows Workflow
Foundation workflow at runtime
Workflows are different from a function/script/cmdlet
•
•
•
•
•
•
•
•
Some commands don’t work unless they are in an InlineScript block
Workflows can execute commands in parallel or in sequence
Variable lifetime is handled differently
Workflows can persist state
You can suspend/resume a workflow
Workflows “survive” OS shutdowns or network outages
Logging and retry are handled by workflow engine
Runs activities. Cmdlets are run inside of an InlineScript block
14. Parameters
• Parameter names can only be letters,
numbers, hyphen, underscore
• Hyphenated parameter names must be
enclosed in quotes
• Parameters can be mandatory
• You can create parameter sets
16. Persistence
• A checkpoint stores the current variable values, output, and
current command to disk in the user profile of the user
running the workflow
• All checkpoints are removed when the workflow completes
unless the –AsJob was used in which case it remains until
the job is deleted
• -PSPersist $true: creates a checkpoint after each activity
• -PSPersist can also be passed to an individual activity
• Checkpoint-Workflow activity can be used anywhere in the
workflow
17. Parallelism: ForEach -Parallel
• ForEach –Parallel can be used to For Each through a
collection executing the commands contained by the For
Each in parallel
• Order is non-deterministic because it depends on each
item’s variable completion time
• Max degrees of parallelism: 5
18. Parallel/Sequence Block Example
• Commands in a Parallel
block execute in an
indeterminate order at the
“same” time
• Max degree of parallelism: 5
• Commands in a Sequence
block execute in order
21. Service Management Automation (SMA)
•
•
•
•
•
SMA is a component in the Orchestrator setup
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 for existing resources or to connect into 3rd
party systems (ticketing system, billing system, etc.)
Check out the Building Clouds Blog for an Introduction
to SMA http://aka.ms/IntroToSMA
22. SMA Advantages Over Orchestrator
•
•
•
•
•
•
•
•
•
•
64-bit support
Native PowerShell execution and PowerShell 3+ support
Checkpoint/restart inside runbooks
Runbook servers architecture is more scalable
Ability to export selected variables, using the SMART tool
Save drafts
Versioned runbooks
Schedule runbooks
Parallel processing
Text authoring vs. visual designer
23. SMA Architecture
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
24. Integration of Orchestrator and SMA
•
•
System Center 2012 R2
Orchestrator
supports both PowerShell
Workflow
and Graphical Authoring
Call SMA from Orchestrator or
call Orchestrator from SMA
PoSh Authoring
Interop
Graphical Authoring
http://bit.ly/1ciQZZc
PoSh Workflow Engine
UI Runbook Engine
Process Automation
26. WAP At a Glance
TENANT & ADMIN
PORTALS
SERVICE MANAGEMENT API
WEBSITES
DATABASES
SERVICE BUS
VIRTUAL
MACHINES
VIRTUAL
NETWORKS
27. WAP Architecture
Tenant
Portal
Service Admin
Portal
Service Management API
PaaS Provisioning
and Management
Engine
Service SQL
Bus
Server
IIS
Service Provider Foundation
(Tenant, Admin, Usage)
Virtual
Machine
Manager
Orchestrator
Hyper-V
Windows Server
Operations
Manager
28. Microsoft Cloud OS Vision
Microsoft Cloud
Windows Azure Platform
Windows Azure Pack
1
Windows Azure Pack
Consistent
Platform
Private Cloud Service Providers
31. SCSM Overview
Connectors
System Center – Configuration Manager
System Center – Operations Manager
System Center – Orchestrator
System Center – Virtual Machine Manager
Active Directory
Exchange
IT Service Management Solutions Service Management Automation (SMA)*
Incident & Problem Management
Service Request Fulfillment
Change & Release Management
Configuration Management
CMDB
Platform
DW
Workflow
Knowledge Management
Self-service Reporting
Self-service Portal
Service Catalog
.NET API Notifications
Asset Management*
Console & Forms
Security
* Cireson Products
32. SCSM–SMA Integration (Cireson SMA Connector)
Key Scenarios
Include a SMA runbook activity in a work item
process
Example: New AD User service request/request
offering
Subscription workflows trigger SMA runbooks
Example: Automated incident troubleshooting
33. SCSM-SMA Connector Key Design Points
•
Connector object
•
•
•
•
•
•
•
•
•
Derives from Activity Work Item class
Can be included in parent work items just like any other activity work item
Generic properties like SCO runbook activity (Text1..10, Boolean1..5, etc.)
Stores mapping of properties to runbook parameters
•
•
•
Persisted, shared connector configuration
Securely encrypts and stores credentials
Doesn’t sync data into SCSM CMDB like other connectors
Subscribe to create/update of any class of objects in CMDB
•
•
•
View Runbook
View Runbook Job
Start Runbook Now
No “runbook” objects in CMDB like SCO integration – no “contract”!
SMA Runbook Activity Work Item Class
SMA runbook subscription workflow wizard
Helpful Views and Console Tasks
36. Self-Service Portal Features
• Service Catalog
• Make service requests
• Report incidents
•
•
•
•
View/update requests
Search knowledge base
Approve/reject requests
Update activities assigned to you
37. Out of Box Portal vs. Cireson Portal
Out of Box Portal
•
•
•
•
•
•
•
•
•
Built on SharePoint
Requires Silverlight
Limited style customization
Lots of clicks and scrolling
Service catalog, my
requests, knowledge base
Poor performance/scale
Doesn’t work on x-plat/mobile
Internet-facing not supported
Windows-integrated auth only
Cireson Portal
•
•
•
•
•
•
•
•
•
No SharePoint required
HTML 5, No Silverlight
Complete style customization
Minimal clicks and scrolling
Service catalog, my
requests, knowledge base +
analyst portal
Excellent performance/scale
Works on x-plat/mobile
Internet-facing supported
Windows-integrated/forms auth
Web SitesWeb Application PaaSHighly ScalableDev-ops optimizedIntegrated SCCFully self-serviceDatabasesSQL Server databaseConfigurableManageableService BusReliable MessagingStandards BasedCross Cloud Virtual Machines:IaaS - Elastic TiersWindows and LinuxGallery of appsVirtual NetworksSoftware defined networksNetwork isolationTenant and Admin PortalsModern look and feelFederated IdentitiesActive Directory integrationStandards BasedDevice FriendlyEnterprise readyHighly scalableProvides usage statistics for chargebackAPIs for integration into billing systemsConfigurable subscriptions, plans, and quotas4:25
Katal is really just an extension of your existing System Center deployment. It is everything you see in green. It sits on top of System Center. For example, when you request a virtual machine to be deployed from the tenant portal that request goes through the SM API to the SPF API to SCVMM and finally the VMM agent on a Hyper-V host is instructed to deploy that VM.The utilization data that is displayed in the tenant portal is collected by Operations Manager and retrieved via the SM API and the SPF API.:45
Let's visualize what we mean by this Cloud OS Vision. First of all, starting really with WS 2012 and SC 2012 SP1 we enabled the "private cloud". Using Hyper-V as the virtualization layer in Windows server, improvements in storage management, and of course using System Center to configure and manage it all, an enterprise customer can have cloud computing in their own datacenter.Around the same time Azure and Office 365 came online as supported services from the "Public Cloud". A customer could use these SaaS services or use Azure PaaS. Then along came Azure IaaS virtual machines allowing a customer to consume cloud computing from outside their own datacenter and their own organization. We don't normally like to talk about this but before Windows Server 2012, Azure was using its own branch of the Hyper-V hypervisor. Azure has now fully adopted the same hypervisor that ships in Windows Server.At the same time some service providers were starting to offer IaaS built on the Microsoft Windows Server and System Center stack. But, honestly very few. Lots of IaaS service providers offer Windows as a guest, but very few of them were using Windows and System Center as the infrastructure layer.With the introduction of the Windows Azure Pack along with System Center 2012 SP1 earlier this year we brought pieces of the Azure software platform to service providers and enterprises. In the Windows Server/System Center 2012 R2 release we will bring even more of that software platform from Azure to service providers and enterprises. By taking software from Windows Server such as Hyper-V and running it in Azure and taking software from Azure and running it at service providers and enterprises we are creating one consistent Cloud software platform across all three types of locations. That is the Cloud OS.Now, let’s look at how Microsoft goes about building this Cloud OS.4:00