weave

Great work! I was exploring the distributed docker networking space yesterday for an open source project I'm working on (https://github.com/pnegahdar/sporedock) and the ones I have currently found are: Weave - https://github.com/zettio/weave Ambassadord - https://github.com/progrium/ambassadord Warmhole - https://github.com/vishvananda/wormhole QTunnel (not docker specific) - https://github.com/getqujing/qtunnel Flannel - https://github.com/coreos/flannel I'd love a comparison write up if you guys ever get to it.

Pretty cool demonstration of Weave[1]. Is it correct to summarize Weave as "Hamachi for Docker containers"? For those that don't remember Hamachi, perhaps "VPN for Docker containers" is a more contemporary technical description. [1] https://github.com/zettio/weave EDIT: I know this was just a proof-of-concept, but I believe if one were to bring up a multi-datacenter Cassandra ring, you'll want to ensure your replication configuration is "NetworkTopologyStrategy" and not the default "SimpleStrategy" setting[2]. [2] http://www.datastax.com/documentation/cassandra/2.0/cassandr...

> complex tricks with the existing network stack To retain the essence of how weave operates, this would likely not just be complex but impossible, short of kernel hackery. > you would really only need to do processing at the beginning of a connection and for some ARP request Weave needs to look at every Ethernet packet. Well, the headers at least. It's a virtual Ethernet switch. It doesn't even really know about IP, let alone TCP streams. See https://github.com/zettio/weave#how-does-it-work

re benchmarks...publishing some is on the TODO list. See https://github.com/zettio/weave/issues/37. Informally, weave is pretty fast but it's not saturating Gbit Ethernet. As you say, capturing with pcap and handling packets in user space carries an appreciable overhead. We've got some issues filed to look at pcap alternatives and also generally aim to improve performance. re suitability for NoSQL clustering... depends on where the bottlenecks are; if you want to cluster for HA rather than scale, i.e. there aren't any real bottlenecks, then weave will work well. Same if you want to cluster because of CPU or memory bottlenecks. If, otoh, networking is the bottleneck then adding weave into the mix isn't going to improve matters.