The document discusses embracing change within a DevOps culture to improve application delivery pipelines while minimizing outages and friction. It emphasizes the importance of continuous integration, frequent deployments, and a streamlined approach to handling changes in code and deployments. The author outlines a modern DevOps platform that supports frequent shipping and rapid bug resolution.

1. modern devops
with docker
@beshippable

2. avi cavale
co-founder & ceo
@avinci || avi@shippable.com
continuous app delivery pipelines

3. the most frequently asked question
during an outage
what changed?

4. the immediate next question is….
who made the change?

5. both questions are bad for your business
courtesy : dilbert comics
slowing down finger pointing

6. change is the root cause of almost all
outages, but…
“business requires change”

7. “need to embrace change”
dev$
app$A$
dev$
app$B$
dev ops
devops: a CULTURE of embracing change

8. we embraced it tightly

9. time
change
required
change
complete
development unit testing functional testing deployment running
traditional
application delivery pipeline

10. 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

11. 20% better is not a REVOLUTION!
courtesy : V for Vendetta

12. courtesy : V for Vendetta
why not build deployable image first?

13. devops is culture, so to make it a
application
delivery
pipelines
F
A
C
rictionless
gile
ontinuous
ransparent
T

14. Transparency
if 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

15. 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

16. Agile
• no SSH!
• bug fixes, new changes, ops scripts all go the same way
• no BRANCHING
• always deployable ‘master/trunk’
• feature flags
• in-code branching
• small frequent changes
• beta users

17. Frictionless
r10
r11
r12
api
i234
i179
i444
immutable images
fe
i534
i191
i744
r20
r21
r22
container fab
dev
beta
prod
r12 api
r21 fe
r11 api
r20 fe
r10 api
r20 fe

18. we ship 20-40 times a day
noticeable FACTs
15 devs in 3 timezones
2hrs mean time to resolve bugs

19. devOps
modern devOps

20. dev
Ops
modern devOps

21. dev
Ops
modern devOps
• continuous delivery
without devOps code
• smart, containerized
environments
• decoupled infrastructure

22. modern devOps platform
source
code
image
registry
OpenShift
Enterprise 3
private
registry
deployment pipelines ————-—>
pre-CI
build
unit
testing
post-CI
build
Dry Dock Lighthouse
int
dev-1
dev-2
db
web
prod
ap
we
db
ap
we
app
db

23. try it
www.shippable.com
&
we are hiring!
@beshippable