The Story of Dev Ops Vahid Ashrafian Pichak

  • Slides: 64
Download presentation
The Story of Dev. Ops Vahid Ashrafian – Pichak Co.

The Story of Dev. Ops Vahid Ashrafian – Pichak Co.

Outline • Story of Pichak • Story of Dev. Ops • Your Story 2

Outline • Story of Pichak • Story of Dev. Ops • Your Story 2

Story of Pichak

Story of Pichak

Story of Pichak • Story of Pichak toward making software, faster, cheaper and good!

Story of Pichak • Story of Pichak toward making software, faster, cheaper and good! • Technical • Culture 4

5

5

Manuals 6

Manuals 6

Bash Scripts 7

Bash Scripts 7

Bash Scripts (Pro’s) • Easy to use • Easy to learn • Easy to

Bash Scripts (Pro’s) • Easy to use • Easy to learn • Easy to change • We can use source control (Git) 8

Bash Scripts (Con’s) • Low Speed • Unorganized 9

Bash Scripts (Con’s) • Low Speed • Unorganized 9

Juju? 10

Juju? 10

 • Provides a modeling language for users that abstracts the specifics of operating

• Provides a modeling language for users that abstracts the specifics of operating complex big software topologies 11

12

12

13

13

Containers 14

Containers 14

15

15

Monitoring Purchase Analytics Alert BL 16

Monitoring Purchase Analytics Alert BL 16

Continues Delivery & Deployment 17

Continues Delivery & Deployment 17

New Relic Servers 18

New Relic Servers 18

Griffin Reporter Cleaner Gatherer Runner Checker 19

Griffin Reporter Cleaner Gatherer Runner Checker 19

New Relic Insights 20

New Relic Insights 20

From Dev to Ops Amirs Vahid Soroush Hasan 21

From Dev to Ops Amirs Vahid Soroush Hasan 21

22

22

23

23

24

24

25

25

Interrupts! 26

Interrupts! 26

We Need to Change 27

We Need to Change 27

Spotify Culture 28

Spotify Culture 28

How we get things done at Pichak Dev. Ops Team • Basic Ideas of

How we get things done at Pichak Dev. Ops Team • Basic Ideas of Kanban • • Limit work in progress Prioritize completion of work in progress over new work Manage the flow of work through the system Visualize the workflow 29

Request Channels • Internal • External 30

Request Channels • Internal • External 30

Request Channels • Incidents • Tasks • Stories 31

Request Channels • Incidents • Tasks • Stories 31

Request Channels • Incidents • Tasks • Stories 32

Request Channels • Incidents • Tasks • Stories 32

33

33

Story of Dev. Ops

Story of Dev. Ops

So I wrote the code, now what? 35

So I wrote the code, now what? 35

Dev. Ops 36

Dev. Ops 36

Dev. Ops 37

Dev. Ops 37

Three Ways of Dev. Ops • The First Way: Accelerate Flow • The Second

Three Ways of Dev. Ops • The First Way: Accelerate Flow • The Second Way: Amplify Feedback Loops • The Third Way: Accelerate Learning 38

The First Way: Accelerate Flow • Continues Delivery & Deployment • Small and Frequent

The First Way: Accelerate Flow • Continues Delivery & Deployment • Small and Frequent Changes • Fast and Frequent Deployment 39

The First Way: Accelerate Flow • Pets vs Cattle 40

The First Way: Accelerate Flow • Pets vs Cattle 40

Microservices 41

Microservices 41

The First Way: Accelerate Flow • Two-Pizza Team • From Idea to Release 42

The First Way: Accelerate Flow • Two-Pizza Team • From Idea to Release 42

The Second Way: Amplify Feedback Loops • Goals: • Right to Left • Find

The Second Way: Amplify Feedback Loops • Goals: • Right to Left • Find and Fix Fast • Shorten and Amplify Feedback 43

The Second Way: Amplify Feedback Loops • Fast Feedback • • • Peer review

The Second Way: Amplify Feedback Loops • Fast Feedback • • • Peer review and pairing Contingency Design for failure Feedback loops Developer managed service 44

