Slide 1

Slide 1 text

The wide range of DevOps

Slide 2

Slide 2 text

Mitchell Hashimoto @mitchellh

Slide 3

Slide 3 text

Vagrant

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

No content

Slide 6

Slide 6 text

— DevOps

Slide 7

Slide 7 text

— Memes W ARNING!

Slide 8

Slide 8 text

I got into DevOps by accident. (But I love it!)

Slide 9

Slide 9 text

Confession: I’m new to this.

Slide 10

Slide 10 text

No experience with Rack & Stack.

Slide 11

Slide 11 text

I am the Cloud generation.

Slide 12

Slide 12 text

More specifically... I am the bridge.

Slide 13

Slide 13 text

I practice DevOps!

Slide 14

Slide 14 text

But my devs don’t do ops...

Slide 15

Slide 15 text

Is this still DevOps?

Slide 16

Slide 16 text

DevOps: A range.

Slide 17

Slide 17 text

Based on my experience transitioning to DevOps...

Slide 18

Slide 18 text

Vagrant

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

2 people to 200 people

Slide 21

Slide 21 text

Ops is a black box. Devs do all ops

Slide 22

Slide 22 text

Ops is a black box. Devs do all ops The Range Requires More than Ops

Slide 23

Slide 23 text

Ops is a black box. Devs do all ops Road to... increased stability. Road to... faster feedback. Road to... cheaper iteration.

Slide 24

Slide 24 text

Metrics, metrics, everywhere.

Slide 25

Slide 25 text

What does my code do?

Slide 26

Slide 26 text

What is the system -wide effect of this change?

Slide 27

Slide 27 text

Why is my service slow?

Slide 28

Slide 28 text

Ops knows.

Slide 29

Slide 29 text

No content

Slide 30

Slide 30 text

No content

Slide 31

Slide 31 text

No content

Slide 32

Slide 32 text

Developers should know, too.

Slide 33

Slide 33 text

No content

Slide 34

Slide 34 text

It should be easy

Slide 35

Slide 35 text

Remember, we’re right here now.

Slide 36

Slide 36 text

How do we make this easy?

Slide 37

Slide 37 text

No content

Slide 38

Slide 38 text

Graphite + Statsite = —

Slide 39

Slide 39 text

That was easy.

Slide 40

Slide 40 text

No content

Slide 41

Slide 41 text

No content

Slide 42

Slide 42 text

Insight into... performance Insight into... system-wide effect Insight into... ops!

Slide 43

Slide 43 text

Document your infrastructure

Slide 44

Slide 44 text

No content

Slide 45

Slide 45 text

“Its easy!”

Slide 46

Slide 46 text

“Its easy!” Your request comes in. IPTables lets it pass through because its global traffic on a load balancer. It then hits an SSL terminator which proxies the request back to a level 7 load balancer, which round robins the request to an app server. If its a static file request its served directly off disk otherwise it goes to the actual application process. Now your code is executed. Got it? Ready to learn about service orchestration, response caching, and how the site stays running?

Slide 47

Slide 47 text

No content

Slide 48

Slide 48 text

1. Document your ops.

Slide 49

Slide 49 text

No content

Slide 50

Slide 50 text

Topics... Deploy process Lifecycle of a request How do new servers come online? Coding guidelines for Cookbooks Failures and resolutions (automated or not) Tools guides (htop, lsof, ps, netcat, strace) Development VM internals (Vagrant)

Slide 51

Slide 51 text

Remove the Black Box

Slide 52

Slide 52 text

2. Company Tech Talks

Slide 53

Slide 53 text

Bi-weekly. Short (15 minutes). Deep dives.

Slide 54

Slide 54 text

Topics... HAProxy Vagrant Configuration management philosophy On-Call Practices Infrastructure testing and verification

Slide 55

Slide 55 text

Deeper understanding of technologies in use

Slide 56

Slide 56 text

No content

Slide 57

Slide 57 text

Insight into... architecture Insight into... scalability Insight into... how code is executed Insight into... ops!

Slide 58

Slide 58 text

Production-mirror Dev Environments

Slide 59

Slide 59 text

Vagrant

Slide 60

Slide 60 text

Duplicate efforts for production vs. development?

