The pillars of DevOps are Culture, Automation, Measurement and Sharing. Docker is a rare tool at enables DevOps through all 4 pillars. These slides take a look at how Docker can affect each pillar in your organization through a Lean lens.

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. What is a Container?
A VM is a full copy of on
an entire computer
running as software via
a hypervisor

51. What is a Container?
A VM is a full copy of on
an entire computer
running as software via
a hypervisor
A container is a slice of
the kernel

52. What is a Container?
A VM is a full copy of on
an entire computer
running as software via a
hypervisor
A container is a slice of
the kernel
Executive Summary: The
lack of extra layers means
big efficiency savings

53. Docker and DevOps
Culture
Automation
Lean
Measurement
Sharing

54. DevOps and the Business

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

56. Culture
Less Communication, More Features, More
Quality

57. Micro Services mean Micro
Teams

58. Definition

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

60. Benefits

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

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

63. 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)

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

65. Concerns

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

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

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

69. Business Perspective

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

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

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

73. Tools

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

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

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

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

78. Adoption

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

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

81. 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”

82. Automation
Faster Delivery means More Innovation

83. Build and Test Grids

84. Definition

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

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

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

88. Benefits

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

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

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

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

93. Concerns

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

95. 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?

96. Business

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

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

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

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

101. Tools

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

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

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

105. Adoption

106. Build and Test Grids -
Adoption
Common adoption path

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

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

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

110. Measurement
Function, Performance, Stress, Security

111. Process Density

112. Definition

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

114. Benefits

115. Process Density - Benefits
Reduce host
consumption reduces
cost

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

117. Concerns

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

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

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

121. “Ants not Cattle”

122. Business

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

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

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

126. Tools

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

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

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

130. Adoption

131. Process Density - Adoption
Mostly production
concern

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

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

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

135. Sharing
Faster Features, Fewer Surprises

136. Disposable Development
Environments

137. Definition

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

139. Benefits

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

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

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

143. Concerns

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

145. Business

146. Disposable Development
Environments - Business
Increases feature
velocity

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

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

149. Tools

150. Disposable Development
Environments - Tools
Virtual Box

151. Disposable Development
Environments - Tools
Virtual Box
Vagrant

152. Disposable Development
Environments - Tools
Virtual Box
Vagrant
boot2docker

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

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

155. Adoption

156. Disposable Development
Environments - Adoption
Common adoption path

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

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

159. Food for Thought
Less developed use cases.

160. Food for Thought
Immutable infrastructure

161. Food for Thought
Immutable infrastructure
A/B Deployments

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

163. Future Past
Containers in production are already happening.

164. Future Past
Pantheon/Rackspace
blog: http://goo.gl/
93steF

165. Future Past
Pantheon/Rackspace
blog: http://goo.gl/
93steF
Note the date: October
7th, 2013

166. Future Past
Pantheon/Rackspace
blog: http://goo.gl/
93steF
Note the date: October
7th, 2013
Amazing video
presentation: http://
goo.gl/gRkKGN

167. Future Past
Pantheon/Rackspace blog:
http://goo.gl/93steF
Note the date: October 7th,
2013
Amazing video presentation:
http://goo.gl/gRkKGN
Docker makes this easier to
consider in our own context

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

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

170. Business

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

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

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

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

175. DevOps

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

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

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

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

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

181. Should you be considering a
Docker adoption?

182. 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)