The Second Way: Amplify Feedback Loops • Etsy Operability Review Contingency Checklist: • •

The Second Way: Amplify Feedback Loops • Etsy Operability Review Contingency Checklist: • • When will it be launched Who is launching it Has it been in production yet Can it be dark, feature or percentage launched Is it new infrastructure Has an on off switch All parties available at launch time 45

The Second Way: Amplify Feedback Loops • Deploys – Upgrading Live Services • •

The Second Way: Amplify Feedback Loops • Deploys – Upgrading Live Services • • • Canary Rolling upgrades Blue green deploy Dark deploys Toggling feature A/B testing 46

The Second Way: Amplify Feedback Loops • Monitoring : Looking at Service Stack •

The Second Way: Amplify Feedback Loops • Monitoring : Looking at Service Stack • • • Business indicators Application indicators Infrastructure indicators User based indicators Deployment indicators 47

The Second Way: Amplify Feedback Loops • Monitoring : Google’s Four Golden Signals •

The Second Way: Amplify Feedback Loops • Monitoring : Google’s Four Golden Signals • • Latency Traffic Errors Saturation 48

The Second Way: Amplify Feedback Loops 49

The Second Way: Amplify Feedback Loops 49

The Second Way: Amplify Feedback Loops • Design for failure 50

The Second Way: Amplify Feedback Loops • Design for failure 50

The Second Way: Amplify Feedback Loops • Design for failure • The Netflix Simian

The Second Way: Amplify Feedback Loops • Design for failure • The Netflix Simian Army • • Chaos Monkey Latency Monkey Conformity Monkey Doctor Monkey Janitor Monkey Security Monkey 10 -18 Monkey Chaos Gorilla 51

The Second Way: Amplify Feedback Loops • Chat. Ops 52

The Second Way: Amplify Feedback Loops • Chat. Ops 52

The Third Way: Accelerate Learning • Learning Organizations • Communication • Blameless Culture 53

The Third Way: Accelerate Learning • Learning Organizations • Communication • Blameless Culture 53

The Third Way: Accelerate Learning • Learning Organizations • • Psychological safety Appreciation of

The Third Way: Accelerate Learning • Learning Organizations • • Psychological safety Appreciation of difference Openness to new ideas Time for reflection Systematic knowledge sharing Education and experiment Reinforced learning 54

The Third Way: Accelerate Learning • Learning Organizations • Communication 55

The Third Way: Accelerate Learning • Learning Organizations • Communication 55

The Third Way: Accelerate Learning • Blameless Culture • A blameless culture believes that

The Third Way: Accelerate Learning • Blameless Culture • A blameless culture believes that systems are NOT inherently safe and humans do the best they can to keep them running. 56

High-performing organizations 57

High-performing organizations 57

High-performing organizations • Deploy 200 times • 2, 555 times faster lead times •

High-performing organizations • Deploy 200 times • 2, 555 times faster lead times • recover 24 times faster • three times lower change failure rates 58

Your Story

Your Story

60

60

61

61

We Need More Stories! 62

We Need More Stories! 62

Thank You! vahid. ashrafian@gmail. com @vahid_ashrafian 63

Thank You! vahid. ashrafian@gmail. com @vahid_ashrafian 63

Recommended Resources • Introduction to Dev. Ops: Transforming and Improving Operations – edx. org

Recommended Resources • Introduction to Dev. Ops: Transforming and Improving Operations – edx. org – The Linux Foundation • Spotify Engineering Culture • https: //www. youtube. com/watch? v=Mpsn 3 Wa. I_4 k&list=PLC 3 mk_XNnm. VS 7 HG_nh. Nr 3 I 1 VQ-2 e. L 2 Xg. B • Transforming Software Development – Amazon Web Services • https: //www. youtube. com/watch? v=YCrhemss. Yu. I • My Personal Dev. Ops Playlist on Youtube • https: //www. youtube. com/playlist? list=PLOw-K 6 Ho. PAvx. U 39 z. L 4 ki 4 Ym. BRr 5 ih. SKV 64