This document discusses configuration management in a containerized world. It provides an overview of Docker's success due to instant productivity, development resembling shipping, and portable artifacts. It then outlines the build, test, ship, and run phases for container management and discusses using tools like Chef to build containers from cookbooks. Lastly, it touches on fleet management across machines using tags and recipes to deploy MySQL and WordPress containers.

1. Configuration Management in a
Containerized World
Julian Dunn
Product Manager
Chef Software, Inc.
February 2015

9. Top 3 Reasons for Docker's Success
1. Instant productivity
2. Developing is like shipping
3. Portable artifact

13. Build Test Ship Run

16. Build
FROM msdos:6.1
LOAD HIMEM.SYS
LOADHIGH EMM386.EXE
ENTRYPOINT AUTOEXEC.BAT
$ knife container docker build ...
• Open-source plugin to Chef's "knife"
• Use existing cookbooks to build containers
• https://github.com/chef/knife-container

17. Test
control_group "shellshock" do
control "ensure bash is a new enough version" do
expect(package('bash')).to be_installed.and at_version('> 4.1.2-25.el6.x86_64')
end
control "try to exploit shellshock" do
let(:cmd) { %q{env x='() { :;}; echo vulnerable' bash -c "echo test" }}
expect(shell_out(cmd).exitstatus)).to not_equal(1)
end
end

18. Ship
• Docker registry
• Kubernetes? Mesos?
• AWS CodeDeploy/Container Service?
• Other?

19. Run
• Per-container monitoring, metrics, inventory
• Resource allocation ("scheduling")
• Service discovery
• Controlled mutability

20. Fleet Management: Crossing the Machine Boundary
machine 'mysql_wordpress' do
recipe 'mysql'
recipe 'wordpress::database'
tag 'mysql_master'
end
num_webservers = 5
1.upto(num_webservers) do |i|
machine "wordpress#{i}" do
recipe 'apache'
recipe 'wordpress'
end
end

31. Thanks!
jdunn@chef.io
julian_dunn
juliandunn