The document discusses the role of Docker in DevOps, emphasizing its significance in creating a culture that automates processes, enhances communication, and fosters innovation. It outlines various aspects of DevOps, including the importance of microservices, process density, and configuration management simplification. Additionally, it highlights the challenges and advantages of adopting Docker, noting that its successful implementation requires a developer-driven approach to system architecture.

1. Docker Enables DevOps
Keep C.A.L.M.S. and Docker On …
Boyd E. Hemphill
@behemphi

2. Let’s Get Acquainted
Share a Perspective

3. Background
Oracle Developer,
MySQL DBA, PHP
Developer, System
Architect, DevOps
Director (snickering
encouraged), Evangelist

4. Background
Oracle Developer,
MySQL DBA, PHP
Developer, System
Architect, DevOps
Director (snickering
encouraged), Evangelist
Founded Austin DevOps
2012. 800+ Members.

5. Background
Oracle Developer, MySQL
DBA, PHP Developer,
System Architect, DevOps
Director (snickering
encouraged), Evangelist
Founded Austin DevOps
2012. 800+ Members.
DevOps Days Austin
Organizer

6. Background
Oracle Developer, MySQL
DBA, PHP Developer, System
Architect, DevOps Director
(snickering encouraged),
Evangelist
Founded Austin DevOps 2012.
800+ Members.
DevOps Days Austin Organizer
Lead Docker Austin 2014.
Nearly 500 Members.

7. Background
Oracle Developer, MySQL DBA,
PHP Developer, System Architect,
DevOps Director (snickering
encouraged), Evangelist
Founded Austin DevOps 2012.
800+ Members.
DevOps Days Austin Organizer
Lead Docker Austin 2014. Nearly
500 Members.
Founded Container Days 2015.
Austin, Boston, San Fran …

8. DevOps Perspective
Philosophy to Implementation

9. So … What is DevOps?

10. Text
Is DevOps a Culture?

11. Text
Is DevOps Automating all-the-things?

12. Text
Is DevOps Lean?

13. Text
Is DevOps Measuring impact?

14. Text
Is DevOps Sharing?

15. Text
The Goal of your Company?

16. Text
The Goal of your Company?
Make Money!

17. So … What is DevOps?
DevOps is a Philosophy

18. So … What is DevOps?
DevOps is a Philosophy
All of the previous are
models for the
implementation of that
philosophy

19. “DevOps is the way in which a technology
organization embeds itself in a business to the
benefit of that business.”

20. Pillars of Reasoning
From Ivory Tower to Neck Beard

21. Framework - Thought to
Action

22. Framework - Thought to
Action
Philosophy
Model
Implementation
Tools

23. Economic Observation

24. Economic Observation
P = R - C

25. Economic Observation
P = R - C
If C = 0, you are out of
business.

26. Economic Observation
P = R - C
If C = 0, you are out of
business.
R has no ceiling!

27. Technology vs. Tools

28. Technology vs. Tools
Tools are only a result of
implementing a DevOps
model

29. Technology vs. Tools
Tools are only a result of
implementing a DevOps
model
Technology enables the
creation of better tools

30. “Technology enables new business models and new
DevOps models. Tools are simply an expression of
those models.”

31. Technology vs. Tools
Virtualization - VMware, AWS, Heroku

32. Technology vs. Tools
Virtualization - VMware, AWS, Heroku
Config Mgmt - CFEngine, Puppet, Chef

33. Technology vs. Tools
Virtualization - VMware, AWS, Heroku
Config Mgmt - CFEngine, Puppet, Chef
Continuous Integration - Go, Jenkins, Travis, CircleCI

34. Technology vs. Tools
Virtualization - VMware, AWS, Heroku
Config Mgmt - CFEngine, Puppet, Chef
Continuous Integration - Go, Jenkins, Travis, CircleCI
Continuous Delivery - Artifactory, Nexus, Docker Hub

35. Technology vs. Tools
Virtualization - VMware, AWS, Heroku
Config Mgmt - CFEngine, Puppet, Chef
Continuous Integration - Go, Jenkins, Travis, CircleCI
Continuous Delivery - Artifactory, Nexus, Docker Hub
Service Discovery - Zookeeper, etcd, consul

