Building the Bridge to Enterprise DevOps Success
Download as PPTX, PDF0 likes283 views
The document discusses the evolution of DevOps practices in enterprises, outlining various stages of software release processes from minimal CI and feedback to integrated continuous delivery at enterprise scale. It emphasizes the need for tailored solutions based on unique enterprise characteristics, such as team distribution and technology stacks. Key focuses at advanced stages include automation, collaboration, security, and real-time feedback to support continuous improvement.
Building the Bridge to Enterprise DevOps Success
- 1. Building the Bridge to Enterprise DevOps Success Tim Buntel VP of Products
- 2. 2
- 3. 3
- 4. 4
- 5. 5
- 6. 6
- 7. 7
- 8. 8
- 9. 9
- 10. 10
- 11. 11
- 12. 12
- 13. 13
- 14. 14
- 15. 15 Scale Stage
- 16. 16 • Build on the previous generation • Retain key characteristics
- 17. 17
- 18. 18 What does this have to do with DevOps?
- 19. 19 Scale StageNo DevOps Dev + Ops Needs Enterprise Scale Intelligence & Business
- 20. 20 • Build on the previous • Retaining key characteristics Dev + Ops Needs Enterprise Scale Intelligence & Business Strong Base Many lanes Monitoring
- 21. 21 Not every crossing is the same! • Geography • Weather conditions • Traffic load • Length Every bridge is different… • Size • Team distribution • Technology stack • Delivery method And so are enterprises!
- 22. 22 Scale StageNo DevOps Dev + Ops Needs Enterprise Scale Intelligence & Business
- 23. 23 Software Release Ferry What does it look like? • Waterfall • No CI • Infrequent releases • Minimal feedback Focus on • Call us!
- 24. 24 Software Release Bridge What does it look like? • Some CI • Agile at team level • team level tools, but not standard across the enterprise • homogenous stack Focus on • Automation • Repeatability • Speed
- 25. 25
- 26. 26
- 27. 27
- 28. 28 Support Across Platforms Cloud and Container Environments Classic Enterprise Environments
- 30. 30 Software Release Highway Bridge What does it look like? • CD in place • Heterogeneous stack • Many teams • Complex Integrations • Compliance • Security & Risk Focus on • Organizational Scale • Dual-mode • Collaboration • Integrations
- 31. 31
- 32. 32
- 34. 34
- 35. 35
- 36. Jason Lenny Director of Technical Product Management 36
- 37. 37 Software Release Smart Bridge What does it look like? • Enterprise-wide CD • Self-service • Continual Improvement Focus • Real-time feedback • Fully integrated security Focus on • Goal Driven • Visibility • Prediction • Longitudinal analysis
- 38. 38
- 39. 39
- 40. TJ Randall VP of Customer Success 40
- 42. 42 Scale StageNo DevOps Dev + Ops Needs Enterprise Scale Intelligence & Business
- 43. 43 What’s next?
- 44. 44
- 45. Thank you! 45
Editor's Notes
- #4: http://www.loc.gov/pictures/collection/fsa/item/fsa1998012456/PP/
- #5: Not always the most stable approach!! By Photographer: G. Heurlin - http://libris.kb.se/bib/1323571, Public Domain, https://commons.wikimedia.org/w/index.php?curid=20515064
- #10: Ponte de Prozelo Northern Portugal - middle of the 14th century
- #11: The Iron Bridge over the River Severn in the Ironbridge Gorge, Shropshire, England, UK. The bridge was built in 1779 and was the first to be fabricated out of cast iron.
- #12: Highway bridge over Murchison River in Western Australia
- #14: early morning on the Bay Bridge, at the exit of a tunnel. It is the main connection between the cities of Oakland and San Francisco, CA
- #15: Goal Driven – more traffic, more safety, etc. Oresund Bridge between Denmark and Sweden 5 miles long continuous monitoring system, capable of measuring both static and dynamic quantities such as temperatures, wind characteristics, air humidity, strains, and acceleration Multiple parts – cars, trains – bridge and tunnel https://en.wikipedia.org/wiki/%C3%98resund_Bridge
- #19: Trying to bring idea/value to customers – bridging a gap
- #23: Adding value at each stage – AND continually adding just like maintenance to the bridge
- #24: Don’t despair! Yoga – blessed with the gift of tightness. Nowhere to go but UP
- #25: Show – automated vs manual report XLD model Code-centric
- #26: Report highlights opportunity to automate Value stream map example – Under each phase of a release, you can see its duration and the proportion of the total duration that the phase took.
- #27: Model supports repeatability Wouldn’t tear down bridge after walking across each time!
- #28: AS-Code allows developers to use a standard process for releasing the appliction – and they define it in a format that suits them. but still have the benefits of reporting, etc. for less technical folks. Coming soon for XLD
- #29: Private Cloud Deployment Automation with XebiaLabs and OpenShift Tom Larrow, KeyBank
- #30: How can organizations decide what to automate? How does being model-driven benefit DevOps teams? What do you see as key platform challenges for companies today? Tell us about your session this afternoon.
- #32: Folders help you scale – by geography, project, etc. Microservices!
- #33: TAGS – good for related but independent releases
- #34: Email, due soon notifications, Slack and Hipchat, Watchers - all help to coordinate efforts when teams are large and distributed.
- #35: The XL Platform includes features for high availability and scalability, so whether you have one server or dozens, you know you can count on XL for your mission-critical software development needs. In this afternoon’s session, you can hear about what’s coming in Both XLR and XLD for this, too. XLR - How do release/portfolio managers with dozens or hundreds of microservices all being deployed through XLR by individual teams engage with and understand what's going on in their delivery landscape? If different teams are using different tech stacks, how do I ensure they are following a consistent governance process? Is there a feature-oriented delivery view possible within XLR that ties releases together based on delivery certain business value?
- #36: Satellites are stand-alone processes that are located in your infrastructure, close to your hosts. XL Deploy orchestrates your deployments by driving the satellites and uploading files (artifacts) and commands to them. XL Deploy satellites can be used to: Deploy an application in a cluster that is located around the world Deploy to production servers in a dedicated subnet that XL Deploy would normally not be allowed access for security reasons Deploy to an infrastructure that contains both Unix and Microsoft Windows hosts, with easier authentication between them
- #37: What are some of the ways you’ve seen organizations deal with scale – geographic, by team, etc.? How do those teams maximize communication? I often hear about organizations needing to balance freedom for developers with control (for compliance, etc.) – have you seen this? Tell us a bit about your session this afternoon…
- #39: Risk insight
- #40: Persona based insight – compliance & audit
- #41: You’re responsible for customer success. Maybe What are some of the key things that define a successful DevOps initiative? How do successful organizations share information about their DevOps processes internally? What about continuous improvement? Is this a core part of successful enterprises? Tell us a bit about your session this afternoon.
- #42: Continual improvement, Goal-driven Link: http://ec2-13-58-232-233.us-east-2.compute.amazonaws.com/ User: admin PW: 2fD1Bwvb7oAG
- #43: Hear from your peers this afternoon – ABN Amro, Freedom Mortgage, Digital Globe Insight from Sunil – DevOps by the Numbers
- #45: 7.0 Launch TODAY! Top items: make it easier for you to Communications Risk Dual-mode devOps with code-centric New UI Cloud