Devops Journey
Total Page:16
File Type:pdf, Size:1020Kb
Enterprise DevOps Journey Carlos Gutiérrez Director DevOps Business Development International 8/6/2017 BizDevOps Powered by Business Agility Innovation and system of engagement Business velocity Deliver high quality software faster Minimum defects No security issues No legal issues Minimize Defects Build, test and deliver high qualityReach expectations software faster€€€ (that is the “real” monitoring) Maximize Velocity High IT Performers State of DevOps Report, ttps://www.ciosummits.com/Online_Assets_Puppet_2016_State_of_DevOps_Report.pdf Change Enterprise DevOps Journey DevOps Inspirations Single application Co-located teams Single stack “loosely coupled” infrastructure Less security and compliance risks Solely agile development A single deployment pipeline across a single application stack Simple application architecture Enterprise DevOps is different DevOps “Purist” Enterprise DevOps Single application Hundreds of applications Co-located teams Geographical dispersed teams Single stack “loosely coupled” Many environments including mainframe infrastructure both “loosely” and “tightly” coupled Less security and compliance risks Highly regulated and high security risks Solely agile development Multiple development methodologies A single deployment pipeline across a Multiple deployment pipelines across a single application stack vast heterogeneous system Simple application architecture Complex multi-platform architecture Challenges Culture Organization - Trust - Vertical - Failure - Cross team - Blame - Coach - Improvement - Skills Processes Technology - Agile Dev - Infrastructure - Config. Manag. - Architecture - CIntegration - Tools - Cdelivery… Some DevOps principles Agile Teaming & Visibility Cooperation Property Skills upon Continuous Measure Roles improvement Embedded Automation Fun! quality Challenges Culture Organization - Trust - Vertical - Failure - Cross team - Blame - Coach - Improvement - Skills Processes Technology - Agile Dev - Infrastructure - Config. Manag. - Architecture - CIntegration - Tools - CDelivery… Ch1: Organization From Functions to value streams Roles involved in SDLC Cornelia David, Senior Director of Technology, Pivotal. DevOps Enterprise Summit 2017. A possible organization Cornelia David, Senior Director of Technology, Pivotal. DevOps Enterprise Summit 2017. Challenges Culture Organization - Trust - Vertical - Failure - Cross team - Blame - Coach - Improvement - Skills Processes Technology - Agile Dev - Infrastructure - Config. Manag. - Architecture - CIntegration - Tools - CDelivery… Example Continuous Delivery Tool Chain Continuous 4 Inspection Agile Story Automated 0 Initiate CI Development & Task Unit & 1 2 3 Change Allocation Process Integration Tests Developer Commit & Planning Inspection VCS Build Deploy To System Deploy to Automated Deploy Auto Test Deploy Integration Test 7 6 5 UAT Testing Continue To Step B Auto Test Automated Package Deploy to Validation Manual 8 9 A Testing Staging Verification Example Continuous Delivery Tool Chain From step A Production Monitor Create Change Release to E Issues B C D Approval Production Application Warranty & Release Performance Incident Mgmt Approval Monitoring Create Business F Enterprise Change G Agility H Change Mgmt Development rd Agile Change 0 3 Party Change Change Requirements Request Mgmt Challenges Culture Organization - Trust - Vertical - Failure - Cross team - Blame - Coach - Improvement - Skills Technology Processes - Infrastructure - Agile Dev - Architecture - VC - Tools - CI/CD Technology • Mainframe • Lack of Automated Testing • Lack of Automated Deployments • Limited/Shared Testing Environments • Large Number of Tools and Practices • Tightly Coupled Release and Deployments • Large and Complex Legacy Applications • Enterprise Release Management Deployment Pipeline Micro Focus Stack The Journey to DevOps Plan Build Test Release Agile Practices Continuous Integration DevOps Practices Continuous Delivery Application Release Automation Example Continuous Delivery Tool Chain Continuous 4 Development Inspection Agile Story Automated 0 Change Initiate CI & Task Unit & 1 2 3 Allocation Process Integration Tests RHYTHM PULSE PULSE PULSE Developer Commit & Planning Inspection VCS Build DA SILK DA Deploy To System Deploy to Automated Deploy Auto Test Deploy Integration Test 7 6 5 UAT Testing DA / DA / Continue SILK RLC RLC To Step B Auto Test Automated Package Deploy to Validation Manual 8 9 A Testing Staging Verification Example Continuous Delivery Tool Chain From step A Create E Production Issues Change Release to Monitor B C D Approval Production Application Generic ITSM APM RLC RLC Warranty SSM & Release Performance SPM Incident Mgmt Approval Monitoring Create Business F Enterprise Change G Agility H Change Mgmt ITSM ITSM ATLAS Development rd Agile Change SSM 0 3 SSM Party Change Change/Config Requirements Request Mgmt Our understanding of DevOps at a glance Performance Defects Deployment Pipeline Plan Code Build Deploy Test Release Monitor Build’s trip throughout environments VC AR BUILD INT SYSTEM STAGING Deploy to next environment if points below are true Several pipes contribute to make an application Compilation þ INT env config þ System env config þ Staging env config þ Unit Test þ Deploy to INT þ Deploy to System þ Deploy to Staging þ Reviews þ Test data ready þ Test data ready þ Test data ok þ - Quality Stubs ready þ No stubs þ Acceptance test þ - Security Integration test þ System test þ Performance test þ - Peer reviews - Other experts Micro Focus Enterprise DevOps Solutions Deployment Pipeline Plan Code Build Deploy Test Release Monitor Agile Planning and Development: Atlas, Rhythm, Dimensions RM, Pulse, VC/ED, EA, COBOL Analyzer Continuous Integration: Dimensions CM, StarTeam, AccuRev, ZMF, ESync Continuous Delivery: Silk Central, Silk Test, Silk Performer, Data Express, TS Application Release Automation: DA, Release Control Monitor, Operate & Improve: SPM, SBM, SSM , ZMF Trends 2015 Gartner DevOps Survey 338 IT Business Leaders DevOps Engagement Model DevOps Engagement Model Initial Value Proof of Value Executive Sign Off & Meetings Workshop (PoV) Endorsement Project Initiation Inform about business Present SDLC Process, Arrange DevOps Procurement Process Define Use Case & objectives, urgency, and People, Tools & Roadmap Presentation to management and Success Criteria DevOps initiatives Challenges Stakeholders Contract Signature Customer Actions Arrange Meeting or Call Complete Applications with Executive or Provide Infrastructure Resources for project Landscape Questionnaire Stakeholders (as required) implementation allocated (L0Q) DevOps implementation Draft DevOps Roadmap Implementation Plan & Micro Focus Product examples by Micro Focus with Priorities and PoV SOW and RASCI Proposal License Customers Expected Benefits Micro Focus Deliverables Customer Need Mutually agreed action Resources allocated Understanding Summary plan (MAAP) (as required) Resources allocated by both parties Prerequisite Budget and Resources DevOps Roadmap with Investment Approved by Implementation Project available for joint Short Term Benefits for Confirm Executive or Executive Kick Off Scheduled Proof of Value Confirmed next steps Stakeholder endorsement DevOps Value Workshop Send the DevOps Value Workshop Agenda to the customer in time • Define Objectives • Resources required • Pre-Requisites • Format of the Workshop • Estimated times DevOps Value Workshop DevOps Engagement Model Worksheet – Current State Input: • Input from Business, Development, Test and Operations SMEs • Document Current SDLC • Identify Pain Points and their level of impact on the IT organisation and Business Goals Output: • Pain Point Heat Map DevOps Value Workshop – Heat Map DevOps Value Workshop DevOps Engagement Model Worksheet – DevOps Roadmap Input: • Pain Points Heat Map • Customer Experts to set priorities and define Proof of Value success criteria • Impact on Business Goals • Mapping Micro Focus Solutions to DevOps process stages • Describe Micro Focus Solution Value for each mapping and how to meet success criteria • L0Q High Level Customer Application landscape Output: • Draft DevOps Roadmap DevOps Value Workshop – Roadmap DevOps Value Workshop – Roadmap Building upon success • The code can compile • The code does what our dev thinks it should because it passed its unit tests • The system does what our analyst or users think it should because it passed all of the acceptance tests • Configuration of infrastructure and baseline environments is managed appropriately, because the application has been tested in an analog of production • The code has all the right components in place because it was deployable • The deployment system works because, at a minimum, it will have been used on this release candidate at least once in a development environment, once in the acceptance test stage, and once in a testing environment before the candidate could have been promoted to this stage • The version control system holds everything we need to deploy without the need of manual intervention, because we have already deployed the system several times Continuous Delivery, Jez Humble & David Farley, page 132 .