This document discusses Docker containers and orchestration tools like Kubernetes, Mesos, and Marathon. It summarizes setting up Docker containers on Kubernetes and other orchestration platforms, the challenges of service discovery and load balancing, and difficulties experienced in setting up Kubernetes in a development environment. Overall it provides an overview of Docker and various orchestration tools while recounting lessons learned from a hands-on setup.

1. Docker on Kubernetes

2. Thank you
@planet for the snacks
22seven for the venue
Blue Battleship for the drinks
(^^^ shameless self promotion)

3. Actually
Docker on Kubernetes
on Mesos via Marathon
in VirtualBox via Vagrant
Provisioned with Chef

4. Relax and listen
All the code and commands will
be available online after the talk

6. What is Docker?
According to Google:
person employed in a port to load and unload ships.

7. Docker containers wrap up a piece of software in a
complete filesystem that contains everything it needs
to run: code, runtime, system tools, system libraries
– anything you can install on a server. This
guarantees that it will always run the same,
regardless of the environment it is running in.

9. Why is this important?
Creates a standard way to ship build artifacts
Ships the exact binary the developer had

10. <Stock photo for docker presentation>

11. So you have containers
Now what?
Let’s deploy!

12. Where do you host them?
Docker Hub (public, security)
AWS ECR
Private Docker registry

13. How do you deploy?
Command line

14. High hardware utilization
Idling systems wastes money

15. Ok, so let’s spin up more
Use each server for multiple services
Forward the ports to the same on host
Put a loadbalancer in front
Pat back, just scaled horizontally

16. Issues
How do the nodes in a service discover other ones
to allow them to cluster?

17. Chef!
(My new koolaid driven tool)
Ansible is also cool, ask Tom

20. Erm, riiiiiiight
I’ve heard Mesos/Marathon can help with that

21. Are we there yet?
I thought this talk was about Kubernetes

22. Kubernetes
Good for spinning up pods
Registering services
Etcd event -> Update DNS

23. Pods
Collection of Docker images that work together
nginx + memcached
Independent, no shared state
Port inside container is mapped to host port

24. Pods
Mortal, when they die, they are gone
Sounds like something should watch them

26. Replication controller
Monitors the pods
Spins up or kills pods depending
on replication count required
Should be used for single pods

27. Pods
If the run on some host somewhere,
how do we find them?

28. Services
Higher level abstraction
Website doesn’t care which instance,
just looking for image processing service
Has a port to pod port mapping

30. Port mapping
Service registers with Etcd -> DNS
Service port -> Pod port -> Container port
Starting to get complicated
myservice.etcd.local

31. Mesos / Marathon
Good with scheduling tasks on nodes
Monitors and restarts processes
Assigns random ports to containers
Allows resource constraints

32. Consul + nginx
Consul raises events when service is registerd
Consul-template -> generate nginx config
Load balance 2x nginx for *.mydomain.com

33. Mesos + Kubernetes
Easy, right?

37. What now?
Vagrant + Virtualbox
Chef them
Sounds do-able

38. Vagrant
Spin up 3 Ubuntu machines
Provision with Chef

39. Eth0 vs Eth1
Chef Ohai reads eth0
Needs to be eth1
Vagrant Ohai plugin!
Then it broke

40. Zookeeper
Mesos
Marathon
Not too much pain

41. Kubernetes
Lot’s of pain
Build from source
Build from source using Docker image
Download binary

42. Kubernetes
Specifically didn’t choose to do single master
example, you wouldn’t run it like this in
production

43. Kubernetes
Watch Kelsey Hightower’s youtubes

44. Kubernetes
Really not so easy to set up as HA

45. Thank you
@planet for the snacks
22seven for the venue
Blue Battleship for the drinks
(^^^ shameless self promotion)