Docker is getting much love & attention these days. Despite that the version 1.0 was released just this spring, pretty much everyone is working on their own version of a system that would allow developers to automate container creation. A combination of CoreOS and Deis seem to be promising, providing a familiar Heroku-style deployment mechanism and eliminating the unnecessary complexity of manual container management. The slides give an overview of the tools mentioned and the benefits one gets by adopting them.

1. Wow! The future is…now!
And how we’re gonna deal with it

2. Why?
• Keep this presentation as a reference for the
company
• Create a vision for you and share mine
• Motivate myself to keep up
• Convince stakeholders
• Buzzwords… yeah, just buzzwords

3. Sources of endless pain
• Bootstrap
• Develop
• Test
• Deploy

4. Sources of endless pain
• Develop
• Bootstrap!
• Test!
• Deploy

7. Thanks to bibstha

8. Thanks to bibstha

9. Thanks to bibstha

10. Thanks to bibstha

11. Docker: ?
• Is a platform to build, run and ship your
applications
• Is a kind of git versioning for software
• How it was in Google back in a day

12. Thanks to bibstha

13. Thanks to bibstha

14. Docker: ??
• Just like the App Store, but open source
• You can pull anything and install it fast
• No approval required
• Anyone can host their private registry

15. Docker: upsides
• Fast startup
• Reproducible environments
• No need to install anything on your dev machine
(except for the docker itself)

16. Docker: downsides
• Some old servers might need an upgrade
• Additional level of complexity
• MacOS incompatibilities
• No way to link containers on multiple machines
(as of September 2014)

17. Typical workflow

18. Create a Dockerfile

20. Then build it…

21. Publish it

22. …and pronto!

23. Showcase time

25. Pretty much every-freaking-one
• Spotify
• Mailgun
• AWS
• Yandex Cocaine
• Digital Ocean
• Create Digital

26. But wait, git introduced
a level of complexity
as well…

27. “…A-a-a-n-d from the business point of view?”
– Our CEO

28. Yay!
• Bootstrap on dev machines
• Test under same conditions
• Stage same containers
• Deploy… yeah, same containers

29. Dockerize all the things!

30. Any way to automate that?

31. IaaS: AWS
• They simply made it right
• However, manual wiring is required

32. PaaS
• Google App Engine
• Heroku

33. 12 Factor
• I. Codebase. One codebase tracked in revision control, many deploys
• II. Dependencies. Explicitly declare and isolate dependencies
• III. Config. Store config in the environment
• IV. Backing Services. Treat backing services as attached resources
• V. Build, release, run. Strictly separate build and run stages
• VI. Processes. Execute the app as one or more stateless processes
• VII. Port binding. Export services via port binding
• VIII. Concurrency. Scale out via the process model
• IX. Disposability. Maximize robustness with fast startup and graceful shutdown
• X. Dev/prod parity. Keep development, staging, and production as similar as possible
• XI. Logs. Treat logs as event streams
• XII. Admin processes. Run admin/management tasks as one-off processes

34. Can I haz a PaaS?
• Sure thing!
• Docker to the rescue

37. CoreOS
• The world's first OS as a Service — patches are
delivered as a continuous stream of updates.
• ChromeOS spin-off
• Every process is dockerized
• Cloud management made simple

38. Awesome dashboard

41. Awesome stuff
• Manage instances. Fleet.
• Service discovery. Etcd.

43. CoreOS: state of things
• Finally stable
• Amazon AMIs, Rackspace
• Bare Metal

45. Much like AWS
But private

46. So what we got
• Docker. Containers and isolation
• CoreOS. Service discovery and container
management

48. Deis

49. Deis
• A PaaS on top of CoreOS
• Heroku-like experience

51. From developer’s POV
• $ git push heroku master
• $ git push deis master

52. Everyone’s freaking happy!

53. Summary
!
Docker + CoreOS + Deis = AWESOME