1. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. HP Operations Orchestration Use Case Automated Application Release Hilton Rosenfeld CEO Stratospheric

2. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 2 Agenda The Customer The Business Problem The Existing Release Process The Automated Release Process − Constrains and Requirements − Methodology and Design Principles − Implementation Business Outcome Maintainability

3. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 3 The Customer Australia’s largest media company News Corp is the world's 2 nd largest media conglomerate (behind Walt Disney) Extremely Siloed Many duplicate tools Very Immature IT Processes Disillusioned with HP Market Cap: US$76 B Staff: 8,000 (Australia) 25,600 (Global) Products: Newspapers Magazines Internet Services: Pay TV National Rugby League Market research DVD and Film distribution Film and TV production News Corporation

4. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Product views may not represent actual product screens. 4 The Business Problem Releases to test environments are currently handed over to Operations for actioning. This causes a lag in the dev, test, ops cycle. “…if releases can be automated this will increase our ability to deliver to our customers in a timely fashion…” Internal News presentation to secure funding CDP Phase 2 The automation of application deployments to test environments Iteration 1 : Fatwire February 2013

5. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Existing Release Process

6. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 6 Developer Creates JIRA Ticket Release Details Includes: Title Application Version Target Environment Schedule Impact, Urgency, Priority, Risk Build Results Dependencies Artefacts (release components) Release Tasks – (release steps) Copy into an SM7 Change Ticket The ticket is populated with the release details and emailed to Operations

7. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 7 Manually applied to multiple servers using Linux Shell Operations Apply Changes Operations Tasks: Notification arrives via email that a release is scheduled Execute the release upon SM7 approval Release Method: − On each server, the operator will open a shell and type in the commands. − This relies heavily on the operators knowledge as the instructions in the Jira ticket are not very detailed. − If anything fails, the operator will mark the SM7 ticket as failed and escalate back to developers. Time Required = 2 - 4 hours

8. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Automated Release Process

9. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 9 There is a better way Constraints and Requirements Automate the deployment of application packages across non-production environments. Support multiple applications / versions, to any environment. HP OO by itself is not the ideal solution to this requirement We tried to position Continuous Delivery Automation or SA with ADM BUT The customer refuses to spend on any new software (especially HP) They have a preference for develop first, buy second

10. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 10 The OO Flow Design Principles Methodology Invent a machine readable structure for release steps Use sub-flows. This is a complex process that has to be broken down into smaller pieces Experiences and lessons learned? Customer did not understand the process until we automated it Some processes are not suited to OO Dynamically set the RAS. Use a global Error Handler Enable SME contributors to author content

11. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 11 XML Data Structure How to represent free text instructions in OO readable form. Analysed hundreds of JIRA tickets and their instructions. Instructions comprise few unique steps that are repeated often. Selected XML to represent the data, as it is naturally structured. Fatwire 9.7.4 SIT1 Impact,Unify,Methode,Social,CDP C145728 20121217 rpm news-centraltech-fatwire-cs-war 9.7.4 http://nexus.ni.news.com.au/nexus?v=9.7.4&e=rpm&c=rpm authoring all publishing:stop root authoring all tomcat:stop tomcat sudo /etc/init.d/cs_tomcat stop Used to ensure that the release instructions are machine readable

12. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 12 Dynamic RAS Selection A discrete RAS is deployed in each environment across the two data centres resulting in 6 RAS services. Dependent on the release target, a RAS must be selected at run time. Essential for a multi data centre environment OO makes this easy! You can override the RAS reference by setting a value for ${overrideRAS}. In our flows we query the target environment and dynamically set the value of ${overrideRAS}. Note: This has changed in OO v10

13. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 13 Transitions Error Handling Transitions connecting to Error Responses should be as descriptive as possible − The transition text can include variable substituition − The transition text can be accessed using ${RS_Previous_Transition}

14. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 14 Operations Error Handling Operations should have a result defined to capture any detailed error messages − This must be configured per operation, as each operation will have unique error messaging

15. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 15 Error Responses Error Handling Error Responses need an input defined to capture the failure transition text and error message Error Responses need a flow output field defined to allow parent flows access to error messages Input to hold error message: errorTMP = ${RS_Previous_Transition} - ${errMessage} Output for parent visibility: errMessage = Flow Output Variable

16. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 16 Global Error Handler A global Error Handling sub-flow Caters to all required error handling methods Change Ticket Incident Ticket Log File Windows Event Log Email Simple to configure Set each option to on / off Provide error message Insert before final exit response

17. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Product views may not represent actual product screens. 17 Implementation Web Portal front end Developers need a system to enter release instructions Temporary web page created Drop Down menus avoid errors Template Option for common deployments Generates XML data Creates SM7 Change ticket

18. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 18 The Flows

19. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 19 An initial win, a larger outcome Business Outcome Release is now completely automated Time Required = 15 minutes Errors still occur due to bugs in the release artefacts No effort invested to improve the process No agenda to increase the scope of the automated release to additional environment or applications News Corp decided to use OO for IT Operations and Service Desk

20. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 20 Reporting Dashboards Are very good for management visibility of what OO is doing in the environment ROI chart is a big win Auto Generated Reports Created from the flow images, description texts and flow inputs/outputs. Easily customised with HTML/CSS Dashboards and Auto Generated Reports

21. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 21 One of the original requirements Maintainability Two important requirements were Reporting and Maintainability OO Platform Architecture documented and handed over to customer tools team. HPLN configured, documented and tested. Considerable effort put into documenting flows in Description tabs. Auto Generated documentation flow scheduled. Training for 5 customer staff on OO Authoring Support Contract in place.

22. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. 22 Resources and Contacts

23. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Q & A

24. © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Thank you