Using Docker with Puppet - James Turnbull, Kickstarter

1. Docker and Puppet
Containerization is the new virtualization

5. What's this all
about?

6. What is Docker?

7. Container
virtualization

8. Build, ship, run

9. Build once.

10. Run in many
places.

11. Isolated, layered,
standard and
content agnostic

12. But this isn't
new?!!?

13. So why should I care?
Software delivery mechanism - a bit like a package!
Put your application in a container, run it anywhere
A bit like a VM but ...

14. Caring
Containers boot faster
Containers have less overhead
Containers bring native performance
Containers are Cloud & VM-compatible

15. Docker Basics
Image & Dockerfile
The Docker Hub
Container

16. Building Docker images
FROM ubuntu
MAINTAINER James Turnbull "james@example.com"
RUN apt-get -qqy update
RUN apt-get install -qqy apache2
ADD index.html /var/www/
ENV APACHE_RUN_USER www-data
ENV APACHE_RUN_GROUP www-data
ENV APACHE_LOG_DIR /var/log/apache2
EXPOSE 80
ENTRYPOINT ["/usr/sbin/apache2"]
CMD ["-D", "FOREGROUND"]

17. Building the image
$ sudo docker build -t="jamtur01/apache2" .

18. Sharing the image
$ sudo docker push jamtur01/apache2

19. Running the container
$ sudo docker run -ti -p 80:80 jamtur01/apache2

20. Docker and
Puppet

21. So does the
Dockerfile solve
all?

22. Well sorta...
It depends.

23. Doesn't have to deal with low-level stuff
Doesn't have to converge
Rebuilds are fast and cached
Allows inheritance and composition
Easy learning curve

24. But...

25. Doesn't deal with low-level stuff
Doesn't define resource dependencies
Doesn't define what runs when

26. Dockerfile
versus
Shell script

27. Shell scripts
Okay for simple stacks
Imperative
Rarely idempotent

28. Dockerfile
versus
Configuration
Management

29. The Good
Handles low-level stuff
Abstracts details
Ensures convergence to a known state
Library of reusable, composable
templates

30. The Bad
Steep learning curve
Generally requires a trigger
Resource-intensive

31. Digging and fixing,
Having so much fun
Working together,
They get the job done

32. Before
Use Puppet to setup hardware,
install packages, deploy code, run
services.
After
Use Puppet to setup hardware,
install Docker, run containers.
Use Dockerfiles to install
packages, deploy code, run
services.

33. Install Docker
with Puppet

34. Should I run
Puppet in my
containers?

35. Nope!

36. Should I use
Puppet to build
my images?

37. Yep!

38. Deploying a
Puppet-powered
container

39. Puppet Apply
FROM ubuntu:14.04
MAINTAINER James Turnbull "james@example.com"
RUN apt-get -qqy update
RUN apt-get -qqy install rubygems
RUN gem install --no-ri --no-rdoc puppet
RUN mkdir /puppet
WORKDIR /puppet
ADD site.pp /puppet/site.pp
RUN puppet apply site.pp

40. Librarian Puppet
FROM ubuntu:14.04
MAINTAINER James Turnbull "james@example.com"
RUN apt-get -y -q install wget git-core rubygems
RUN gem install --no-ri --no-rdoc puppet librarian-puppet
ADD Puppetfile /
RUN librarian-puppet install
RUN puppet apply --modulepath=/modules -e "class { 'nginx': }"
RUN echo "daemon off;" >> /etc/nginx/nginx.conf
EXPOSE 80
CMD ["nginx"]

41. But there's more!

42. What if we could get rid of...
SSHd - Access via nsenter or docker exec
Crond in a container
Logging in a container

43. Creates a new
architecture

44. Separates orthogonal concerns
Don't rebuild your app to change services
Have different policies in domains
Ship lighter apps