-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathslides.html
638 lines (402 loc) · 12.1 KB
/
slides.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
<!DOCTYPE html>
<html>
<head>
<title>Introduction to DevOps</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<link rel="stylesheet" type="text/css" href="fonts.css">
<link rel="stylesheet" type="text/css" href="style.css">
</head>
<body>
<textarea id="source">
layout: true
class: white-text
name: cover
background-image: url(images/devops.png)
background-size: 50%
background-position: center 20%
---
layout: true
class: divider
name: divider
background-color: #26546D
---
layout: true
class: divider
name: sub-divider
background-color: #70AD47
---
template: cover
<div class="footer bottombox" style="background-color: #2C4B60;">
<h1>Introduction to DevOps</h1>
<h3>Martin Fietz</h3>
</div>
<div class="footer bottombox">
<h1>Introduction to DevOps</h1>
<h3>Martin Fietz</h3>
</div>
---
layout: true
---
# Agenda
1. What it is & what it is not
2. Goals & Short History
3. The Three Ways
4. CALMS
5. Challenges
6. Resources
---
class: center
# Why?
<font class="container" size="6"><strong>BLUF:</strong>
<p><nobr>We are follow the principles,</nobr></p>
<p><nobr>we might as well do DevOps <em>deliberately</em></nobr></p>
</font>
---
# 2017 State of DevOps Report
* automation is directly linked to organization competitiveness
* high performers achieve both faster throughput and better stability:
* 46 times more frequent code deployments
* 440 times faster lead time from commit to deployments
* 96 times faster mean time to recover
* 5 times lower change failure rate
* DevOps applies to all organizations
* Lean product management drives higher
organizational performance
→ strong evidence that DevOps practices lead to higher IT performance
---
template: divider
# DevOps is *not* ...
---
# DevOps is not...
* a role/job title ("DevOps Engineer")
* would be an issue for collaboration and end-to-end-responsibility
* only (infrastructure) automation
* just one aspect of many
* getting rid of ops - "NoOps"
* as development assumes more ownership and responsibility,<br>
*Ops is more important than ever*
* sysadmins who code
---
# DevOps is not... (Cont'd)
* DevOps teams
* creates just another functional silo between dev and ops
* knowledge gap
* further concentrates responsibility
* ownership of product?
* basically release engineering
---
template: divider
# Devops is...
---
class: center
# DevOps Explained
<img src="images/devops-explained-0.png" style="width: 70%;"/>
---
template: sub-divider
# Interlude: Dev vs Ops
---
# Dev vs Ops
<div style="text-align: center">
<img src="images/department-for-change.jpg" style="width: 30%;"/>
<img src="images/department-against-change.jpg" style="width: 30%;"/><br>
<em><small>Source: hikingartist.com/</small></em>
</div>
---
# Dev vs Ops
<table style="width:100%; border-spacing: 1em;">
<tr>
<th>Dev</th>
<th>Ops</th>
</tr>
<tr>
<td>business priorities:<br>get innovation to users, fast</td>
<td>protect business from disruption</td>
</tr>
<tr>
<td>application performance</td>
<td>application availability / stability</td>
</tr>
<tr>
<td>end-user analytics</td>
<td>infrastructure & application metrics</td>
</tr>
<tr>
<td>code quality</td>
<td>end user complaints</td>
</tr>
<tr>
<td>code-level errors</td>
<td>performance analytics</td>
</tr>
<tr>
<td><strong>lack of operational mindest</strong></td>
<td><strong>lack of development mindest</strong></td>
</tr>
</table>
---
count: false
# Dev vs Ops
<table style="width:100%; border-spacing: 1em;">
<tr>
<th>Dev</th>
<th>Ops</th>
</tr>
<tr>
<td>business priorities:<br>get innovation to users, fast</td>
<td>protect business from disruption</td>
</tr>
<tr>
<td>application performance</td>
<td>application availability / stability</td>
</tr>
<tr>
<td>end-user analytics</td>
<td>infrastructure & application metrics</td>
</tr>
<tr>
<td>code quality</td>
<td>end user complaints</td>
</tr>
<tr>
<td>code-level errors</td>
<td>performance analytics</td>
</tr>
<tr>
<td><strong>lack of operational mindest</strong></td>
<td><strong>lack of development mindest</strong></td>
</tr>
</table>
<p align="center"><br>
<strong><font color="red">These are merely means to an end, not end goals</font></strong>
</p>
---
class: center
# DevOps Explained
<img src="images/devops-explained-1.png" style="width: 70%;"/>
---
class: center
# DevOps Explained
<p> </p>
<p> </p>
<p> </p>
<img src="images/devops-explained-2.png" style="width: 75%;"/>
---
class: center
# DevOps Explained
<p> </p>
<img src="images/devops-explained-3.png" style="width: 75%;"/>
---
# DevOps is ...
> DevOps is the practice of operations and development engineers participating
together in the entire service lifecycle, from design through the development process to production support.
<div style="text-align: right">Ernest Mueller [theagileadmin.com]</div>
<p> </p>
> DevOps is just the agile principle, taken to the full enterprise.
<div style="text-align: right">Rosalind Radcliffe</div>
---
# DevOps is ...
* Originally, union of sub-disciplines Dev and Ops
* a <em>mindset</em> or cultural <em>movement</em>
* learning culture and practice
* strategies that break down silos & facilitate collaboration
* not actually "new" or revolutionary - but it does not claim to be
* encourage ownership & accountability - "you build it, you run it"
---
# Goals
* shorter development & feedback cycles
* faster time to market
* improve mean time to recovery (MTTR)
* lower failure rates of new releases
* eliminate technical debt and unplanned work
* alignment with business objectives
---
template: divider
# A Short History
---
# History
* 2008: Andrew Shafer posted an idea for an agile infrastructure session at the Agile 2008 Conference. <br>Only a single person, Patrick Debois, showed up.
* 2009: *10+ Deploys Per Day: Dev and Ops Cooperation at Flickr* presentation<br>
This inspired Patrick to create his own conference
* 2009: First DevOpsDays conference
* 2010: First DevOpsDays US
* 2011: DevOps goes mainstream<br>Before, movement still mainly fueled by individuals and open source tools
* 2014: Large companies like Target, Nordstrom and LEGO adapt DevOps
---
template: divider
# The Three Ways
---
# The First Way: Systems Thinking
<div class="boxed" style="text-align: center">Business → Dev → Ops → Customer</div>
*Improve work flow from left to right*, i.e. performance of the entire system
* lower amount of Work in Progress (WIP)
* WIP only creates value as finished product
* faster flow will deliver value faster
* remove constraints (person, technology, culture, process)
---
# The Second Way
<div class="boxed" style="text-align: center">Business ↔ Dev ↔ Ops ↔ Customer</div>
**Enhance feedback loops from right to left**
* improve both number of feedback loops and speed
* stop if error is found and transmit as fast as possible to source
* e.g. designing quality into product at earliest stage
---
# The Third Way
**Continuous experimentation and learning**
* create culture where
* constant experimentation and learning is encouraged
* people acknowledge that way to mastery is through repetition and practice
* take risks and learn from failures
* controlled: risk is not too big (small WIP) and fast feedback on changes
* ensuring to continually put tension into system to continually reinforce habits and improve
---
template: divider
# CALMS
---
# CALMS
<figure style="float: right">
<img src="images/calms.png" width="400" />
<center>
<figcaption><em><small>Source: DevOpsGuys / Redgate</small></em></figcaption>
</center>
</figure>
* <strong>C</strong> ulture
* <strong>A</strong> utomation
* <strong>L</strong> ean
* <strong>M</strong> easurement
* <strong>S</strong> haring
---
# Culture
<p> </p>
<p> </p>
> Even with the best tools, DevOps is just another buzzword if you don't have the right culture.
<div style="text-align: right">Rouan Wilsenach</div>
---
# Culture
* increased collaboration
* shared responsibility
* blameless post-mortem/retrospectives
* failures as learning opportunities
* honesty and openness
* transparency
* trust & autonomy
---
count: false
# Culture
* increased collaboration
* shared responsibility
* blameless post-mortem/retrospectives
* failures as learning opportunities
* honesty and openness
* transparency
* trust & autonomy
<br>
<strong>What's your opinion - where do we stand?</strong>
---
# Case Example: Culture at Netflix
1. Encourage independent decision-making by employees
2. Share information openly, broadly and deliberately
3. Are extraordinarily candid with each other
4. Keep only our highly effective people
* adequate performers receive a generous severance package
5. Avoid rules
* policy for travel, entertainment, gifts, and other expenses: "act in Netflix’s best interest"
* vacation policy: "take vacation"
* avoid over-correcting when freedom is abused
*Source: https://jobs.netflix.com/culture*
---
# Automation: Goals
* enabler for devops
* fast feedback
* save time
* prevent defects
* consistency & repeatability
* self-service
---
# Automation: Tools
<div align="center">
<img src="images/devops-tools.png" style="width: 90%;"/>
</div>
---
# Lean
* focus on identifying value streams
* eliminate waste: keeping everything minimal, yet useful; e.g.
* small and frequent deployments
* team size
* continuous improvement, e.g.
* regular retrospectives
* A/B testing
* embracing failure
* absorb, recover, learn → anti-fragility
* postmortems focus on where processes fell down and how to strengthen them
---
# Measurement
* track metrics and use information to drive feedback loops and objective, blameless decision making
* end-to-end visiblity for applications, infrastructure, and digital business as a whole
* beware of cultural impact: behavioural changes b/c something is measured
**Examples**
* Business Success: Conversion rate, avg revenue per user
* Customer Experience: response time of key business transactions, customer satisfaction
* Application Performance: Uptime, response times, resource utilization
* Speed: lead time for changes, mean time to resolution
* Software Quality: error rates, outstanding bugs
---
# Sharing
* share goals to establish a common purpose
* exchange ideas across teams
* sharing tools, discoveries and lessons
* find people with similar needs and collaborate to elinimate duplicate work
* conference participation: motivation and information
---
template: divider
# Challenges
---
# Challenges
* management buyin (top-down sponsorship): introduction costs time and money
* culture change: resistance to change
* legacy systems & infrastructure
* tool turbulance
* cross-functional teams
* share resources: making time for non-product Work
* constant context switching
* "no one can serve two masters"
* process challenges: with power comes great responsibility
---
template: divider
# Resources
---
# Resources
<div style="text-align: center">
<img src="images/phoenix-project.jpg" height="450" style="margin-right: 2em">
<img src="images/devops-handbook.jpg" height="450">
</div>
---
# Resources (Cont'd)
<div style="text-align: center">
<img src="images/release-it.jpg" height="200" style="margin-right: 2em">
<img src="images/site-reliability-engineering.jpg" height="200" style="margin-right: 2em">
<img src="images/continuous-delivery.jpg" height="200">
</div>
<p> </p>
* Weekly Devops Email Newsletter: http://www.devopsweekly.com
* Awesome Devops: https://github.com/AcalephStorage/awesome-devops
* 2017 State of DevOps Report: https://puppet.com/resources/whitepaper/state-of-devops-report
---
<!-- CONTEND END -->
</textarea>
<script src="remark.js" type="text/javascript">
</script>
<script type="text/javascript">
var slideshow = remark.create({
ratio: '16:10',
highlightLanguage: 'kotlin',
highlightStyle: 'idea',
highlightLines: true,
highlightSpans: true,
navigation: {
scroll: false // disable nagivation using scroll
}
});
</script>
<script src="remark-zoom.js" type="text/javascript"></script>
</body>
</html>