Code to Cloud: Three Trends for Faster, Safer Continuous Delivery
1 like742 views
The document outlines three trends in continuous delivery: viewing continuous delivery as a relay race, transforming monitoring into actionable insights, and prioritizing developer experience. It emphasizes the importance of establishing scalable frameworks for seamless app deployment and operation, along with fostering a community culture for efficient collaboration. Case studies from various companies illustrate the successful implementation of these trends, enhancing developer efficiency and accelerating feature delivery.
![What We’ll Cover
● Setting the Context
● [1] Continuous delivery: the relay race
○ Demo
● [2] Turning monitoring into action
● [3] Developer experience at the heart
● Summary
● Q&A](https://image.slidesharecdn.com/codetocloudwebinar-191031160233/85/Code-to-Cloud-Three-Trends-for-Faster-Safer-Continuous-Delivery-2-320.jpg)
Code to Cloud: Three Trends for Faster, Safer Continuous Delivery
- 1. © 2019 PIVOTAL SOFTWARE, INC. All Rights Reserved. Code to Cloud: Three Trends for Faster, Safer Continuous Delivery October 31, 2019 Olga Kundzich, Pivotal, Senior Product Manager Spinnaker @olgakundzich Tony Vetter, Pivotal, Technical Product Marketing Manager @anthonyjvetter Patricia Johnson, Pivotal, Product Marketing Manager CI/CD @PJ4DevOps
- 2. What We’ll Cover ● Setting the Context ● [1] Continuous delivery: the relay race ○ Demo ● [2] Turning monitoring into action ● [3] Developer experience at the heart ● Summary ● Q&A
- 3. Is this like your path from commit to production? https://www.youtube.com/watch?v=ZQGmtuG0Nx8
- 4. Establishing a repeatable, traceable, scalable framework that ● Enables fast, iterative development and testing ● Deploys apps seamlessly, securely, and safely ● Actively operates apps in production Continuous Delivery of Modern Apps Monitoring Managing Resiliency Develop Security Compliance Validation Pivotal Platform Deploy Operate Planning Test-Driven Dev CI/Build Development Users
- 5. Code to Cloud Trends Trend 1: CD as a relay race Trend 2: Turn monitoring into action Trend 3: Developers at the heart
- 6. Continuous Delivery: The Relay Race Trend #1
- 7. CI and CD Are Two Different, Related Processes Source Code Repository CD Pipeline Development Production CI Pipeline Artifact Repository CI CD
- 8. Source code system of record Artifact system of record Runtime app system of record CI/Build automation Delivery automation Code to Cloud: Managing App Release and Operation Systems of Record Automation
- 9. Git Repository Spinnaker CD Dev Cluster Prod Cluster DEMO: Software Automated Path to Production Harbor ity Security Validation MySQL Concourse CI Spring Boot Build Testing Docker Image Monitor for branch commit Monitor for master commit Upload to container registry Monitor for image and deploy to Dev or Production Pivotal Platform Promote to master branch 2 1 3 4 5 6Commit code Concourse CI Spring Boot Build Testing Docker Image
- 10. DEMO
- 11. Turning Monitoring into Action Trend #2
- 12. Spinnaker: OSS Multi-Cloud Delivery Platform Spinnaker Community “...the passionate open source community dedicated to making deployment pain go away.” https://www.spinnaker.io/publications/ebook/
- 13. Application Centric Control Plane = Turn monitoring into action Deploy safely with speed
- 14. Leveraging the Inventory Automated Canary Analysis Corrective Actions Chaos Engineering Scanning for Security Vulnerabilities Artifact Traceability Built-in corrective actions
- 15. Automated Canary Analysis Ensures your applications meet your SLAs https://medium.com/netflix-techblog/automated-canary-analysis-at-netflix-with-kayenta-3260bc7acc69
- 18. Canary Best Practices ■ Run canaries long enough to gather enough data points ■ Fine-tune the metrics you choose to reflect key service health indicators ■ Include business metrics such as pirate metrics
- 19. Developer Experience at the Heart Trend #3
- 20. “Server delivery for a project was on a 4-6 week basis...there was a lot of error involved…. It was a poor experience for the development community…” —Kevin Ponds, Director of Site Reliability Engineer and Customer Satisfaction, AutoZone “The driving goal of our work has been to enable our DevOps teams to focus on delivering value and not on tasks below the value line.” —Nick Penston, Director of Engineering, Fidelity Investments OLD DAYS NEW WAYS
- 21. Strategies for Removing Friction for Developers ● Onboarding ● Backlog for the platform ● Platform automation ● Compliance ● Security ● Logging ● Feedback loops ● Education ● Cross-functional work Platform as a Product Pipelines with Guardrails Community Culture
- 22. “We went from having a couple of monoliths to easily 65-70 microservices in our organization…. And we needed a platform, and we really needed a platform team. There was no way we were going to continue doing what we were doing.” —Bryan Kelly, Principal Software Engineer, Cerner Corporation Platform as a Product Is Born
- 23. A Good Definition
- 24. Elements of Platform as a Product Automated On-boarding Platform Automation Product Managed “When you go look at our backlog today, it’s not full of chores on how to make our jobs easier. ...it’s full of features to make developers, architects, InfoSec’s lives easier. And I always drag those to the top of the list because I want to get value to the customers.” —Daniel Church, Product Manager PlatformOps & Customer Satisfaction, AutoZone
- 25. Platform as a Product Results —Kevin Ponds, Director of Site Reliability Engineer and Customer Satisfaction, Autozone “Developer efficiency and job satisfaction has improved and we could release more features more quickly with fewer headaches.”
- 26. ...it’s about creating a cohesive pattern that our engineers can follow that will expedite and fast track them from a concept to cash for our clients. And we refer to that as instant change authorization. If you follow all the right patterns, if you reach the right quality thresholds, if you meet our cyber bars, then we allow you to do full continuous delivery with Spinnaker. And we’ve got about 200 apps going through that cycle. —Stephen Flaherty, Head of Enterprise Architecture, Core Engineering & Public Cloud at JPMorgan Chase Pipelines with Guardrails
- 27. Standardizing the Delivery Toolchain “...we have 30,000 developers. So it’s very important that we’re very efficient in the tools and technologies and practices that we embed within our technology organization.” —Richard Francois, VP, JPMorgan Chase & Co.
- 28. Pipelines with Different Levels of Opinions “We want to build the security and the safety into the automation so developers don’t have to worry about it.” —Fidelity Investments More Opinionated for Less Mature Teams Less Opinionated for More Mature Teams
- 29. “We’re constantly building the knowledge of everybody in the organization.” —Gerard McMahon, VP Architecture, Fidelity Investments Community Culture
- 30. Collaboration Techniques “You need trust if you want high-performance teams.” —Fidelity Investments
- 31. Cloud Parties “We take our cyber colleagues, identity access management, and the AD teams and sit them all in a room with us and have a week-long hackathon.” —Stephen Flaherty, Head of Enterprise Architecture, Core Engineering & Public Cloud at JPMorgan Chase
- 32. Enterprise Case Studies ● AutoZone: AutoZone and the Road to Cloud-Native ● Cerner: The Continuous Platform ● Dick’s Sporting Goods: PKS Automation Station...All Aboard: Enabling Team Access to PKS with a Concourse Pipeline ● Fidelity Investments: Accelerating the Developer’s Road to the Cloud at Enterprise Scale ● Fiserv: SDLC for Pivotal Platform, Powered by Spring Initializr, Concourse, and Spinnaker ● JPMorgan Chase: ○ SpringOne Platform Day 3 Keynote ○ The Reality of Managing Microservice Deployments at Scale: You Need a Spinnaker ● Royal Bank of Canada: Are You SREious? An Approach to Site Reliability Engineering ● Platform as a Product: How to Delight Your Developers and Deliver Value for Your Customers
- 34. Code to Cloud Trends Summary Trend 1: CD as a relay race Trend 2: Turn monitoring into action Trend 3: Developers at the heart
- 35. Supported Helm Chart Deployment Pivotal Concourse v5.5.3 Validated, Supported Spinnaker - Beta Release Pivotal Continuous Delivery with Spinnaker™ OSS Community Commercial Release www.pivotal.io/concourse www.pivotal.io/spinnaker Recent App CI/CD News from Pivotal
- 36. Q&A
- 37. Pivotal’s Partnership Approach to Software Is Holistic Methodology Learn the necessary practices to build modern software Tools Build with products focused on developer productivity Platform Run every app, on every cloud, on a unified platform Cloud-native software Pivotal Labs and Services Pivotal Platform Best-in-class products Your teams Pivotal Culture Continually improve and deliver customer success
- 38. Build Service ● Intelligent approach to OCI-compatible image updates ● Automated updates ensure image always reflects newest version of reality ● Make sure apps use secure, compliant dependencies Concourse CI Spinnaker CD ● Containerized build and test—clean, consistent environment every time ● Simple, declarative pipeline models that are reusable and can be tracked in source control ● Fast feedback and team alignment with shared pipeline visuals ● Inventory of deployed applications across enterprise ● Sophisticated deployment scenarios like canary, blue/green deploys ● Record of all pipeline activities for compliance and audit ● Deploy to multiple Kubernetes clusters on demand ● Includes Harbor, an enterprise-class container registry with security validation ● Out-of-the-box network management and security Container Service DevOps Toolchain from Pivotal