Multi host container networking
Download as PPTX, PDF1 like463 views
This document outlines a multi-host container networking solution called Weaveworks. It describes Weave as an overlay container network that allows containers running on different VMs or hosts to communicate. The document demonstrates Weave by showing a data producer container sending messages to an "HTTP" server container running on different hosts and connected through the Weave network. It also briefly describes Weave Run for IPAM, load balancing and service discovery and Weave Scope for visualizing containers.
Multi host container networking
- 1. Multi-host Container Networking Alfonso Acosta Software Engineer at Weaveworks
- 3. Outline 1.Problem statement 2.What's Weave? 3.VM<->VM Demo 4.Weave+ECS Demo
- 4. Problem statement ? ? ? ? ?
- 6. What's Weaveworks Founded in 2014 Goals: connect, observe and control containers simple to use developer friendly Weave passes Mårten Mickos' 15 min test - Adrian Cockroft
- 7. Not only a SDN Weave Net: Overlay container network
- 8. Not only a SDN Weave Run: IPAM, LB, SD (weaveDNS) ...
- 9. Not only a SDN Weave Scope: Container visualization
- 10. Weave Demo
- 11. Data producer while true; do # Get IP IP=`hostname -i | awk '{ print $1 }'` # Offer data on port 4540 echo "Hi, this is the data producer in $IP" | nc - q 0 -l -p 4540 done
- 12. "HTTP" Server while true; do # Get a message from a data producer DATA_PRODUCER_MESSAGE=`nc dataproducer 4540` # Render message HTML="… <h1>Chosen data producer message:</h1> <h2>${DATA_PRODUCER_MESSAGE}</h2> … " echo "$HTML" | nc -q 0 -l -p 80 done
- 13. Weave+ECS Demo
Editor's Notes
- #2: Introduce yourself
- #3: Survey: ask the audience who has used … 1. Docker, 2. Weave, 3. ECS.
- #7: Insist on the fact that we are developer oriented, there are other solutions out there but they are not that developer-friendly
- #8: Cloud agnostic (bare metal support), Open source,supports network topologies which are not fully connected
- #9: Talk about weaveDNS (container name -> A record, Random A-record order, Gossip) how it scales better than Consul (agent->master, starts to bottleneck on 250 nodes and requries DNSmask/caching)