weavenetwork

6 ms·

31.
by weavenetwork 12y ago
we are hiring ;-)
32.
by weavenetwork 12y ago
@wmf, with respect, it's not garbage and actually works well for many cases. At the same time, it is quite possible to see ways to integrate weave with kernel features! We welcome your input and help on that -- why not get in touch?
33.
by weavenetwork 12y ago
Weave is also topology agnostic - see the explanation vs Flannel (formerly "Rudder") here http://www.infoworld.com/article/2608941/application-virtual...
34.
WeaveDNS – A distributed DNS service for a weave network(weaveblog.com)
43 points by weavenetwork 12y ago|15 comments
35.
by weavenetwork 12y ago
I think VPN is a use case for SDN. Weave is fundamentally a software network that provides a virtual switch at layer 2.
36.
by weavenetwork 12y ago
The most significant conceptual difference is that in rudder sub-nets are tied to hosts. So containers on different hosts will always be on different sub-nets. By contrast, in weave containers belonging to the same application reside in the
37.
by weavenetwork 12y ago
We are certainly aware of consul, and have indeed been thinking of weaving weave into it. Would love to see an experiment along those lines, if there are any volunteers.
38.
by weavenetwork 12y ago
> 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 beginnin
39.
by weavenetwork 12y ago
Weave itself does not provide addressability beyond IP. That is the situation now, but this area is very much high on the agenda for us - service discovery is definitely in scope for weave. Meanwhile, two points of note: 1) In weave the I
40.
by weavenetwork 12y ago
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
41.
by weavenetwork 12y ago
TCP and UDP is all you need. (And the UDP can actually be quite broken, just not completely) We've created weave networks spanning hosts on EC2, GCE and local data centres.
42.
by weavenetwork 12y ago
Just having a look at Tinc.. one difference is completely non-technical - Tinc is GPL but Weave is Apache licensed so aligns better with the whole Docker ecosystem. More comments to come.
43.
by weavenetwork 12y ago
It is definitely changing fast, but that is not a reason to wait before trying out the technology in order to learn about it. If nothing else, the community will welcome your feedback :-)