A Summary about Hykes' Keynote on Dockercon 2015
3 likes1,119 views
The keynote discussed Docker's goals of reinventing the programmer's toolbox through tools like Docker runtime, distribution, composition, machine management, clustering, networking, and extensibility plugins. It also discussed building better infrastructure plumbing through projects like Notary for secure content distribution and runC as a portable container runtime. Finally, it covered promoting open standards through the Open Container Project to define a vendor-neutral container format and ensure support from a broad industry coalition.
A Summary about Hykes' Keynote on Dockercon 2015
- 1. Hykes’ Keynote on Dockercon 2015 Henry Huang
- 2. • 1st step: Done • 2nd step: Done • 3rd step: Great more to come! • 4th and 5th steps: Docker in Production
- 3. Docker in Production • Real community, robust ecosystem • Works for everyone (developers, devops, & ops) • Works for everywhere (multi-arch, multi-os, on & off prem) • Extensible & Pluggable • Solution and roadmap – Security – Orchestration – Network & Storage – Workflows for developing, shipping, deploying/managing • Real users
- 4. PROGRAMMING What is the biggest innovation multiplier today?
- 7. Goal #1 Reinvent the programmer’s toolbox • Building distributed applications is too hard, because the tools are not adequate. • Let’s give programmers a toolbox designed for distributed applications • Take “Incremental Revolution” – Choose one fundamental problem – Solve in the simplest possible way – Repeat
- 8. Problem #1 - Runtime How do I run my code repeatedly on different machines? Docker Container Runtime
- 9. #2 - Packaging & Distribution How do I ship my code across many different machines? Docker Distribution Tools • Docker registry, etc.
- 10. #3 - Service Composition How do I organize my application in scalable services? Docker Compose
- 11. #4 - Machine Management How do I deploy many machines to run my code? Docker Machine
- 12. #5 - Clustering How do I stop worrying about individual machines? Docker Swarm
- 13. #6 - Networking How do I securely connect my containers across machines? Docker Network
- 14. Docker Network • It’s a experimental release: – https://docker.com/experimental • Multiple-host networking out of the box • Micro-segmentation built-in – Assemble virtual networks into any topology, enforce security policies, insert probes and firewalls • Built on industry standards – No need to modify your application – No need to rip out your infrastructure • Standardized service discovery – DNS • 11 community contributed backends – Azure, Calico, Cisco, Consul, Etcd, Midokura, Netflix, NuagentNetworks, VMware, Weave, Zookeeper
- 15. #7 - Extensibility How do I add my own tools to the toolbox? Docker Plugin • Network Plugins • Volume Plugins • Scheduler Plugins • Service Discovery Plugins • More to come…
- 16. Docker Plugin • Dynamic loading – No patches or restarts needed • Multi-tenant – Use different plugins for different applications • No lock-in – If your application works in Docker, it already supports every plugin • Developed with the ecosystem – WeaveWorks, ClusterHQ, Glider Labs, Mesosphere
- 17. Goal #2 Build better plumbing • To build a developer platform, we need infrastructure plumbing – lots of it • Infrastructure plumbers around the World are improving the Internet’s software infrastructure • Take “Principle of Software Plumbing”
- 21. Plumbing for Security • Trusted, cross-platform, content distribution on the Internet is an unsolved problem
- 22. Notary • https://github.com/docker/notary • Platform-agnostic – Distribute any content: source, build artifacts, packages, containers, VM images, documentation… • Built on industry-leading research – Reliable updates – Proof of origin – Resistant to untrusted transport – Survivable key compromise
- 23. Plumbing for OS Containers • Containers are 5% of Docker’s code • It’s just plumbing but it’s popular plumbing
- 24. runC • Just the runtime and nothing else – Battle-tested and production-ready – Support all security features of Linux • Selinux, Apparmor, Cgroups, Seccomp, Cap-drop… – Support user namespaces – Support live migration – Microsoft is contributing Windows support – ARM support underway – Intel is contributing DPDK, Secure enclave – Define a standard, portable runnable format – Usable from the command-line or programmatically
- 26. Goal #3 Promote open standards
- 27. Needs #1 – A formal specification Make it easy for anyone to write their own implementation Open Container Project • A universal intermediary format for OS containers • Supports all hardware architecture and OS
- 28. #2 – Independent Government Don’t tie the standard to a single company Open Container Project In collaboration with “ the Linux Foundation ”
- 29. #3 - A neutral reference implementation The best standards start with rough consensus and working code
- 30. #4 - Support from a broad coalition Your standard must present a majority of the market
- 31. #5 – An open door to fresh ideas Many people have been thinking about this. Hear them out.
- 32. 4 Goals in the Keynote • Reinvent the programmer’s toolbox. • Build better plumbing • Promote open standards • Help organizations solve real- world problems in unique ways