36. Technology vs. Tools
Virtualization - VMware, AWS, Heroku
Config Mgmt - CFEngine, Puppet, Chef
Continuous Integration - Go, Jenkins, Travis, CircleCI
Continuous Delivery - Artifactory, Nexus, Docker Hub
Service Discovery - Zookeeper, etcd, consul
Containers - Jails, Zones, OpenVZ, LXC, Docker, Rocket

37. Language Matters

38. Language Matters
We do ourselves a
disservice by naming
technology with tools

39. Language Matters
We do ourselves a
disservice by naming
technology with tools
Talk about solving a
configuration
management issue
(model)

40. Language Matters
We do ourselves a
disservice by naming
technology with tools
Talk about solving a
configuration
management issue
(model)
Don’t talk about writing
Chef code (tool)

41. Language Matters
We do ourselves a disservice by
naming technology with tools
Talk about solving a
configuration management
issue (model)
Don’t talk about writing Chef
code (tool)
Understanding the nature of the
problem leads to the best
choice of tool

42. How Language Happens

43. How Language Happens
Good tools enable
technology use

44. How Language Happens
Good tools enable
technology use
CFEngine vs. Puppet vs.
Chef

45. How Language Happens
Good tools enable
technology use
CFEngine vs. Puppet vs.
Chef
VMware vs. Slicehost
vs. AWS

46. How Language Happens
Good tools enable
technology use
CFEngine vs. Puppet vs.
Chef
VMware vs. Slicehost
vs. AWS
LXC vs. Docker

47. “Docker enables the use of Linux containers by
mere mortals. Thus, it makes the containerization
technology a viable DevOps model.”

48. Docker, DevOps and the
Business
Linux Containers for Mere Mortals

49. Docker and DevOps

50. Docker and DevOps
Culture
Automation
Lean
Measurement
Sharing

51. DevOps and the Business

52. DevOps and the Business
Define an Opportunity
Discuss Benefits
Discuss Concerns
Explore Business
Perspective
Available Tools
Adoptions

53. Culture
Less Communication, More Features, More
Quality

54. Micro Services mean Micro
Teams

55. Definition

56. Micro Services mean Micro
Teams - Definition
Microservices
Architecture is where
each process has a
single purpose.

57. Benefits

58. Micro Services mean Micro
Teams - Benefits
“Code to Interface”
moves to infrastructure

59. Micro Services mean Micro
Teams - Benefits
“Code to Interface”
moves to infrastructure
Micro team’s service
moves at its own pace

60. Micro Services mean Micro
Teams - Benefits
“Code to Interface”
moves to infrastructure
Micro team’s service
moves at its own pace
Coordination between
people eased (Mythical
Man Month)

61. Micro Services mean Micro
Teams - Benefits
“Code to Interface”
moves to infrastructure
Micro team’s service
moves at its own pace
Coordination between
people eased (Mythical
Man Month)
Feature velocity increases

62. Concerns

63. Micro Services mean Micro
Teams - Concerns
Few coders understand
“code to the interface”

64. Micro Services mean Micro
Teams - Concerns
Few coders understand
“code to the interface”
Only Unicorns to reason
from currently

65. Micro Services mean Micro
Teams - Concerns
Few coders understand
“code to the interface”
Only Unicorns to reason
from currently
Migration of existing
apps is high risk

66. Business Perspective

67. Micro Services mean Micro
Teams - Business
Extraordinary increase in
Dev Team velocity
means true competitive
advantage

68. Micro Services mean Micro
Teams - Business
Extraordinary increase in
Dev Team velocity
means true competitive
advantage
Difficulty of adoption
means advantage is
lasting

69. Micro Services mean Micro
Teams - Business
Extraordinary increase in
Dev Team velocity means
true competitive
advantage
Difficulty of adoption
means advantage is
lasting
Dip a toe in low risk and
greenfield apps

70. Tools

71. Micro Services mean Micro
Teams - Tools
No tools exist to convert
legacy apps to a micro
service architecture

72. Micro Services mean Micro
Teams - Tools
No tools exist to convert
legacy apps to a micro
service architecture
Stuff it all in a single
container

73. Micro Services mean Micro
Teams - Tools
No tools exist to convert
legacy apps to a micro
service architecture
Stuff it all in a single
container
Bring in some help

