Docker AWS TechCONNECT Boston, 28-July-2015
•Descargar como ODP, PDF•
2 recomendaciones•586 vistas
Presentation I gave about Docker and its ecosystem at Amazon Web Services TechCONNECT in Boston on July 28,2015
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (18)
Destacado
Destacado (12)
Similar a Docker AWS TechCONNECT Boston, 28-July-2015
Similar a Docker AWS TechCONNECT Boston, 28-July-2015 (20)
Último
Último (20)
Docker AWS TechCONNECT Boston, 28-July-2015
- 1. Our mission is to build tools of mass innovation
- 3. Incredible new technology Billions of creative people
- 4. Incredible new technology Billions of creative people
- 5. Incredible new technology Billions of creative people
- 6. Incredible new technology Billions of creative people Mass innovation
- 7. What is the biggest innovation multiplier today?
- 8. What is the biggest innovation multiplier today? Programming.
- 9. New hardware can do incredible things Millions of programmers Mass innovation Make it programmable
- 10. What new hardware could do incredible things if made programmable?
- 11. THE INTERNET Millions of programmers Mass innovation Make it programmable
- 12. Internet Servers Desktops Phones Cars Houses Drones Network equipment Public transit TVs Industrial facilities Scientific instruments Financial system
- 13. Internet Servers Desktops Phones Cars Houses Drones Network equipment Public transit TVs Industrial facilities Scientific instruments Financial system Programmers Must program!!!!
- 14. Internet Servers Desktops Phones Cars Houses Drones Network equipment Public transit TVs Industrial facilities Scientific instruments Financial system Androi d iOS AWS Raspberry pi Cloudfoundr y Openstack Microsoft Web Heroku ... App App App App App App App App App App App App App App App App App Programmers
- 15. Internet (hardware layer) Servers Desktops Phones Cars Houses Drones Network equipment Public transit TVs Industrial facilities Scientific instruments Financial system Programmers Internet (software layer) App App App App App App App App App App App App App App App App App App App App App App App App App App App App
- 16. Internet (hardware layer) Servers Desktops Phones Cars Houses Drones Network equipment Public transit TVs Industrial facilities Scientific instrumen ts Financial system Programmers App App App App App App App App App App App App App App App App App App App App App App App App App App App App a software layer to program the internet
- 17. Docker in the Cloud Market
- 19. History of containerization • 1960’s mainframe • 1990’s hardware virtualization • 1990’s OS virt precursors: BSD Jails, Solaris zones • 2006 Cloud IaaS • 2009 platform virtualization (PaaS) • 2013 Docker See @bcantrill’s deck http://www.slideshare.net/bcantrill/docker-and-the-future-of-containers-in-production
- 20. 7
- 22. Why Docker success now? • Cloud adoption • Portability • Hybrid • Devops
- 25. RancherOS
- 26. Docker
- 27. Isolation using Linux kernel features namespaces pid mnt net uts ipc user cgroups memory cpu blkio devices
- 28. Image layers
- 29. Docker now
- 31. docker-compose: running multiple containers Run your stack with one command: docker-compose up Describe your stack with one file: docker-compose.yml web: build: . command: python app.py ports: - "5000:5000" volumes: - .:/code links: - redis:redis redis: image: redis
- 32. What’s new in 1.3.0? Performance and stability improvements Lots more config option support New feature (experimental!): Smart Recreate Only recreate containers whose configuration has been changed $ docker-compose up --x-smart-recreate Will eventually be the default behaviour
- 33. docker-machine docker-machine create -d azure —azure-subscription-id="c4f51be3-784c-xxx-7c50ad9e1b7c" --azure-subscription-cert="/Users/pat/.ssh/docker-azure- cert.pem" --azure-location="East US" --azure-size=Small --azure-username="pat" pat-docker-machine-n
- 35. What is new in 0.3.0? Generic Driver -Provision any host with SSH Engine and Swarm Options -Specify any swarm or engine option Swarm Provisioning out of experimental Custom Engine and Swarm Versions -Specify stable/test for engine -Specify image for Swarm
- 36. Docker Hub
- 37. 150,000 repos 500+ million pulls 240,000 users 3/23/13 7/15/13 11/4/13 2/24/14 6/16/14 10/6/14 1/26/15 5/18/15 - 75,000 150,000 225,000 300,000 4/29/13 8/19/13 12/9/13 3/31/14 7/21/1411/10/14 3/2/15 - 40,000 80,000 120,000 160,000 5/6/13 8/5/1311/4/132/3/14 5/5/14 8/4/1411/3/142/2/15 5/4/15 - 125,000,000 250,000,000 375,000,000 500,000,000 2014 2015 2014 2015 2014 2015
- 39. Docker Hub Dev & QA ColleaguesDevelopers QA Build & Ship
- 40. Docker Hub Faster Pulls 60% Less Bandwidth v1 v2 0% 25% 50% 75% 100% v1 v2 0% 25% 50% 75% 100% 80% Fewer Requests
- 41. Docker Hub Dashboard: 2.0x Speedup Search: 1.6x Speedup Current New 0 3,000 6,000 9,000 12,000 Current New 0 2,250 4,500 6,750 9,000
- 44. On-premise registry server LDAP/Active Directory integration Role-based access control Audit & events logging Easy deploy, upgrade, & rollback
- 46. Kitematic
- 48. It’s all about Devops
- 49. 28 Dev / Ops
- 50. Separation of concerns: Sylvester the Developer Inside my container: − my code − my libraries − my package manager − my app − my data
- 51. Separation of concerns: Robert the Ops guy Outside the container: − logging − remote access − network configuration − monitoring
- 52. Networking
- 61. M 1 M 2 M 3 C 2 C 1 C 3 C 4 C 6 C 5 Network 1 Network 2
- 64. Plugins
- 65. Docker Plugins Developed with the community. Mesosphere, WeaveWorks, ClusterHQ, Glider Labs,… 4 new extension points: Networking Service discovery Storage volumes Scheduling More extension points coming soon.
- 66. Docker Plugins Batteries included but removable: default implementation is a plugin too! Dynamically loaded: extend Docker without patching or restarting it Multi-tenant: different apps can use different plugins No lock-in: if your application works in Docker, it already supports every plugin.
- 67. Swarm Scheduler pluginsScheduler plugins Engine Volumes pluginsVolumes plugins Network pluginsNetwork plugins Service discovery plugins Service discovery plugins Engine Volumes pluginsVolumes plugins Network pluginsNetwork plugins Service discovery plugins Service discovery plugins mesos flockerglusterfs weavecalico consuletcdzookeeper midokuraciscoazurenuagenetworks
- 68. Weave
- 69. Flocker
- 70. Orchestration
- 71. Docker Swarm
- 76. Swarm beta integrations Fully integrated with Machine Partially integrated with Compose Mesos integration has started in collaboration with Mesosphere.
- 77. Swarm load balancing: interlock https://github.com/ehazlett/interlock/tree/master/plugins/haproxy
- 78. New in Swarm
- 85. Orchestration summary • Docker Swarm: Docker-style, provision with docker- machine • Mesos: Twitter-style, aligned with Swarm • Fleet: CoreOS-style, simple • Kubernetes: Google-style, heavy-duty, many concepts • AWS EC2 Container Service: simple, aligned with Swarm • Cloud Foundry Diego, IBM BlueMix: PaaS -> orchestration • Also: Joyent, Tutum, Flynn
- 86. Plumbing
- 87. The Docker toolbox is built on plumbing. Lots of it. Linux LXC selinux apparmor aufs lvm zfs btrfs virtualbox iptables openssl tar git raft serf xenkvm openvz paxos ssh Go
- 88. The Docker community created its own plumbing... Lots of it. 50% of Docker’s source code is plumbing.
- 89. Service discovery networking os containers authentication storage logging build content distribution code signature master election code signatureload balancing scheduling testing code review The Docker community created its own plumbing... Lots of it.
- 90. Thou shalt... 1. re-use and improve existing plumbing 2. make new plumbing easy to re-use and improve 3. Follow the unix principles: make small simple tools, not big complicated ones 4. define standard interfaces for assembling larger systems The principles of software plumbing
- 91. Docker is spinning out its plumbing All of it.
- 92. We need your help!
- 94. Secure content distribution on the Internet is an unsolved problem.
- 95. Introducing Notary “Let’s stop using curl|sh” Trusted collections for any content Transport-agnostic Reliable updates, proof of origin, resistant to untrusted transport, survivable key compromise Build on industry-leading standards and research
- 97. It’s just plumbing... but it’s popular plumbing! Containers are 5% of Docker’s code
- 98. Introducing RunC The universal container runtime All of Docker’s container management plumbing and nothing else Super lightweight Battle-tested and production-ready Supports all security features of Linux: selinux, apparmor, cgroups, seccomp, namespaces, cap-drop.. Supports user namespaces Supports live migration Microsof is contributing Windows support Arm support underway Intel is contributing DPDK, Secure enclave Defines a standard, portable runnable format Usable from the command-line https://runc.io
- 100. Open Standards
- 101. “You are the de facto standard. Make it a proper standard!”
- 103. (logo slide)
- 104. Fire up your first container today! Ride the Whale!
- 105. Learning • http://docs.docker.com/ • http://slideshare.net/chanezon • https://github.com/chanezon/azure-linux
- 107. Q&A
Notas del editor
- Docker Hub is Docker’s cloud service for … Publishing and discovering container images through the public registry Team collaboration and automation of application workflows
- However you look at it, the growth has been extraordinary. Almost a quarter million users … … who have created or are collaborating on 150,000 repositories … … X% of which are publicly available … … serving more than Y TB of Docker container images … There are millions of consumers of these repos, and altogether they have pulled them more than 500 million times … … using Z TB of bandwidth.
- … also launched at DockerCon last June, the Docker Hub Official Repos program has grown to almost 80 Official Repos. These curated images are actively maintained by the upstream owners or by Docker … … and have proven to be some of the most popular repositories on Docker Hub …
- Many of you are probably aware of our open source Registry v2 efforts, which shipped in April. The Registry v2 team has been working hard with the Docker Hub team to transition the Docker Hub Registry to Registry v2. New CDN optimization The results have been simply outstanding. First … the new Docker Hub is FASTER. This is a result of the v2 protocol being dramatically more efficient than v1, requiring 80% fewer requests and 60% less bandwidth to accomplish the same pull. FEWER REQUESTS parallel pulls of multiple layers fewer requests, and the requests that are being done are done in parallel LESS BANDWIDTH less bandwidth required due to better caching (better cacheability) and sharing across images
- Third … thanks to completely re-built backend and frontend stacks, Docker Hub has a much more responsive user experience. The user’s Dashboard is … The search results is …
- Second … the new Docker Hub is more reliable than previously. This is the result of improved reliability of the Registry v2 protocol. Specifically, Docker Hub Registry v2 has an authentication stack independent of other Hub services. This gives push / pull operations improved availability. User benefit: less interruptions of pulls … and Docker uses Docker Hub Why more reliable? Fewer requests Web transaction is a simpler protocol and thus less error-prone
- … with features critical for on-premise deployments If you’re an OSS registry user … EASY install, update, rollback
- … and to make all this easy to configure and manage, Docker Trusted Registry also features a web-based admin GUI … for insights into the state of the DTR host …