Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

DockerCon EU 2015: Docker Networking Deep Dive

with Jana Radhakrishnan, Lead Software Engineer at Docker, and David Tucker, Product Manager, Docker

Docker Networking is a feature of Docker Engine that allows you to create virtual networks and attach containers to them so you can create the network topology that is right for your application. The networked containers can even span multiple hosts, so you don’t have to worry about what host your container lands on. They can seamlessly communicate with each other wherever they are - thus enabling true distributed applications.

And Networking is pluggable, so you can use any third-party networking driver to power your networks without having to make any changes to your application.

Read more: https://blog.docker.com/2015/11/docker-multi-host-networking-ga/


Docker is an open platform for developers and system administrators to build, ship and run distributed applications. With Docker, IT organizations shrink application delivery from months to minutes, frictionlessly move workloads between data centers and the cloud and can achieve up to 20X greater efficiency in their use of computing resources. Inspired by an active community and by transparent, open source innovation, Docker containers have been downloaded more than 700 million times and Docker is used by millions of developers across thousands of the world’s most innovative organizations, including eBay, Baidu, the BBC, Goldman Sachs, Groupon, ING, Yelp, and Spotify. Docker’s rapid adoption has catalyzed an active ecosystem, resulting in more than 180,000 “Dockerized” applications, over 40 Docker-related startups and integration partnerships with AWS, Cloud Foundry, Google, IBM, Microsoft, OpenStack, Rackspace, Red Hat and VMware.

Learn more at www.docker.com

Ähnliche Bücher

Kostenlos mit einer 30-tägigen Testversion von Scribd

Alle anzeigen

Ähnliche Hörbücher

Kostenlos mit einer 30-tägigen Testversion von Scribd

Alle anzeigen
  • Als Erste(r) kommentieren

DockerCon EU 2015: Docker Networking Deep Dive

  1. 1. Docker Networking Deep Dive Dave Tucker Product Manager Jana Radhakrishnan Senior Software Engineer
  2. 2. Agenda What's Next? IPv6 Service Discovery Security Better together Deploying an app using Swarm, Compose and Networking What's in 1.9 Overview Bridge Driver Overlay Driver Default Gateway service Use Cases Microsegmentation Multi-Tenancy Cloud portability
  3. 3. What's in 1.9? Lot's of networking awesomeness
  4. 4. — Moby Dock “Transform networking, like Docker did for compute” 4
  5. 5. 5 • New top-level UX & API: docker network • Multiple micro-segmented networks • Connect containers to multiple networks • Multi-host networking • Pluggable • Network driver plugins • IP Address Management plugins Features available in 1.9
  6. 6. 6 • A Network... • Interconnects a set of containers • Provides isolation for these containers • Every network is backed by a driver • Networks are scoped as Local or Global • Scope is chosen based on negotiated driver scope Networks and Scopes
  7. 7. 7 docker network create mrjana@dev-1:~$ docker network create --help Usage: docker network create [OPTIONS] NETWORK-NAME Creates a new network with a name specified by the user --aux-address=map[] auxiliary ipv4 or ipv6 addresses used by Network driver -d, --driver=bridge Driver to manage the Network --gateway=[] ipv4 or ipv6 Gateway for the master subnet --help=false Print usage --ip-range=[] allocate container ip from a sub-range --ipam-driver=default IP Address Management Driver -o, --opt=map[] set driver specific options --subnet=[] subnet in CIDR format that represents a network segment
  8. 8. Bridge Network Driver 8 C1 Docker0 br-ee40a8236479 Host NIC X Docker Host C2 C3 C4 C5 C6
  9. 9. Multi-host Networking KV Store Docker Host Docker Host Docker Host C1 C2 C3 C4 C5 C6 C7 C8 C9
  10. 10. Overlay Network Driver 10 C1 C2 C3 C5 C4 br0 Veth Veth Veth Host NIC VXLAN Host NIC br0 Veth Veth VXLAN Docker Host 1 Docker Host 2
  11. 11. Overlay Control Plane 11 KV STORE Serf IP Address allocation VXLAN ID allocation (Network, subnet) -> VXLAN ID Populate Neighbor Table entries Populate L2 FDB entries Populate Neighbor Table entries Populate L2 FDB entries Docker Host 1 Docker Host 2
  12. 12. Default gateway service 12 C2 Overlay Network 2 default_gw bridge C1 Overlay Network 1 ICC=false Port Mapping & NAT Happens here
  13. 13. Use Cases How to use Docker's new networking
  14. 14. Use Case: Multi-Tenancy 14 Network "Foo" Network "Bar" C1 C2
  15. 15. Use Case: Microsegmentation 15 Network "frontend" Network "backend" App DB1 DB
  16. 16. Use Case: Cloud Portability 16 Network "ubercloud" aws do
  17. 17. What's Next? More awesome, coming soon
  18. 18. Better IPv6 Support - IPv6 that just works out of the box - IPv6 address allocation - Static public address assignments - Bridge Network and Overlay Network - Support for AAAA record resolution
  19. 19. Service Discovery - DNS based service discovery - Register one or more containers as providing a "service" within a network - Provide DNS records to allow the service to be discovered
  20. 20. Security - Encryption for the Overlay Network - Official "proxy" container for tying networks together - Like in the micro-segmentation use case - "Offline" networks
  21. 21. Better together Deploying an application with networking
  22. 22. — Dave Tucker “Taking Kitematic's Minecraft Demo and turning it up to eleven ” 22
  23. 23. The problem statement - Deploy a Minecraft server - Support multiple worlds, one for each mode of play - Central lobby - Survival world - Creative world
  24. 24. The Application LobbySurvival Creative
  25. 25. Infrastructure Overlay Network
  26. 26. See it in action!
  27. 27. Thank you! Dave Tucker @dave_tucker dt@docker.com Jana Radhakrishnan @mrjana jana@docker.com
  28. 28. Q&A
  29. 29. Backup
  30. 30. Day in the life of packet 30 C1 ARP Request br0 Flood ARP Request Src VXLAN Interface Proxy ARP Response C1 br0 Full IP packet with L2 header Flood IP packet Src VXLAN InterfaceLookup FDB Send VXLAN packet Src Host NICSend on the wire Dst Host NICProcess VXLAN Encap Dst VXLAN Interface Send original IP packet over bridge br0 Flood IP packet C2
  31. 31. Classic three tier application App WebDB Front End Network Back End Network