At OPEN'15, Bastiaan Schaap (Docker trainer @ Amazic), gave a presentation about the difference between pets and cattle and how this relates to the Docker philosophy.

1. Herding your cattlefromdev to ops

2. Herding… wut?!
from http://gmccance.net/

3. Why should
you ?care

4. Dev to Ops the old way..

5. Dev to Ops the new way!

6. “
”
It’s pretty much the best thing for
cloud computing
since the movement from bare metal
to virtual machines
HoMingLi(DockerCon2014attendant)

7. “
”
Docker aims to reduce the cycle time
between
code being written
and code being tested, deployed, and
used.
JamesTurnbull(authorofTheDockerBook)

8. “
”
Docker is one of those technologies that,
without any great fuss and without anyone
noticing, is now everywhere. […]
I wouldn’t call Docker a“Swiss Army Knife”
— it has so many more uses than that.
DrMikeNorman(CloudServicesArchitect@JPMorgan)

10. #whoami
• DevOps engineer
• Linux, middleware & cloud
technologies
• 18+ yrs IT experience
• Docker trainer @ Amazic

11. DevOps means giving a shit about your job
enough
to want to learn all the parts
and not just your little world.
JohnE.Vincent(blog.lusis.org)
“
”

12. 10,000 feet
WAY UP

16. The real value of Docker is not technology,
it’s getting people to agree on something.
SolomonHykes(FounderofDocker)
“
”

20. Linux Containers
NEXT UP

21. Almost everything in Google
runs in a container.
BrianDorsey(GoogleCloud)
“
”

22. What is Container Virtualisation?
• Alternative to“traditional”virtualisation on Hypervisors such asVMWare
• No guest operating system (or booting) required for containers
• Virtualisation layer runs as an application inside the host OS
• Sandboxed execution environment
• Lightweight, high performance (especially on bare metal hardware)

24. Where does Docker fit in?
• Built on top of Linux container technology (LXC, AUFS)
• Provides tools to build, run, share and version“images”
• Handles communication between running“containers”(network, fs)
• Docker containers run practically everywhere
• Extremely reproducible; you could start from scratch every time!

25. Docker containers

26. Images versus Containers
• Docker images consist of one or more read-only layered file-systems
• The bottom layer is called the base image (Linux kernel, e.g. Red Hat)
• A Dockerfile is the equivalent of a build file to create an image
• Docker containers are the running, stateful instances of images
• Modified containers can also be committed back to images

28. Docker build demo
NEXT UP

29. FROM jboss/wildfly
MAINTAINER Bastiaan Schaap <http://github.com/siteminds>
RUN /opt/jboss/wildfly/bin/add-user.sh --silent admin admin
ADD sample.war /opt/jboss/wildfly/standalone/deployments/
EXPOSE 8080
EXPOSE 9990
Sample Dockerfile

31. Conclusion
FINALLY..

32. Pros
• Standardized way of getting code from development to production
• Easy to use DevOps workflow
• Fast container startup
• Isolation of processes and their configuration

33. Cons
• Very easy to do, can be very hard to do right
• Networking can be difficult
• Ecosystem evolving (rapidly)
• Which orchestration tools/platforms/frameworks to use

35. Questions?
THANK YOU

36. @bjwschaap
bastiaan@amazic.com