How to Uplevel Your Pipeline with Release Orchestration and Deployment Automation
1 like343 views
The document discusses the transformation of software delivery through Agile and DevOps practices, emphasizing the need for integrated product teams and value stream management to enhance efficiency. It outlines the shift from monolithic to microservices architecture and the requirements for continuous deployment and application release automation. Additionally, it highlights tools and strategies for managing releases, ensuring compliance, and improving collaboration across teams in a rapidly evolving technological landscape.
How to Uplevel Your Pipeline with Release Orchestration and Deployment Automation
- 1. Jeff Keyes Director of Product Marketing [email protected] Tracy Ragan CEO [email protected]
- 2. For Agile + DevOps, make integrated product teams the pulsing heart of your organization Source: Organize Your App-Dev Teams With Agile And DevOps | © 2018 FORRESTER Value stream product teams Shared service DevOps CoE ArchitectureSecurityCX/UX Federated testing CoE PMO Software platform services teams Operational platform services CD dojos • Common component services • Common architecture patterns Project teams • Single release • Shared resources • Finite scope Shared services teams • Automated self- service • Pool of resources x projects and products • Zero wait time or automated Development Operations
- 3. PAGE 3 Delivery Model Goal Sprint Sprint Sprint Sprint Sprint 100% Automated Regression / Sanity / Gated Commits RLS RLS RLS RLS Automated Security Scans Hardening / UAT Performance / Offline Visual Content / UI / API Testing
- 4. PAGE 4 The J-Curve of Transformation Digital Transformation is Hard “We’ve been doing DevOps for 18 months … and have yet to release anything.” - PLUTORA PROSPECT
- 5. PAGE 5 Modern Pipeline Reality Planning & Coordination Governance & DeploymentReadiness & Management
- 6. PAGE 6 From Monolithic to Microservices And Our World is Changing Traditional Monolithic Releases Modern Architecture Services
- 7. PAGE 7 From Siloed to Connected Legacy to Modern Architecture Separated by Walls Joined and Collaborative
- 8. PAGE 8 But worth it The Modern architecture is driven by high performing software teams who are building AI and ML applications requiring high availability and redundancy. Software updates will occur continuously. Our old practices will need to be replaced. Only Getting More Complex Automation and tracking will be a requirement, not a luxury. Scripts and excel spreadsheets will not meet the demand. Value Stream Management and Release Automation designed for these teams will be critical. 1 2 3 4 5
- 9. PAGE 9 I’m not 100% automated to delivery ….And what about me? I need to intermix Waterfall with Agile/DevOps pipelines into a single release I don’t have a standardized process – each release follows a different path. I have heavy governance & audit requirements d Deployment Plans Runbooks and Deployment Plans
- 10. Approverolloutplans Development Testing Production Monitoring Diagnostics Incidents Release Policy & Strategy Release Planning Rollout Planning Release Configuration Release Acceptance Release Communication Define release process, policies Establish release management tools Identify RASCI Prepare release calendar Assign projects to releases Identify dependencies Determine rollout policy Review roll out plans Identify, mitigate risks Prepare release bundles Verify release criteria Verify process, policy approvals Communicate release updates Ticketing and Change Management Implement Releases Verify Releases Transition Releases Rollout release to production Verify release in production Monitor key metrics Rollback releases Transition to operations and prod support UT SIT UAT Prod Identifyprojectstakeholders PRD,ERDreviews Bookprojectonarelease Resolveprojectconflicts Reviewcapacity,code Createproductionbuilds Runregression Releasecriteriahasbeenmet Verifyapprovals Prodrollout Releasedone QDPRB ITSM R R O B DPRB PRB QDPR O QR QPRB B R RMO PMO Dev QA/E OpsBusiness QDPRB O Speaking of Governance…
- 11. PAGE 11 Delivery Model Reality Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Week 11 Week 12 Week 13 Week 14 CI/CD Builds, Test, Scanning Security GoLive Agile Sprints Regression 100% of Team Stays on Release Offline Hardening Performance UAT QuietPeriod
- 12. PAGE 12 How to get to Continuous Deployment?
- 13. PAGE 13 Release Orchestration & Release Automation
- 14. PAGE 14 Complete Solution Application Release Orchestration (ARO) serves to compress the tasks completed in traditional waterfall practices into an agile cadence improving the speed, governance and visibility of the software lifecycle. These tools serve the enterprise and support multi- generational teams from legacy through modern architecture. ARO and ARA Defined Application Release Automation (ARA) tools perform the packaging, versioning and deployment of application related artifacts with a large number of rapid, small releases across physical servers, clouds, and containers. They replace scripted deployment practices with a model driven design and coordinate releases across teams. ARA tools track application configurations and the inventory of an endpoint. ARA tools improve the speed and quality of software updates and serve as the continuous deployment solution in pipelines.
- 15. Release Orchestration PROJECT TEAM PRODUCT TEAM PROJECT TEAM Activities Automation Coordination Resources Communication Activities Automation Coordination Resources Communication ENTERPRISE RELEASE PLANS UAT StagingSIT Prod
- 16. PAGE 16 The Fundamentals Complete Solution Value Stream Management with Release Orchestration Release Orchestration & Management Tracking a software change from check-in through deploy. Test Environment Management Centralize environment schedules, resolve conflicts and track dependencies. Deployment Management Manage approvals, report on deployment times, create audit trail. Release Analytics Aggregate release, quality and deployment data for continuous improvement.
- 17. PAGE 17 The Benefits Complete Solution 1. Intermixing Waterfall with Agile/DevOps pipelines 2. Templatize the process. Break it down into sub- releases. 3. Incorporate manual and automation 4. Phases and Gates
- 18. PAGE 18 The Fundamentals Complete Solution Release Automation and Continuous Deployment Catalog & Publish Centralize and Share components for improved collaboration and reuse. Package Define an application package with binaries, database updates and infrastructure. Version Version application releases for fast rollback, roll forward or version jumping. Deploy Update physical servers, cloud images, or Kubernetes clusters and track inventory history.
- 19. PAGE 19 Application Release Automation Catalog, Publish, Version & Deploy Catalog using a Domain Driven Design Component to Application Mapping and Config. Versioning Centralized Publishing for Sharing Deploys a large number of rapid, small releases safely
- 20. Login Master Front End Master Rear Wheel Yellow Front Wheel Yellow Frame Black Frame Yellow Seat Black Seat Yellow ‘Bumble Bee’ Application Version 1 ‘Yellow Jacket’ Application Version 2 DockerImage=Microservice=DHComponentVersion Application Versions Logical View of the Monolithic DeployHub Service Catalog DeployHub Mapping & Service Versioning Biking Game
- 21. PAGE 21 The Benefits Complete Solution 1. Continuous Process Improvement and insight. 2. Central control point for software releases 3. Audit tracking and inventory history 4. Automation and control from check-out to endpoint update
- 22. PAGE 22 Well, sort of…. Continuous Delivery is a ‘software engineering approach’ not a tool. According to the Continuous Delivery Foundation: Isn’t all of this just Continuous Delivery? “Continuous Delivery is a software engineering approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time. The rise of microservices, cloud native architectures has caused a corollary rise in continuous delivery practices.”
- 23. Plutora is the most complete Value Stream Management platform FOUNDED IN 2011
- 24. PAGE 24 “I see Plutora as the glue that holds the delivery process together, communicating with project managers, development teams, test teams, infrastructure teams, and stakeholders.” DANNY TOBIAS, PROJECT & PORTFOLIO ENVIRONMENT MANAGER CASE STUDY 25% INCREASE IN ENVIRONMENT USAGE 3.5X INCREASE IN RELEASE THROUGHPUT 30 HOURS SAVED AND REINVESTED EACH WEEK
- 25. PAGE 25 Ortelius.io Open Source Project Continuous Deployment with Microservices Configuration Mapping
- 26. PAGE 26 “Using DeployHub for continuous deployment, we reduced software delivery times from 7 hours to 5 minutes..” Chris Wale, Canadian Government CASE STUDY
- 27. Jeff Keyes Director of Product Marketing [email protected] Tracy Ragan CEO [email protected] Q & A
- 28. PAGE 28 Orchestrate scripts in a workflow with no high level tracking or coordination The Good • No new technology introduction, open source CD tools • Use existing scripts for build and release The Bad • Existing Scripts were born in waterfall • Process is monolithic and cannot support rapid, small releases • Production uses different tools • No database updates, or configuration versioning • Can’t adapt across the life cycle, must update the script for every ⁃ Release, environment, version • Not transparent – log information is all you get. The Ugly • Business logic and audit is incorporated into code requiring dev teams to constantly negotiate and update it. • The process is based upon scripts keeping the Traditional Continuous Delivery Orchestration Tools
- 29. PAGE 29 Interconnected Delivery Phases & Gates ENTERPRISE RELEASE PLANS UAT StagingSIT • Quality • Governance • Security / Compliance