Slide 61

Slide 61 text

Use production ops for development

Slide 62

Slide 62 text

Extra effort involved. Big gain.

Slide 63

Slide 63 text

Small effect on developer workflow.

Slide 64

Slide 64 text

No content

Slide 65

Slide 65 text

Insight into... provisioning Insight into... server evolution Insight into... architecture Insight into... ops!

Slide 66

Slide 66 text

DevOps Office Hours

Slide 67

Slide 67 text

Ops can be scary to those new to it.

Slide 68

Slide 68 text

What was that?!

Slide 69

Slide 69 text

Luckily, we’re friendly.

Slide 70

Slide 70 text

Ops office hours. Dev office hours.

Slide 71

Slide 71 text

A comfortable environment to ask and learn anything.

Slide 72

Slide 72 text

No content

Slide 73

Slide 73 text

Office hour activities... Architecture explanation Fast Chef tutorial Help with cookbook bugs Teaching how current cookbooks work Code review!

Slide 74

Slide 74 text

My Office Hours: Mondays 3 - 5 PM

Slide 75

Slide 75 text

No content

Slide 76

Slide 76 text

Insight into... anything Provides a safe, comfortable learning environment.

Slide 77

Slide 77 text

Automated Infrastructure Tests

Slide 78

Slide 78 text

Warning: This field is still under heavy development

Slide 79

Slide 79 text

Honestly: I don’t trust devs to do ops, right now.

Slide 80

Slide 80 text

But... I don’t need to.

Slide 81

Slide 81 text

No content

Slide 82

Slide 82 text

Test that Chef runs complete successfully.

Slide 83

Slide 83 text

Run integration tests on top of that.

Slide 84

Slide 84 text

My Opinion: “Unit tests” for ops is still too new and doesn’t excite me yet.

Slide 85

Slide 85 text

Test at high level... Do the new changes apply cleanly? Can I still load the website? Is it still secure? Do all the interactions with the site still work?

Slide 86

Slide 86 text

Can we do better?

Slide 87

Slide 87 text

Can we do better? I think so. We need tools.

Slide 88

Slide 88 text

Also: Code Review

Slide 89

Slide 89 text

Ops engineers verify any non-ops contributions

Slide 90

Slide 90 text

No content

Slide 91

Slide 91 text

Developers are now safe to make their own ops changes.* * Ops supervision still important

Slide 92

Slide 92 text

Devs: Go Crazy.

Slide 93

Slide 93 text

A strong foundation.

Slide 94

Slide 94 text

Powerful insight via metrics.

Slide 95

Slide 95 text

Powerful insight via metrics. In-depth documentation.

Slide 96

Slide 96 text

Powerful insight via metrics. In-depth documentation. Production-mirror development.

Slide 97

Slide 97 text

Powerful insight via metrics. In-depth documentation. Production-mirror development. A safe learning environment.

Slide 98

Slide 98 text

Powerful insight via metrics. In-depth documentation. Production-mirror development. A safe learning environment. Infrastructure verification.

Slide 99

Slide 99 text

Powerful insight via metrics. In-depth documentation. Production-mirror development. A safe learning environment. Infrastructure verification. Devs doing Ops.

Slide 100

Slide 100 text

Powerful insight via metrics. In-depth documentation. Production-mirror development. A safe learning environment. Infrastructure verification. But: This is all DevOps.

Slide 101

Slide 101 text

Ops is a black box. Devs do all ops

Slide 102

Slide 102 text

WAIT! The most important question of all...

Slide 103

Slide 103 text

Who wears the pager?

Slide 104

Slide 104 text

On-call rotation for everybody.

Slide 105

Slide 105 text

Problem/Solution not in the Wiki? Call in the ops engineer.

Slide 106

Slide 106 text

Can’t fix the problem in 5 minutes or less? Call in the ops engineer.

Slide 107

Slide 107 text

I only care about the site or services going down.

Slide 108

Slide 108 text

Nagios [almost] never wakes me up.

Slide 109

Slide 109 text

No content

Slide 110

Slide 110 text

People aren’t overworked. Everyone shares responsibility.

Slide 111

Slide 111 text

THANK YOU I — DevOps Questions?