Deploy: Train, Driver and Tracks

Story of small DevOps team consisting of 4 on-call people and 2 newbies. How did we manage to go on-call and manage backlog. Talk is about the experiments we did that lead to be effective. Concepts such as deploy train, driver, navigator and tracks running real life DevOps.

Transcript

1. Deploy: Train, Driver and Tracks Garima Sharma Pivotal
2. About my team • PAAS Ops • R&D product teams • Since we run production env • Responsibility is to be first customer for feedback
3. About today’s talk • A few problems • Solutions
4. Problem 1 Too much to deploy • Long running deploys • 9 + 1 products • Frequent releases • 9 hours
5. Problem 1 Too much to deploy • Long running deploys • 9 + 1 products • Frequent releases • 9 hours
6. Solution Deploy Train • Train leaves early morning. • Boarding all the deploys it can take Photo by Mado El Khouly on Unsplash
7. Keep upgrading • Fear of upgrade is lost • It is hard but it is worth
8. Boarding the train Broadcast the deployments Relevant teams may join
9. Deployment Reports • For major deployment • Timezone
10. Train Schedule • Calendar • What was deployed and when • Relevant teams can subscribe to it
11. Problem 2 On call • Under-resourced team • Once a week per month
12. Changes cause issues • Upgrades • Config changes
13. Solution Train Driver • Carries context • Be on call • Deploys all week
14. Pairing • Driver always pairs with someone • Secondary on-call • Handover on every monday
15. Problem 3 Not just deployments • Explore • Root cause analysis • Interrupts • Development
16. Solution Tracks • Backlog management • Story: unit of work
17. Deploy Track • Version and new products that need to be deployed Photo by Irina Kostenich from Pexels
18. Interrupt Track • Explore • Interrupts like access • Root cause analysis Photo by Ales Krivec from Pexels
19. Dev Track • Development of tools to help Ops
20. Summary • Train • Driver • Tracks