74. Micro Services mean Micro
Teams - Tools
No tools exist to convert
legacy apps to a micro
service architecture
Stuff it all in a single
container
Bring in some help
http://12factor.net

75. Adoption

76. Micro Services mean Micro
Teams - Adoption
Shops are
experimenting with
whole apps in a
container first

77. Micro Services mean Micro
Teams - Adoption
Shops are
experimenting with
whole apps in a
container first
Greenfield startups are
designing for micro
services

78. Micro Services mean Micro
Teams - Adoption
Shops are experimenting
with whole apps in a
container first
Greenfield startups are
designing for micro
services
Many service companies
are springing up to help
with “containerization”

79. Automation
Faster Delivery means More Innovation

80. Build and Test Grids

81. Definition

82. Build and Test Grids -
Definition
Consider the set of all
app versions and
environments

83. Build and Test Grids -
Definition
Consider the set of all
app versions and
environments
Example: Ruby versions
across Ubuntu 12.04,
14.04 and Centos 6.5,
7.3 and Windows.

84. Build and Test Grids -
Definition
Consider the set of all app
versions and environments
Example: Ruby versions
across Ubuntu 12.04,
14.04 and Centos 6.5, 7.3
and Windows.
Very important to installed
software and legacy
application management.

85. Benefits

86. Build and Test Grids -
Benefits
Containers start in less
than one second - faster
builds

87. Build and Test Grids -
Benefits
Containers start in less
than one second - faster
builds
Can test more
permutations of the
system

88. Build and Test Grids -
Benefits
Containers start in less
than one second - faster
builds
Can test more
permutations of the
system
Increase build
parallelism

89. Build and Test Grids -
Benefits
Containers start in less
than one second - faster
builds
Can test more
permutations of the system
Increase build parallelism
Increases feature velocity
and innovation

90. Concerns

91. Build and Test Grids -
Concerns
Is a container based test
bed close enough to
production?

92. Build and Test Grids -
Concerns
Is a container based test
bed close enough to
production?
Impedance: How does
app get to prod if not via
container?

93. Business

94. Build and Test Grids -
Business
Grid density lowers cost

95. Build and Test Grids -
Business
Grid density lowers cost
Increased innovation
due to build time
decrease

96. Build and Test Grids -
Business
Grid density lowers cost
Increased innovation
due to build time
decrease
Increased feature
velocity (unicorn
example)

97. Build and Test Grids -
Business
Grid density lowers cost
Increased innovation due
to build time decrease
Increased feature
velocity (unicorn
example)
Decrease QA Bottleneck

98. Tools

99. Build and Test Grids - Tools
Build and test images as
artifacts still immature
Build: Jenkins, CircleCI,
Shippable

100. Build and Test Grids - Tools
Build and test images as
artifacts still immature
Build: Jenkins, CircleCI,
Shippable
Artifact management still
immature
Artifact: Docker Registry,
Quay.io, Artifactory

101. Build and Test Grids - Tools
Build and test images as artifacts
still immature
Build: Jenkins, CircleCI, Shippable
Artifact management still
immature
Artifact: Docker Registry, Quay.io,
Artifactory
Delivery is unsolved
StackEngine, CircleCI, Shippable

102. Adoption

103. Build and Test Grids -
Adoption
Common adoption path

104. Build and Test Grids -
Adoption
Common adoption path
Driving legacy apps to
containers (Websphere!)

105. Build and Test Grids -
Adoption
Common adoption path
Driving legacy apps to
containers (Websphere!)
Production adoption
creates impedance

106. Build and Test Grids -
Adoption
Common adoption path
Driving legacy apps to
containers (Websphere!)
Production adoption
creates impedance
Done with no impact to
other teams

107. Configuration Management
Simplification

108. Definition

109. Configuration Management
Simplification - Definition
Automate the state of a
single machine
This is not orchestration

110. Benefits

111. Configuration Management
Simplification - Benefits
Learning curve of typical
CM tool is extremely
steep

112. Configuration Management
Simplification - Benefits
Learning curve of typical
CM tool is extremely
steep
Docker obviates need
for most host config
(bakery)

113. Configuration Management
Simplification - Benefits
Learning curve of typical
CM tool is extremely
steep
Docker obviates need for
most host config (bakery)
Containers are
configured via a simple
bash-like file.

114. Concerns

