1 / 29

Jakob Gottlieb Svendsen

Jakob Gottlieb Svendsen. System Center Orchestrator 2012 Runbook Design 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

kail
Download Presentation

Jakob Gottlieb Svendsen

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Jakob Gottlieb Svendsen • System Center Orchestrator 2012 Runbook Design 101

  2. 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)

  3. Agenda • Introduction to Orchestrator • Runbook Planning • Runbook Design • Best Practices • Logging • Stage Tracking

  4. Introduction

  5. Orchestrator Concepts Databus Activities Runbooks Collection of Activities Executes a task Published Data from Activities UpdateService Request Get Data Source Create Recovery Point Run .Net Script Invoke Web Services Send e-mail Create Checkpoint Create Incident Start Maint Mode Shut Down VM Check Schedule Update on success E-mail on error Return Data Compare Values Query Database Clone Linux VM

  6. Integration Packs • Solution or Application specific • Provide ready-built defined activities • Packaged and Deployed • Brings version control to activities • Microsoft and Partner provided • All major enterprise management products • HP, IBM, CA, BMC, EMC • Build your own with the Integration Toolkit! • Leverage the Community ecosystem

  7. Basic Example - Deploy Web site Create Folder Copy Content Create Web Site Test Web Site

  8. Demo Basic runbook

  9. Runbook Planning

  10. When to Automate Activities ? Time Consuming Easy to Automate Occurs Often Visible to Customers High Risk Breaches SLA Often

  11. Identify the best processes • Is the process optimized and standardized? • Is SCO the right tool? • Development Cost vs. Manual Process • Ports & Permissions?

  12. Scenario 1 – Basic Task Automate “manual” task 1 time every month Takes 20 minutes to do 1 week to build runbook 20 minutes x 12 months = 4 hours per year 40 hours / 4 hours = 10 years

  13. Scenario 2 – Incident Remediation Automate “Service Stopped” alerts 1 alert every day 1st line receives and forward (5 mins) 2nd line RDP and fix (15 mins) 1 week to build runbook 20 minutes x 365 days = 121 hours per year 40 hours / 20 minutes = 120 days = 4 months

  14. Customer Request / Dream Invent “Skynet” The runbook will monitor this system for new objects, then it will… and if it is like that it will… then it will integrate with… and pass data into… …We don’t think it will take more than 14-18 months to build the solution. …By the way, we have never used Orchestrator before

  15. Runbook Design

  16. Demo Design Guide – Best Practice

  17. Design Guide Folder and runbook structure Naming convention Variables Library of standard runbooks Rename activities Use link labels & colors Success Warning / Failed “Could be” Left to right

  18. Demo Watch Out!

  19. Watch out! • Successmight not equal to your expectation • No Loops in Links – Only on activity level • Multiple Results (Multi-value published data) • Library runbooks might be in use!

  20. Logging Don’ts Do’s Custom Database IP for Standard Logging (codeplex) SCSM – Action Log Make your own IP using the Wizard • Text File • Event log (except SCOM monitors) • Platform Event • Built-in “Activity Specific Logging”

  21. Demo Logging!

  22. BuildModules • Doesonetask • Easier to develop and test • Can beused in multiple scenarios • Do not usewhen handling a lot of executions • Adds a delay of a couple of seconds per execution.

  23. Demo Modules

  24. Fail-Over • Infrastructure • Multiple Runbook Servers • Runbook • Design to support failover • Resume at the correct stage (staging)

  25. State Tracking • Integration Pack for Standard Logging • Custom Database • Service Manager

  26. Demo State Tracking

  27. Windows Server 2012 R2 Support Service Management Automation Windows Azure Pack Runbook Workers System Center Integration Pack for Microsoft SharePoint System Center Orchestrator R2

  28. Summary • Start small / simple • Planning makes development much faster! • Use Service Manager for staging support

  29. Pleaseevaluatethesessionbeforeyouleave

More Related