Modern devOps with Docker
38
devops with docker @beshippable
-
Upload
avi-cavale -
Category
Technology
-
view
267 -
download
0
Transcript of Modern devOps with Docker
devops with docker@beshippable
the most frequently asked question during an outage
the most frequently asked question during an outage
what changed?
the immediate next question is….
the immediate next question is….
who made the change?
both questions are bad for your business
both questions are bad for your business
slowing down
both questions are bad for your business
courtesy : dilbert comics
slowing down finger pointing
change is the root cause of almost all outages, but…
change is the root cause of almost all outages, but…
“business requires change”
“need to embrace change”
dev$app$A$
dev$app$B$
dev ops
“need to embrace change”
dev$app$A$
dev$app$B$
dev ops
devops: a CULTURE of embracing change
we embraced it tightly
time
change required
change complete
traditional
application delivery pipeline
time
change required
change complete
development
traditional
application delivery pipeline
time
change required
change complete
development unit testing
traditional
application delivery pipeline
time
change required
change complete
development unit testing functional testing
traditional
application delivery pipeline
time
change required
change complete
development unit testing functional testing deployment
traditional
application delivery pipeline
time
change required
change complete
development unit testing functional testing deployment running
traditional
application delivery pipeline
time
change required
development unit testing functional testing deployment running
devops culture embraced
change complete
application delivery pipeline
time
change required
development unit testing functional testing deployment running
devops culture embraced
change complete
15-20% improvement
application delivery pipeline
time
change required
development unit testing functional testing deployment running
devops culture embraced
change complete
15-20% improvement
org silo friction1
application delivery pipeline
time
change required
development unit testing functional testing deployment running
devops culture embraced
change complete
15-20% improvement
org silo friction1
tool chain vertically optimized2
application delivery pipeline
time
change required
development unit testing functional testing deployment running
devops culture embraced
change complete
15-20% improvement
org silo friction1
tool chain vertically optimized2
deployable image built last3
application delivery pipeline
20% better is not a REVOLUTION!
courtesy : V for Vendetta
courtesy : V for Vendetta
why not build deployable image first?
devops is culture, so to make it a
FACT
devops is culture, so to make it a
application delivery pipelines
FAC
rictionless
gile
ontinuous
ransparentT
Transparencyif you want to do just 1 thing this year
every action
• starts in a chat room
• tracked as a github issue
• ends in a chat room
Transparencyif you want to do just 1 thing this year
business req
support
prod errors
every action
• starts in a chat room
• tracked as a github issue
• ends in a chat room
Continuous
• continuous integration for every pull-request
• 1 step docker build image for every merge to `master`
• 1 step auto deploy & continuous functional testing
• deployment to prod is just changing an ENV var
Agile• no SSH!
• bug fixes, new changes, ops scripts all go the same way
• always deployable `master` • no feature branching
• feature flags • in-code branching
• small frequent changes • beta program
Frictionless
r10r11r12api
r19r20r21fe
container fab
dev
beta
prod
r12 apir21 fe
r11 apir20 fe
r10 apir20 fe
i234
i179
i444
i534
i191
i744
app delivery pipelines
ship images 40-60 times a day
noticeable FACTs
15 devs in 5 timezones
2hrs mean time to resolve bugs
where are we going from here?
micro-services baby!
throughput creates merge hell
rapid changes on 1 repo creates
images chaos
signup for our beta program
45,000 devs on Shippable
25,000 build containers/week
quiz me
thank you very much
@beshippable