115. Configuration Management
Simplification - Concerns
Is a Dockerfile enough
for complex
applications?

116. Configuration Management
Simplification - Concerns
Is a Dockerfile enough
for complex
applications?
How to transition from
updating in place to
immutable release

117. Business

118. Configuration Management
Simplification - Business
Removal of complexity
lowers release and
administrative risk

119. Configuration Management
Simplification - Business
Removal of complexity
lowers release and
administrative risk
Scaling issues of most
CM tools are moot.

120. Tools

121. Configuration Management
Simplification - Tools
Bakery model for hosts

122. Configuration Management
Simplification - Tools
Bakery model for hosts
Dockerfile for containers

123. Configuration Management
Simplification - Tools
Bakery model for hosts
Dockerfile for containers
Multihost image
management:
StackEngine

124. Adoption

125. Configuration Management
Simplification - Adoption
Companies who adopt
Docker in production
gradually realize they
need CM less and less

126. Configuration Management
Simplification - Adoption
Companies who adopt
Docker in production
gradually realize they
need CM less and less
This is true in every case
we have encountered
including our own

127. Measurement
Function, Performance, Stress, Security

128. Process Density

129. Definition

130. Process Density - Definition
Density increases when
the amount of idle
compute on a host
tends to zero

131. Benefits

132. Process Density - Benefits
Reduce host
consumption reduces
cost

133. Process Density - Benefits
Reduce host
consumption reduces
cost
Reduces power footprint
in large physical setting

134. Concerns

135. Process Density - Definition
Spare capacity is no
longer there when
spikes occur

136. Process Density - Definition
Spare capacity is no
longer there when
spikes occur
Another complexity layer

137. Process Density - Definition
Spare capacity is no
longer there when
spikes occur
Another complexity layer
Container Sprawl

138. “Ants not Cattle”

139. Business

140. Process Density - Business
Reduced hosts mean
reduced cost (CapEx
and OpEx)

141. Process Density - Business
Reduced hosts mean
reduced cost (CapEx
and OpEx)
Does not address
revenue growth

142. Process Density - Business
Reduced hosts mean
reduced cost (CapEx
and OpEx)
Does not address
revenue growth
Probably not a
compelling reason, but
easy to understand

143. Tools

144. Process Density - Tools
Basic management
tools for multi host
inventory

145. Process Density - Tools
Basic management
tools for multi host
inventory
StackEngine, Tutum,
Fleet

146. Process Density - Tools
Basic management
tools for multi host
inventory
StackEngine, Tutum,
Fleet
Scheduling to help with
usage spikes

147. Adoption

148. Process Density - Adoption
Mostly production
concern

149. Process Density - Adoption
Mostly production
concern
Much talk, little action

150. Process Density - Adoption
Mostly production
concern
Much talk, little action
Revolution not evolution

151. Process Density - Adoption
Mostly production
concern
Much talk, little action
Revolution not evolution
Tools for production
management are hard to
use (Kubernetes, Mesos)

152. Sharing
Faster Features, Fewer Surprises

153. Disposable Development
Environments

154. Definition

155. Disposable Development
Environments - Definition
A fully functional
development
environment that can be
brought up in minutes or
seconds

156. Benefits

157. Disposable Development
Environments - Benefits
New team members are
productive their first day

158. Disposable Development
Environments - Benefits
New team members are
productive their first day
Innovation - try new
things quickly

159. Disposable Development
Environments - Benefits
New team members are
productive their first day
Innovation - try new
things quickly
Developers share
improvements easily via
familiar tools

160. Concerns

161. Disposable Development
Environments - Concerns
Impedance: Config
changes across teams
(Dev, QA, Ops)

162. Business

163. Disposable Development
Environments - Business
Increases feature
velocity

164. Disposable Development
Environments - Business
Increases feature
velocity
Increases innovation

165. Disposable Development
Environments - Business
Increases feature
velocity
Increases innovation
Local optima

166. Tools

167. Disposable Development
Environments - Tools
Virtual Box

168. Disposable Development
Environments - Tools
Virtual Box
Vagrant

169. Disposable Development
Environments - Tools
Virtual Box
Vagrant
boot2docker

170. Disposable Development
Environments - Tools
Virtual Box
Vagrant
boot2docker
kitematic

171. Disposable Development
Environments - Tools
Virtual Box
Vagrant
boot2docker
kitematic
docker compose

