The Cloud: Releasing Software into Controlled Chaos
•Download as PPTX, PDF•
1 like•478 views
The document discusses release management for software deployed to the cloud. It describes a typical enterprise release process with 6 steps: 1) multi-release scheduling, 2) pre-release communications, 3) deployment workflow planning, 4) release deployment, 5) release communications, and 6) post-release monitoring. It also discusses using continuous integration, continuous delivery, and monitoring to provide an "always-on" cloud service.
Report
Share
The Cloud: Releasing Software into Controlled Chaos
- 1. 2015 The Cloud: Releasing Software into Controlled Chaos Wednesday October 14, 2015 #GHC15 2015
- 2. 2015 DIRECTOR Release Management Panelists PRINCIPAL Release Management ENGINEER Release Engineering ENGINEER DevOps Engineer Kate Gentry Eugene Boguslavsky Nicole Santiago Geraldine Gray
- 3. 20152015 Enterprise Release Process 1 Multi-Release Scheduling Release Manager does centralized scheduling 2 Pre-Release Communications Customer Communication Specialist 3 Deployment Workflow Plan All team members input into the plan 4 Release Deployment Mostly automated; Errors/Exceptions need human intervention 5 Release Communications Automated Messages to customers providing release status information 6 Post-Release Monitoring Automated; Any concerning metrics are investigated by Service Owner
- 4. 2015 More than deploying a software package Providing “Always-On” Service
- 5. 2015 Continuous Integration Developers Check in Package +tests Continuous Integration Test Environment Robots Handle Testers, Release Mgrs.
- 6. 2015 Continuous Integration Continuous Delivery Monitoring Monitoring Monitoring If bad Ifbad RollbackReject Production Acceptance Test TestDevelopment Intregrated Dev. Env. Build & Integration Package & Repository Test Automation
- 7. 2015 Got Feedback? Rate and review the session on our mobile app Download at http://ddut.ch/ghc15 or search GHC 2015 in the app store