Operability in Serverless Environments

by Allan Espinosa

Slide 1

Slide 1 text

Serverlessͷૢ࡞ੑ Allan Espinosa

Slide 2

Slide 2 text

@AllanEspinosa PaaS Engineer

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

@AllanEspinosa CloudFoundry Experience • ։ൃͱӡ༻ • Private Cloud for other teams • “Platform team” “DevOps team” • ೔ຊͰ̏೥ಇ͖·ͨ͠

Slide 5

Slide 5 text

@AllanEspinosa Engine Yard Cloud Experience • DevOpsαϙʔτΤϯδχΞ • chef-solo 0.6.x, 10.x.x, 12.x.x (new) • PaaS Vendor

Slide 6

Slide 6 text

@AllanEspinosa Container Experience Kubernetes, CoreOS, Deis • DevOpsαϙʔτΤϯδχΞ • buildpacks • All container bugs!

Slide 7

Slide 7 text

@AllanEspinosa Operability without Servers • monitoring • deployment • security • networking

Slide 8

Slide 8 text

–M. Conway, “How Committees Invent,” Datamation, 1968. “… organizations which design systems… are constraint to produce designs which are copies of the communication structures of these organizations.” Conway’s Law @AllanEspinosa

Slide 9

Slide 9 text

@AllanEspinosa Operability on Conway won’t be achieved unless • importance not communicated • no discussion • Ops as second class citizens

Slide 10

Slide 10 text

Platform “Teams”

Slide 11

Slide 11 text

@AllanEspinosa Early Days of • Developer focus • ։ൃ͚ͩʂ • no operation tooling • logs, metrics, instrumentation • fork to achieve ૯࠶ੜ

Slide 12

Slide 12 text

@AllanEspinosa Fork • legal! bureaucracies! • priority mismatch • unaccepted patches ऐ͔ͬͨ͠

Slide 13

Slide 13 text

@AllanEspinosa Organizational changes • OSS ﬁrst • ࠜճ͠ • ϗϨϯι

Slide 14

Slide 14 text

@AllanEspinosa Community Evolution • Operability (Finally!) • Composability

Slide 15

Slide 15 text

@AllanEspinosa Early Chef (0.6) • early corporate contributor • ﬁrst Chef Server • mostly developers

Slide 16

Slide 16 text

Early Docker

Slide 17

Slide 17 text

@AllanEspinosa Show HN Resume-Driven Development , Inc. Raging and Forking Operability Time Visibility

Slide 18

Slide 18 text

“Other” Developers

Slide 19

Slide 19 text

@AllanEspinosa “Other” developers “Just focus on your application” • double-edged sword྆ਕͷ݋ • dev-oriented incentives • communicate operability

Slide 20

Slide 20 text

@AllanEspinosa Support Questions Devs • Our app is down. HELP! • How many instances should my application have? Ops • I debugged XXX, expected was A but got B. Can you help us dig deeper?

Slide 21

Slide 21 text

@AllanEspinosa Container “Adopters” • network is “reliable” • decentralized logging • blaming Docker

Slide 22

Slide 22 text

@AllanEspinosa

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

So Serverless

Slide 25

Slide 25 text

@AllanEspinosa Communication • Provider? • Customers? • Community? • Teammates?

Slide 26

Slide 26 text

–Melvin Conway “… ﬂexibiliy of organization is important to effective design.” Conwayͷ΋ͬͱॏཁͳϙΠϯτ @AllanEspinosa

Slide 27

Slide 27 text

Thank You @AllanEspinosa ςΟʔγϟπ͕͋Γ·͢Αʂ