172. Adoption

173. Disposable Development
Environments - Adoption
Common adoption path

174. Disposable Development
Environments - Adoption
Common adoption path
Typically done in lieu of
Vagrant

175. Disposable Development
Environments - Adoption
Common adoption path
Typically done in lieu of
Vagrant
Often gains traction with
QA!

176. Food for Thought
Less developed use cases.

177. Food for Thought
Immutable infrastructure

178. Food for Thought
Immutable infrastructure
A/B Deployments

179. Food for Thought
Immutable infrastructure
A/B Deployments
A/B Testing for
Marketing

180. Future Past
Containers in production are already happening.

181. Future Past
Pantheon/Rackspace
blog: http://bit.ly/
15a2UIW
Note the date: October
7th, 2013
Docker makes this
easier to consider in our
own context

182. Text
Robots and Unicorns
Docker makes containers available to mere
mortals.

183. Closing Thoughts
How do I determine if Docker is worth
investigating?

184. Business

185. Business
Developer adoption of Docker is only valuable as a first
step. There is not enough benefit from it alone to justify
the effort, it must inform system architecture and
production operations over time.

186. Business
Developer adoption of Docker is only valuable as a first
step. There is not enough benefit from it alone to justify
the effort, it must inform system architecture and
production operations over time.
Docker’s system architecture ramifications have the
potential to provide a significant and lasting competitive
advantage

187. Business
Developer adoption of Docker is only valuable as a first step.
There is not enough benefit from it alone to justify the effort, it
must inform system architecture and production operations
over time.
Docker’s system architecture ramifications have the potential
to provide a significant and lasting competitive advantage
Unlike most ops driven improvements derived from applying
DevOps thinking, this must be developer and QA driven
since the greatest benefit is derived from system architecture

188. Business
Developer adoption of Docker is only valuable as a first step. There
is not enough benefit from it alone to justify the effort, it must
inform system architecture and production operations over time.
Docker’s system architecture ramifications have the potential to
provide a significant and lasting competitive advantage
Unlike most ops driven improvements derived from applying
DevOps thinking, this must be developer and QA driven since the
greatest benefit is derived from system architecture
Horses are starting to become unicorns. Evolve or die.

189. DevOps

190. DevOps
Culture - DevOps thought leaders must determine how
a Docker adoption path looks in their organization

191. DevOps
Culture - DevOps thought leaders must determine how
a Docker adoption path looks in their organization
Automation - Tools are not there yet. Companies are
showing up with the mission to address this, but it is
very early days.

192. DevOps
Culture - DevOps thought leaders must determine how
a Docker adoption path looks in their organization
Automation - Tools are not there yet. Companies are
showing up with the mission to address this, but it is
very early days.
Lean - DevOps thought leaders are responsible for the
holistic impact of technology decisions at the business
level.

193. DevOps
Culture - DevOps thought leaders must determine how a
Docker adoption path looks in their organization
Automation - Tools are not there yet. Companies are showing
up with the mission to address this, but it is very early days.
Lean - DevOps thought leaders are responsible for the holistic
impact of technology decisions at the business level.
Measurement - Empiricism is required if we are to meet our
Measurement obligation. Blackbox thinking could revolutionize
compliance.

194. DevOps
Culture - DevOps thought leaders must determine how a Docker adoption path
looks in their organization
Automation - Tools are not there yet. Companies are showing up with the
mission to address this, but it is very early days.
Lean - DevOps thought leaders are responsible for the holistic impact of
technology decisions at the business level.
Measurement - Empiricism is required if we are to meet our Measurement
obligation. Blackbox thinking could revolutionize compliance.
Sharing - DevOps thought leaders should be working with peers and
collaborators in their company to determine if they can derive the proposed
business benefits.

195. Should you be considering a
Docker adoption?

196. Best Ever DevOps Tool:
audible.com
The Lean Startup - Reis (tech)
The Goal - Goldratt (Theory of Constraints)
It’s not Luck - Goldratt (Theory of Constraints)
Good to Great - Collins (Culture)
The No Asshole Rule - Sutton (Culture)
The Phoenix Project - Kim (*) (tech)
Continuous Deliver - Humble (*) (hardcore tech)
The Lean Enterprise - Humble (*) (tech)