reweave/weave
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
873 Commits 7 Branches 85 Tags
v0.7.0
Commit Graph
873 Commits
This Branch
This Branch
All Branches
Author SHA1 Message Date
Michael Bridgen 8aaf72cbf5 Update changelog for first (0.7.0) release. v0.7.0 2014-12-30 14:36:25 +00:00
Matthias Radestock 2f053161d4 oops 2014-12-30 14:33:48 +00:00
rade c41c6fd8a7 Merge pull request #263 from zettio/versioned_releases 
Machinery for versioned releases
 2014-12-30 13:22:09 +00:00
Michael Bridgen 29f94fd64f Update the example weave status output 2014-12-30 12:50:46 +00:00
Michael Bridgen 82dfe1cc02 Upload the release artefact to a "latest_release" release 
We would like to have a stable URL for the most recently released
script, so that we can mention it in the README and people can use it
in update scripts.

Since GitHub's releases/latest URL redirects, and anyway doesn't work
for downloads, we have to create (possibly delete first) a release
tagged "latest_release" and update it.
 2014-12-29 18:28:02 +00:00
Matthias Radestock 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.

Fixes #300
 2014-12-29 17:27:39 +00:00
rade d7405bf8d5 Merge pull request #304 from viirya/fix_detach 
Support detaching on containers created in container networking mode.
 2014-12-29 15:41:03 +00:00
Liang-Chi Hsieh 961b1eb3de Support detaching on containers created in container networking mode. 2014-12-29 23:14:59 +08:00
Matthias Radestock cca0f5fc79 don't allow lightweight tags after all 2014-12-29 14:27:21 +00:00
Matthias Radestock 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.

Closes #303, #302.
 2014-12-29 14:14:53 +00:00
Matthias Radestock f9593ac571 ignore release dir 2014-12-29 13:51:45 +00:00
Matthias Radestock 50d94529bf accept lightweight tags 2014-12-29 13:49:46 +00:00
Matthias Radestock d31a4ea331 more idiomatic go build time variable setting 
avoiding the use of 'sed'
 2014-12-29 13:27:35 +00:00
Matthias Radestock 7c8586b576 nicer error when there is no version tag 2014-12-29 12:27:42 +00:00
Michael Bridgen ec7dc556ed Factor out ask_version and don't exit 1 if it fails 2014-12-29 12:05:38 +00:00
Michael Bridgen 6c2bef5f88 Missed change of command in usage message 2014-12-29 12:05:38 +00:00
Michael Bridgen 314fff0cff No need for make publish 2014-12-29 12:05:38 +00:00
Matthias Radestock 3e1d96995a cosmetic 2014-12-29 12:01:29 +00:00
Matthias Radestock 7cfb79cfc1 close connection when failing to decrypt packets 
Since we may never recover from that if nonces got out of sync.

Closes #274.
 2014-12-28 19:52:56 +00:00
Matthias Radestock f792bf7ef8 don't log packet on decryption error 
since that is expensive and clutters the logs
 2014-12-28 19:09:41 +00:00
Matthias Radestock 4242a60768 use documented 'docker inspect --format=...' instead of '--format ...' 2014-12-28 00:11:03 +00:00
Matthias Radestock 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

Closes #270.
 2014-12-27 15:14:29 +00:00
Matthias Radestock 73bbb95f7f refactor: move LocalPeer code into separate file 2014-12-25 14:05:41 +00:00
Matthias Radestock f304543ddf refactor: move definition of Peer and related types 2014-12-25 14:02:53 +00:00
Matthias Radestock 7a026f5a14 cosmetic: move a method 2014-12-25 13:57:49 +00:00
Matthias Radestock 5e6bb8ee67 cosmetic: more logical field order 2014-12-25 13:57:31 +00:00
Matthias Radestock 75ed7d52b9 refactor: give Peers knowledge of Ourself.Peer and MacCache 
so their use (when applying updates and performing gc) is opaque
 2014-12-25 13:49:58 +00:00
Matthias Radestock af59b38134 refactor: Peers no longer has dependency on Router 
or ConnectionMaker
 2014-12-25 13:33:45 +00:00
Matthias Radestock 6f990d217d refactor: fewer references to Router 2014-12-25 13:12:42 +00:00
Matthias Radestock 3ba5a5024e refactor: Peer no longer needs Router 
Hooray!
 2014-12-25 13:05:22 +00:00
Matthias Radestock 465915d7d4 refactor: split out LocalPeer 
This has been a source of confusion for a long time.
 2014-12-25 12:57:45 +00:00
Matthias Radestock 059360416a gofmt 2014-12-25 11:27:42 +00:00
rade c367914984 Merge pull request #299 from viirya/fix_doc_link 
Minor fix of document link
 2014-12-25 08:49:20 +00:00
Liang-Chi Hsieh d557f2ff31 Fix document link. 2014-12-25 16:25:19 +08:00
Matthias Radestock da8e9fd0eb refactor: further reduce dependency on router 2014-12-24 20:43:35 +00:00
Matthias Radestock 2d4baa8dba refactor: reduce dependency on peer.Router 
now the only code depending on it is Peer itself
 2014-12-24 20:12:48 +00:00
Matthias Radestock 945a5cf7fe refactor: reduce dependencies of ConnectionMaker 
it doesn't need to know about Router, just Ourself and Peers
 2014-12-24 19:53:11 +00:00
Matthias Radestock 71cd83bf20 refactor: move ConnectionMaker and related types 2014-12-24 19:46:12 +00:00
Matthias Radestock 03b338a252 remove cruft 2014-12-24 19:42:49 +00:00
Matthias Radestock b3be24248e refactor: narrow dependencies of Routes 
it doesn't need to know about the Router, just Ourself and Peers.
 2014-12-24 19:40:18 +00:00
Matthias Radestock 2b2f47c031 refactor: rename PeerCache to Peers 
It was never much of a cache, and that aspect of it is certainly not
its defining characteristic.
 2014-12-24 19:23:43 +00:00
Matthias Radestock 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.
 2014-12-24 19:12:01 +00:00
Matthias Radestock 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).

This does mean the connections' receiveTCP goroutines will take a
direct lock on PeerCache, but a) it is only a read lock, and b) they
already take a write lock in another code path.

There may be some extra load on the PeerCache as a result of this
change, due to the topology fetching of multiple connections no longer
being funneled through the single Topology goroutine. Consequently,
write locks on the PeerCache may take a little longer to
acquire. Until we encounter this as a genuine problem though it's
better to stick with the simpler code.
 2014-12-24 18:34:59 +00:00
Matthias Radestock aa5fc62184 remove cruft 2014-12-24 16:06:31 +00:00
Bryan Boreham 47f4933c92 Merge pull request #295 from rade/eliminate_heartbeater 
LGTM.  Fixes #294
 2014-12-24 13:41:03 +00:00
Matthias Radestock 1c5d720db4 simplify some more 2014-12-24 13:38:17 +00:00
Matthias Radestock fecbf220cc simplify 2014-12-24 13:35:51 +00:00
Matthias Radestock 9cd652ef0b refactor: introduce small helper 2014-12-24 13:29:13 +00:00
Michael Bridgen f842b22eb8 Do better with checking the changelog 
Before, this could fail without a message if there was a changelog but
no matching line.

Also change the changelog format
      == Release v0.0.1
to
      == Release 0.0.1
 2014-12-24 12:44:19 +00:00
Michael Bridgen 8b783af832 Quote all echoings and be consistent about the message prefix 2014-12-24 12:04:53 +00:00