Quali webinar de-mystifyind dev_ops-a practitioner’s perspective
- 1. De-mystifying DevOps A Practitioner’s Perspective Sept 2016 Promise DevOps The Education Webinar Series
- 2. 2 Joan Wrabetz CTO Edan Evantal VP, Engineering Shashi Kiran CMO PANELISTS MODERATOR
- 4. Agenda • Introduction • DevOps Framework • Sandboxes and Quali CloudShell • The Quali DevOps Journey • Challenges and Learnings • The Road Ahead • Summary and Best Practices 4
- 5. 01 02 03 Venture-funded start-up focused on DevOps and BizOps Automation Delivers “Sandboxes” - Replicas of production environments Strong Innovation DNA – Trusted by customers worldwide About Quali 5 300+ customers – Cloud providers, Telcos, Enterprises – across FSI, Retail, Healthcare and Government ~115 employees in USA, Israel and Europe focused on serving customers worldwide300+
- 7. How We View the DevOps Lifecycle 7
- 8. Quali Cloud Sandboxes Building Blocks for DevOps and BizOps Automation Personalized replicas of production environments Reservation Self-Service with Sophisticated Modeling and Automation BI and Analytics Deploy Anywhere Set-up and tear down Environment GUI or API-driven Connectivity Applications and DataPhysical or Virtual Infrastructure Orchestrate DevOps and BizOps workflows Security “Full Stack” On-Prem or Hybrid CloudMulti-tenant
- 9. Quali Cloud Shell – Industry –Leading Sandbox Hybrid Infrastructure Enable Self-Service Environments with BI and Analytics Provide physical/virtual Infrastructure & Applications (Any DC/ Cloud) Mode & Orchestrate Full-Stack replicas of Production Environments
- 10. Benefits of Sandboxes to DevOps 10 Faster Release Cycles Lower TCO Reduced Ops Failures Automate Config. Setup and teardown Integrate with CI/CD Toolsets Decrease Risk Dev/Test in Production Replicas Expand scope Eg. Security Reduce Cost Efficient Resource Utilization
- 11. Quali Development Environment 50+ Engineers 15% Focused on DevOps Development Tools Source Control Build Virtualization / Cloud Test Dev/Test Sandbox ALM Collaboration
- 12. Stage 1 – Implement Agile SCRUM Implement Agile Quali DevOps Journey 7 1 2 3 4 5 6 FIX ISSUE • 2 weeks “sprints” create planning overhead • QA and test cycle = 50% of release bloat. • Definition of “done” • Shift to 4 wk. sprints to automate tests • Implemented Kanban with short weekly planning We Implemented Agile Scrum framework fully
- 13. Quali Lean Development Process Today Product Backlog Backlog grooming “Next“ stories Daily Scrum Meeting – Release Kickoff Weekly planning 4 weeks Sprint Review and Retrospective Potentially Shippable Product Increment
- 14. 14 Efficiency 2X productive • Agile Development • Kanban planning • Paired code reviews 1
- 15. Stage 2 – Increase % Automation Implement Agile Increase Automation Quali DevOps Journey 7 1 2 3 4 5 6 FIX ISSUE • Only 40% tests automated • Escape defects • Reduce UI testing • Implemented zero bug policy • Quality sprints – zero bug baseline release
- 16. Test Automation Composition UI Integration Unit 10’s 100’s 1000’s UI Integration Unit100’s 10’s 100’s 3 Years Ago Today
- 17. 17 • Agile Development • Kanban planning • Paired code reviews • Zero bug policy 2 Test Automation 85% Continuous testing 2
- 18. Stage 3 – Get Real Customer Input Implement Agile Increase Automation Customer Input Quali DevOps Journey 7 1 2 3 4 5 6 FIX ISSUE • INTERNAL sprint demos at end of 4 week releases. No customer input till EA too late to make changes • EXTERNAL sprint demos to field and delivery • CloudShell sandbox for realistic config., training and customer roadshows
- 19. Field Training and customer demos with CloudShell sandboxes 3 EA Feedback Months to Weeks
- 20. Stage 4 – Move to DevOps Implement Agile Increase Automation Customer Input Move to DevOps Quali DevOps Journey 7 1 2 3 4 5 6 FIX ISSUE • Obtain immediate Developer feedback. • Integrate CI/CD • Create CI Pipeline Shift left • Created CloudShell sandboxes mirroring customer environments added to automated test flow
- 21. 21 Continuous testing Developer Feedback Weeks to Minutes Continuous Integration Cloud Sandboxes 4
- 22. Stage 5 – Engage Customer and Partner Dev. Implement Agile Increase Automation Customer Input Move to DevOps 3rd Party Developers Quali DevOps Journey 7 1 2 3 4 5 6 FIX ISSUE • Get customers and partners to contribute to “shell” development • Collaborate - Distributed teams • Open Source “Shells” on GitHub • DevOps pipeline moved to GitHub for open participation • Developer version • Simpler documentation • API for 3rd party/ community
- 23. 23 Open Source 10X Innovation Velocity • Open Source Shells • Source Code in GitHub • Dev tools and docs • API driven 5
- 24. Stage 6 – Getting to GA Faster Implement Agile Increase Automation Customer Input Move to DevOps 3rd Party Developers GA Release Quality Quali DevOps Journey 7 1 2 3 4 5 6 FIX ISSUE • 3-month releases • No continuous deployment • Impacts new feature velocity • Live staging for EA customers • Interim builds – with features in development • CloudShell demos on AWS – experiment on early-stage builds
- 25. 25 Customer Sat. 30% Increase Customer Staging Sites Demos of latest build to EA customers speeds GA 6
- 26. Stage 7 – Increase Responsiveness Increase Responsiveness Implement Agile Increase Automation Customer Input Move to DevOps 3rd Party Developers GA Release Quality Quali DevOps Journey 7 1 2 3 4 5 6 FIX ISSUE • Continuous Deployment • New features and bugs cause disruption or get delayed by 3 months • Series of optimizations in progress
- 27. The Quali DevOps Journey … So Far Increase Responsiveness Implement Agile Increase Automation Customer Input Move to DevOps 3rd Party Developers GA Release Quality Quali DevOps Journey 7 1 2 3 4 5 6 2X Efficiency Increase 85% Test Automation EA Feedback: Months to Weeks Developer Feedback: Week to Minutes Work in Progress 30% Increase in Customer Satisfaction 10X Innovation Velocity
- 28. DevOps Progress Board ToDo InProgress Done (?) Eliminate release planning - only feature level planning Flexible CD for non-SaaS Deployments Deliver customer code non-disruptively on- premise or in the cloud Fixed scrum team allocation. No pre- planned backlogs 100% Continuous Integration DevOps Style Innovation Customer and Partner Engagement Feature velocity and Faster EA customer feedback Community scaling. Test Automation
- 29. DevOps Best Practices – It is a Journey! Focus on Agile Development1 Take an “Automation-First” Approach – CI/ CD2 Define end-goals. Leverage Cloud Sandboxes to Accelerate and De-risk the journey.3 Successful pioneers like Netflix, Etsy and Amazon took 5+ years to get CD (We are in year 3).
- 30. Q & A
- 31. Future Educational Webinars 1. Accelerate Hybrid Clouds with Sandboxes 2. Enhancing Security with Cyber Ranges 3. Cloud Sandboxes – Building blocks for DevOps Automation 4. Digitization – Key to Business Transformation
- 32. Quali Community
- 33. Blogswww.quali.com Social Media @Quali @Qualisystems 33 Quali engages with its customers, partners and developers in many ways. Stay in Touch