da3d343f26
tidying: remove 'publish' targer from .PHONY we forgot to do that when removing the target itsel
Matthias Radestock2015-01-02 16:27:37 +00:00
618de144d9
update changelog entry for 0.7.0 to point out new download locations
Matthias Radestock2015-01-02 15:43:34 +00:00
82b54aabcd
Move logging, updating and testing utils into common directory
Bryan Boreham2014-12-24 12:00:30 +00:00
7b6ea37fea
wire in weavetools image build We use a plain ubuntu container as a build environment for ethtool & conntrack, so a) we don't require onerous tooling on the build host, and b) don't pollute the build host with build artefacts. The latter arise because I can only get conntrack to build by installing its dependencies 'globally'.
Matthias Radestock2015-01-01 00:57:02 +00:00
5da2219dc8
cosmetic: remove weaver/.gitignore and handle that in the top-level .gitignore instead. Just as we do for weavedns.
Matthias Radestock2015-01-01 00:49:34 +00:00
57856a5584
align script and image versions - released weave scripts run their corresponding image versions - unreleased weave scripts run the 'latest'-tagged image versions
Matthias Radestock2014-12-30 16:20:00 +00:00
d3002384d7
Also push the :latest tags to Dockerhub when publishing
Michael Bridgen2014-12-30 16:01:10 +00:00
82dfe1cc02
Upload the release artefact to a "latest_release" release
Michael Bridgen2014-12-29 16:42:41 +00:00
a0ec8c4daa
correctly check whether weavedns is running and return an error status rather than exit when containers stop just before an HTTP call, which in turn allows us to make tell_dns properly ignore weavedns container absences.
Matthias Radestock2014-12-29 17:27:39 +00:00
d7405bf8d5
Merge pull request #304 from viirya/fix_detach
rade2014-12-29 15:41:03 +00:00
961b1eb3de
Support detaching on containers created in container networking mode.
Liang-Chi Hsieh2014-12-29 23:14:59 +08:00
70eea06de0
more precise detection of weave-attached-ness Rather than looking for the host end of the veth pair, we look for the expected interface inside the container. This has the advantage of detecting weave-attached-ness even when the container is sharing a network namespace with others.
Matthias Radestock2014-12-29 14:14:53 +00:00
7cfb79cfc1
close connection when failing to decrypt packets Since we may never recover from that if nonces got out of sync.
Matthias Radestock2014-12-28 19:52:56 +00:00
f792bf7ef8
don't log packet on decryption error since that is expensive and clutters the logs
Matthias Radestock2014-12-28 19:09:41 +00:00
4242a60768
use documented 'docker inspect --format=...' instead of '--format ...'
Matthias Radestock2014-12-28 00:11:03 +00:00
f3faf83321
refuse to attach containers running in the host network namespace Since bad things happen otherwise, i.e. we end up creating veth pairs with an ethwe on the host
Matthias Radestock2014-12-27 15:14:29 +00:00
75ed7d52b9
refactor: give Peers knowledge of Ourself.Peer and MacCache so their use (when applying updates and performing gc) is opaque
Matthias Radestock2014-12-25 13:49:58 +00:00
af59b38134
refactor: Peers no longer has dependency on Router or ConnectionMaker
Matthias Radestock2014-12-25 13:33:45 +00:00
2d4baa8dba
refactor: reduce dependency on peer.Router now the only code depending on it is Peer itself
Matthias Radestock2014-12-24 20:12:48 +00:00
945a5cf7fe
refactor: reduce dependencies of ConnectionMaker it doesn't need to know about Router, just Ourself and Peers
Matthias Radestock2014-12-24 19:53:11 +00:00
b3be24248e
refactor: narrow dependencies of Routes it doesn't need to know about the Router, just Ourself and Peers.
Matthias Radestock2014-12-24 19:40:18 +00:00
2b2f47c031
refactor: rename PeerCache to Peers It was never much of a cache, and that aspect of it is certainly not its defining characteristic.
Matthias Radestock2014-12-24 19:23:43 +00:00
e8f836ad85
refactor: rename 'Topology' to 'Routes' Since that is what it is. By contrast, when the docs talk about topology they actually refer to the peer connectivity graph.
Matthias Radestock2014-12-24 19:12:01 +00:00
fc1ec6ada2
refactor: go straight to PeerCache for fetching topology There is no need to go via Topology. Fetching does not access or modify the Topology state, and none of the functions on Topology update the PeerCache. So there is no point serialising the fetching with RebuildRoutes (or anything else).
Matthias Radestock2014-12-24 18:34:59 +00:00
5ccc753367
kill stale connections The weave protocol already effectively performs heartbeating - FetchAll is performed at regular intervals. Hence we can detect stale connections by the lack of receiving any data for approximately that interval (we use x2).
Matthias Radestock2014-12-24 10:33:37 +00:00
Ilya Dmitrichenko