-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
374 lines (257 loc) · 6.72 KB
/
index.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
<!DOCTYPE html>
<html>
<head>
<style type="text/css">
@import url(https://fonts.googleapis.com/css?family=Yanone+Kaffeesatz);
@import url(https://fonts.googleapis.com/css?family=Droid+Serif:400,700,400italic);
@import url(https://fonts.googleapis.com/css?family=Ubuntu+Mono:400,700,400italic);
body {
font-family: 'Proxima Nova';
color: white;
}
h1,
h2,
h3 {
color: #00cdbe;
font-family: 'Proxima Nova';
font-weight: normal;
}
.remark-code,
.remark-inline-code {
font-family: 'Ubuntu Mono';
}
li {
font-size: xx-large
}
p img {
width: 90%
}
.image-avatar img {
width: 150px;
height: 150px;
border-radius: 50%;
object-fit: cover;
object-position: center right;
}
.footnote img {
width: 20%
}
.footer { position: absolute; bottom: 12px; left: 20px }
.footer span { height: 30px; padding-left: 20px; font-size: small; text-align: top;}
</style>
</head>
<body>
<textarea id="source">
layout: true
name: background
background-color: black
---
template: background
background-image: url(images/EvolutionTitle.png)
background-size: contain
class: bottom
## .center[Evolution of Infrastructure as Code]
### .center[A Weedmaps DevOps Journey]
???
---
template: background
background-image: url(images/wm-leaves-dark.jpg)
# Who Am I? .image-avatar[]
* Rakesh Patel
* Senior Systems Engineer @ Weedmaps
* 20 year career
* data engineering, backend systems, frontend, infrastructure
* golang
---
template: background
background-image: url(images/EvolutionTitle2.png)
background-size: contain
???
Paul Hinze - Applying Graph Theory to Infrastructure as Code
DevOps Journeys
- DevOps feedback loops
- Journeys examine those loops
- little hippie like that
---
template: background
background-image: url(images/ManualEvolution.png)
background-size: contain
# .center[Manual]
???
Rack & Stack
golden images
ssh administration
---
template: background
background-image: url(images/BasicAutomationEvolution.png)
background-size: contain
# .center[Basic Automation]
???
distributed rsync
hosted package repos
agents
get nostalgic
---
template: background
background-image: url(images/MachineVirtualizationEvolution.png)
background-size: contain
# .center[Machine Virtualization]
???
organizations build test/dev infrastructure
physical hardware represented by software (configuration)
beginnings of automated infrastructure
---
template: background
background-image: url(images/CommoditizationOfInfrastructure.png)
background-size: contain
# .center[Commoditization of Infrastructure]
???
Large orgs got good at this, started representing as API's
start out writing custom bash
Terraform - represent as config, state stored as json
---
template: background
background-image: url(images/SimpleWebArchitecture.png)
background-size: contain
class: middle, center
???
capabilities complexity
basic web arc
the cloud is not reliable
---
template: background
background-image: url(images/LegacyOps.png)
background-size: contain
class: bottom
# .left[Legacy Ops]
???
Ansible - yaml driven configuration
Outsourced Ops - when you outsource, lessons learned aren't retained
young company
---
template: background
background-image: url(images/BlueGreenDeploy.png)
background-size: contain
class: center
# Blue Green Deploys
???
update ELB's
---
template: background
background-image: url(images/AMIOhMy.png)
background-size: contain
# AMI's, oh my!
???
nightly build of golden ami (45min)
build new ami from golden ami, rebuild
what happens if the build fails at the 45th min
now multiply that by a factor of 10
fledgling industry, fledgling company, still trying to understand
---
template: background
background-image: url(images/WheresTheTruth.png)
background-size: contain
# Where's The Truth?
???
Documentation?
Cost Analysis?
---
template: background
background-image: url(images/wm-leaves-dark.jpg)
# .center[So What Do We Want]
* Infrastructure is version controlled
--
* Infrastructure is repeatable
--
* Provide fast delivery of software
---
template: background
background-image: url(images/Terraform.png)
background-size: contain
---
template: background
background-image: url(images/GitOpsV1.png)
background-size: contain
class: bottom, left
## Weedmaps GitOps v0.1
???
Problems
- terraform code base started getting Large
- jenkins tough to work with
- chefdk environment sensitive
---
template: background
background-image: url(images/DataCenterAsCompute.png)
background-size: contain
# Datacenter as Compute
???
chroot became powerful
orchestration/scheduling
---
template: background
background-image: url(images/SimpleWebArchitectureV2.png)
background-size: contain
???
Not very different
Software not deployed at the instance level
Groups of compute and memory units
---
template: background
background-image: url(images/FasterDeployments.png)
background-size: contain
???
image builds are fast (don't have to actually startup a virt)
container orchestration
scheduler starts containers and removes the old ones
app startup times must be fast
setup and configuration run as separate tasks
minimal coordination
---
template: background
background-image: url(images/GitOpsV2.png)
background-size: contain
???
smaller state files
use refspec flow for terraform
chef still the ugly stepchild
---
template: background
background-image: url(images/wm-leaves-dark.jpg)
# Lessons Learned
* adoption
* don't have to get it right the first time
* culture change
* may want to make the instance fail
* assume the network will not work
* ensure tooling, there's no one golden tool
* chatops
* capabilities and complexity
* if there's an AWS service for it, use it
???
perspectives change
how you build your app is looked at differently
toil of using new tech and complexity but the capabilities gained aren't noticed
---
template: background
background-image: url(images/wm-leaves-dark.jpg)
# References
* Paul Hinze - Applying Graph Theory To Terraform [https://www.youtube.com/watch?v=Ce3RNfRbdZ0](https://www.youtube.com/watch?v=Ce3RNfRbdZ0)
* DevOps KungFu - [https://github.com/chef/devops-kungfu](https://github.com/chef/devops-kungfu)
* Refspectacular - [https://github.com/JNKRMN/RefSpectacular](https://github.com/JNKRMN/RefSpectacular)
* And how you connect thru the interwebs
* @rocpatel
* github.com/rocpatel
---
template: background
background-image: url(images/KungFuOps.png)
background-size: contain
???
journeys r a way of practicing while providing value
</textarea>
<script src="https://remarkjs.com/downloads/remark-latest.min.js">
</script>
<script>
var slideshow = remark.create();
</script>
</body>
</html>