weave

Despite having been the main maintainer of Weave Net for ~4 years, I have no idea what you are talking about. Weave Net used Google's NaCL library from day 1; later adding optional AES using the in-kernel implementation. https://github.com/weaveworks/weave/blob/master/site/concept...

I'm literally not surprised... https://github.com/weaveworks/weave/issues/3868#issuecomment... And my comment: "Why would someone pay for something that is broken?" If you only prioritize work for paying customers, and don't do things to grow ... you'll eventually die from attrition.

Weave Cloud is the commercial service. It's a management platform for developers creating and operating Kubernetes-based applications. It helps you do CI/CD, observability, monitoring and networking/security[0]. It's across the whole 'developer experience' not just networking. Weave Net is completely OSS and usable to create overlay networks between docker nodes or hosts. There's an extensive user guide [1] and project on Github [2]. You wouldn't need the commercial service for this sort of usage. Business users buy a subscription to get support for complex networking. [0] https://www.weave.works/product/cloud/ [1] https://www.weave.works/docs/net/latest/overview/features/ [2] https://github.com/weaveworks/weave

The issue that I have with the newly imagined Docker Swarm is that it continues Docker's trend of trying to be a jack of all trades. I have no specific examples for Docker Swarm, but using this approach in other areas has led to some pretty major deficiencies in Docker's design that they have been slow to fix, and I'm not keen on seeing that happen again. For a concrete example, see https://github.com/docker/docker/issues/19474 - in a minor release, they completely changed how DNS worked and broke previously working systems (i.e. https://github.com/weaveworks/weave/issues/2157), all in the name of service discovery

I work on Weave Net http://github.com/weaveworks/weave.

Weave (https://github.com/weaveworks/weave) is actually a nice DNS/SDN solution for Docker. Quick and easy to set up.

It's terribly slow unless you don't care about encryption: https://github.com/weaveworks/weave/issues/1925 The per-packet processing overhead is a real and unresolved problem. I'm using Rancher's networking now instead. It uses ipsec between hosts, so everything gets handled by code paths which have been optimized in the kernel, and performance is good (especially if you have a not-ancient CPU and have the AES-NI instruction - then wirespeed gigabit works with acceptable overhead). I like Weave's decentralized architecture and wish it were realistic to use it. If they are going to stick with a user-space solution they probably need to use DPDK or one of the other high-performance software defined networking toolkits, which tend to process packets using a SIMD approach.

For now, yes. https://github.com/weaveworks/weave/issues/1925 https://github.com/weaveworks/weave/issues/1931 The developers are friendly, helpful and responsive. But in my testing, Weave simply wasn't adequate. I hope they'll get there.

Weaveworker here: I'd love to know what you mean by "over-complicate". It can be as simple as `docker run --net=weave ...`. We have a PR open that would let you connect Docker's bridge to Weave Net - https://github.com/weaveworks/weave/pull/1955

http://github.com/weaveworks/weave enables multicast between containers (and many other things besides).

> high barrier of entry for multi-node deployments and isolated networks Have you tried Weave? [1] It gives you an isolated multi-node network for your containers. I'd be interested to know if you still think it has a high barrier of entry. Disclosure: I work on Weave. [1] https://github.com/zettio/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...