Driving Systems Stability & Delivery Agility through DevOps [Decoding DevOps Conference - InfoSeption]
2 likes1,223 views
The document discusses how VMware IT drives systems stability and delivery agility through DevOps practices. It summarizes how VMware IT automated instance provisioning to reduce provisioning time from 4-6 weeks to under 22 hours. It also discusses how VMware IT uses a cloud operations management platform for instance monitoring and management to improve operational efficiency. Finally, it outlines how VMware IT leverages a continuous delivery platform and service virtualization to improve application delivery agility.
Driving Systems Stability & Delivery Agility through DevOps [Decoding DevOps Conference - InfoSeption]
- 1. © 2014 VMware Inc. All rights reserved. Driving Systems Stability & Delivery Agility through Devops Insights from VMware IT! Gopinath Anantharaman Director, VMware
- 2. 2 Agenda 1 Context 2 IT Systems Stability & Agility Automated Instance Provisioning 4 Summary 3 Application Delivery Agility Instance Monitoring & Management Continuous Delivery Platform Service Virtualization Application Architectural Changes
- 3. Section 1: Context VMware IT Applications Delivery Eco-System
- 4. CONFIDENTIAL 4 VMware Applications Portfolio VMware vCloud Air Network Hybrid Cloud VMware Private Cloud Public Cloud My VMware ITB M
- 5. 2014 Operational Plan of Record CONFIDENTIAL 5
- 6. CONFIDENTIAL 6 Parallel Release Instances DEV13 LR:4/28/13 DEV14 LR:6/3/14 DEV15 LR:6/16/14 DEV16 LR:7/15/14 DEV11 LR:8/19/14 TEST13 LR:5/13/14 TEST14 LR:5/13/14 TEST15 LR:5/13/14 TEST16 LR:5/13/14 TEST11 LR:5/13/14 UAT LR:3/24/14 Load Test LR:3/24/14 (WDC) STAGE LR:4/17/13 (SC9) NR:10/28/14 NR:11/18/14 NR:12/30/14 NR:1/27/15 NR:TBD NR:11/04/14 NR:12/02/14 NR:1/06/15 NR:1/27/15 NR:8/19/14 vCHS TEST19 vCHS TEST20 vCHS Releases vCHS Releases NR:TBD Path to Production (Support Fix Path) 10/17 release train 11/7 release 12/05 release 1/23 release VMWSandbox PREDEV Instance DEV12 PREDEV Instance NR:9/20/14 NR:11/25/14 TEST12 Planned for provisioning PROD (SC9) NR:11/25/14 Pricing (Test31) (OC)
- 7. Section 2: IT Systems Stability & Agility Automated Instance Provisioning
- 8. CONFIDENTIAL 8 Responding to SMAC Era Disruption Corpor ate Strateg y Revenu e Cost Continuous Requirements Management Continuous Infrastructure Delivery Continuous Integration Continuous Deployment Continuous Delivery Continuous Dev & Test Product Development Transformation Respond with Continuous Delivery
- 9. Traditional Infrastructure Provisioning Process 4-6 weeks Delivery Cycle Request Infrastructure Verification Hardware Setup Build VMs – New or Clone DNS Entries Install, Setup, Configure Workload Database Refresh Latest Code Deployment Load Balancer Entries Web Server Configuration Firewall Changes External Interface & Integration PPM Tasks Workload Monitoring Setup Security – VM access control Testing 1- 2 days 3- 5 days 2 – 4 weeks 3 – 5 days 1 – 2 days 4 – 7 days 2 – 3 days 2 – 5 days 2 – 5 days 1 -2 days 2 – 4 days 1 – 2 days 3 – 7 days 2 – 3 days 1 day 5 – 6 days Task timeWait time CONFIDENTIAL
- 10. CONFIDENTIAL 10 Instance Provisioning Challenges Handoffs Silos. Globally distributed teams. Multiple application experts. Slow and Error Prone Many manual steps. Ticketing systems. Human error Capacity Constrained Only 4-6 projects in parallel Global Team Management PTOs, Holidays, Skill level
- 11. CONFIDENTIAL 11 Fix The “human middleware” on traditional infrastructure Replace and Automate End-to-end provisioning on SDDC Private Cloud Option 1 Option 2 Optimizing Instance Provisioning
- 12. VMware vCloud Suite CONFIDENTIAL 12 Automated and Software Orchestrated Instance Provisioning
- 13. Continuous Infrastructure Delivery in < 22 hours Virtual Data Center Virtual Server 40 work weeks effort – Per Release… 20 work weeks effort – Once! 22 hours 4 - 6 weeks Service Request Run Book Service Definition Blueprint Policy POC1 POC2 To Catalog Provision QA Staging Release It takes less effort/time to convert the runbook into blueprints than it takes to “run” the runbook...
- 14. Section 2: IT Systems Stability & Agility Instance Monitoring and Management
- 15. What’s Needed for Efficient Operations Management? What Is Needed? Quality of Service Reduce Mean Time to Identification (MTTI): • Visibility across Infrastructure and Applications • Proactive issue prevention • Quickly resolve business impacting issues Operational Efficiency Reduce Capital and Operating Costs: • Optimize use of resources to prevent unnecessary purchases • Improve team efficiency and increase VI/admin ratios Control & Compliance Adhere to IT policies and standards: • Compliance visibility to Operations • Enforce IT policies across assets and infrastructures Goal
- 16. VMware’s Cloud Operations Management Platform Cloud Operations Console Extensibility Integrated Management Disciplines Performance ComplianceMonitoringConfigurationCapacity Platform Services Analytics LogsDiscoveryReporting Automation SDK Management Packs APIs
- 17. Test Instance – vCOps Cockpit CONFIDENTIAL 17
- 18. LUNS Admin gets alerted that Oracle App is slow Oracle VM has performance issue Storage LUN health is red VNX | Target HBA Resets Target HBA Resets is high, limiting application performance Check LUN Details (EMC VNX: LUN44) IO OUTSTANDING DISK IO (870/1024) High I/O outstanding Check EMC VNX Analytics SP-A is red 1 2 34 Transaction latency above normal Scenario: Troubleshoot Across App, VM, and Storage
- 19. vCOps Benefits and Usage CONFIDENTIAL 19 Real time health status Monitor Health, Risk and Efficiency Static Thresholds Dynamic Thresholds Quick Isolation Right Sizing Opportunities Drill down to the resource detail
- 20. Section 3: Applications Delivery Agility Continuous Delivery Platform
- 21. DevOps is a Journey Automation / Infrastructure-as-a-Service Manual provisioning On-demand, automated self – service access Technology sprawl High standardization Initial provisioning Lifecycle management Homogeneous Enterprise wide / heterogeneous ExtensibleOne inflexible approach Virtualized infrastructure Any service from any layer Manual approvals High governance Journey with many starting points and many maturity levels Continuous Delivery / DevOps Standardized MW / Apps–as-a-Service
- 22. CONFIDENTIAL 22 How can you…? How do you glue it all together? 1. Ensure a consistent, repeatable & predictable software release process? 2. Get visibility into where a build is in the release process? 3. Ensure that the right artifacts are deployed every time? 4. Eliminate the costs and errors associated with manual tasks and hand-offs? 5. Really leverage the value from all of the tools in your software development release chain?
- 23. Integrated Dev. Env. Code Stream ties it together 24 Test ProductionUAT vRealize Code Stream Release Pipeline Artifact Management Dashboard VMware vRA (IaaS, MW & Apps) CUSTOM ANY PROVISIONING/DEPLOYMENT ENGINE Source Control Systems Build & Cont. Integration Repository Systems Troubleshooting
- 24. End-to-End Visibility Across the Pipeline • Provide a consistent view across stages and environments • Track artifacts to ensure consistent use • Enforce governance across stages via gating rules CONFIDENTIAL 25 Automated or manual gating rules Track the lifecycle of builds across environment & stages Automate artifact retrieval, provisioning, deployment, test and other tasks View task execution details
- 25. Section 3: Applications Delivery Agility Service Virtualization
- 26. What is Service Virtualization? CONFIDENTIAL 27 “In software engineering, service virtualization is a method to emulate the behavior of specific components in heterogeneous component-based applications such as API-driven applications, cloud-based applications and service-oriented architectures.” • Emulate Component • “Capture” & Automation Techniques to provide Scenario Breadth • It’s NOT a dummy stub
- 27. 28 VMWare IT Delivery – Challenges and SV Needs I can’t do much until I have an integrated working environment! Dev/Test Environments Interfaces need virtualization in the absence of source and target end points Target System Virtualized services to speed up development Reduce dependence on integrated SDLC Test data preparation is slow painstakingly slow for capturing end to end cases. Unavailability of enough application instances - timesharing application across SDLC instances. Automation is limited to well defined test cases and requires relevant test data. ChallengesSVNeeds Test Data Reduce test case data setup for every system they touch Ability to record once and replay test data many times Service/Function specific data setup Test Automation Capture directly or import from transactions, databases, files Dynamically adjust data for time or situational relevance Component level automation requires advanced interception and data capture techniques Our IT projects have impact on multiple systems and users. An Integrated Environment has become the basic requirement to deliver even a small fix. Virtual Services ensure that test data and test environments are always available for QA and Dev. They can be developed in less time and can be consumed by multiple environments. CONFIDENTIAL
- 28. 29 Service Virtualization Benefits Faster, Cheaper and Better - Doing More with Less! Reduce Infrastructure footprint SaaS & On-Premise System The 20+ SaaS & Several Enterprise On-Premise systems could be SV’ed and hence eliminate the need for these altogether in Dev/Test Instances. Instance Provisioning The SDLC Instances can be provisioned rapidly and on-demand. New Development - Dependent Systems availability and SV’ed interfaces enable individual track owners to develop independent of other teams. Parallel Development - Multiple Release Trains can co-exist with visibility of services being newly built available to future Releases. Parallel Development Shift-Left Functional QA Automation Shift-Left Functional Testing can start much earlier in the cycle, as soon as SV’ed code is available in the Dev Instance. QE Automation can start much earlier (as opposed to starting middle of QA cycle right now) based on SV contracts. This also forces teams to write Test cases earlier. Overall Quality Improvements due to the breadth of coverage via SV. Data Conflicts – help in managing data conflicts due to it being overridden by other development teams. Data Setup Time - Reduce overall data setup time. Test Data Management
- 29. Section 3: Applications Delivery Agility Application Architectural Considerations
- 30. Application Architectural Considerations CONFIDENTIAL 31 Architectural Governance Driving Services Reuse Micro Services Enablement Service Virtualization Enablement VMs + Containers, Better Together Supportability Requirements Runtime Application Insights
- 32. Reduced provision time 95% (4 weeks to 22 hours) Improved productivity of 600 developers 20% Reduced IT operations costs $1.5M /year Able to say “yes” to developer requests Reduced the cost of a VM/month 80% ($133 to $20) Reduced infrastructure costs $4.5M/year Key Stats
- 33. CONFIDENTIAL 34 Embracing the Digital Era 1. Reduce Complexity 2. Dramatically Lower Costs 3. Enable Flexible, Agile IT Service Delivery to simplify operations and maintenance to redirect investment into value-add opportunities to meet and anticipate the needs of the business Drive IT Agility to Increase Business Value