Deploy: Train, Driver and Tracks

Slide 1

Slide 1 text

Deploy: Train, Driver and Tracks Garima Sharma Pivotal

Slide 2

Slide 2 text

About my team ● PAAS Ops ● R&D product teams ● Since we run production env ● Responsibility is to be first customer for feedback

Slide 3

Slide 3 text

About today’s talk ● A few problems ● Solutions

Slide 4

Slide 4 text

Problem 1 Too much to deploy ● Long running deploys ● 9 + 1 products ● Frequent releases ● 9 hours

Slide 5

Slide 5 text

Problem 1 Too much to deploy ● Long running deploys ● 9 + 1 products ● Frequent releases ● 9 hours

Slide 6

Slide 6 text

Solution Deploy Train ● Train leaves early morning. ● Boarding all the deploys it can take Photo by Mado El Khouly on Unsplash

Slide 7

Slide 7 text

Keep upgrading ● Fear of upgrade is lost ● It is hard but it is worth

Slide 8

Slide 8 text

Boarding the train Broadcast the deployments Relevant teams may join

Slide 9

Slide 9 text

Deployment Reports ● For major deployment ● Timezone

Slide 10

Slide 10 text

Train Schedule ● Calendar ● What was deployed and when ● Relevant teams can subscribe to it

Slide 11

Slide 11 text

Problem 2 On call ● Under-resourced team ● Once a week per month

Slide 12

Slide 12 text

Changes cause issues ● Upgrades ● Config changes

Slide 13

Slide 13 text

Solution Train Driver ● Carries context ● Be on call ● Deploys all week

Slide 14

Slide 14 text

Pairing ● Driver always pairs with someone ● Secondary on-call ● Handover on every monday

Slide 15

Slide 15 text

Problem 3 Not just deployments ● Explore ● Root cause analysis ● Interrupts ● Development

Slide 16

Slide 16 text

Solution Tracks ● Backlog management ● Story: unit of work

Slide 17

Slide 17 text

Deploy Track ● Version and new products that need to be deployed Photo by Irina Kostenich from Pexels

Slide 18

Slide 18 text

Interrupt Track ● Explore ● Interrupts like access ● Root cause analysis Photo by Ales Krivec from Pexels