Matthias Radestock
cf08b8b1aa
cosmetic: tweak --observer usage text
2016-03-21 12:02:22 +00:00
Matthias Radestock
0b3dd35624
cosmetic
2016-03-21 11:08:17 +00:00
Matthias Radestock
357d0e918a
Merge pull request #2000 from weaveworks/issues/1998-specify-ipam-seed
...
Allow specification of initial IPAM ring via --ipam-seed
Fixes #1998 .
2016-03-21 10:52:40 +00:00
Adam Harrison
3123418022
Merge pull request #2030 from weaveworks/issues/1992-cni-plugin
...
Implement CNI plugin
2016-03-21 10:51:19 +00:00
Adam Harrison
e9081c6607
Allow specification of initial IPAM ring via --ipam-seed
2016-03-21 09:49:54 +00:00
Matthias Radestock
6ebac90cb0
refactor: eliminate dot imports in main packages
2016-03-20 14:34:27 +00:00
Adam Harrison
f9f6e8ed26
Protect container-addrs against stopped containers
2016-03-18 10:46:30 +00:00
Bryan Boreham
b153e6a0d2
Simplify, after review feedback
2016-03-17 14:29:34 +00:00
Bryan Boreham
024eb46c7d
CNI plugin implemented as script that docker runs plugin container,
...
installed via `weave setup`
2016-03-17 14:29:33 +00:00
Bryan Boreham
42ff61f97c
CNI net plugin
2016-03-17 12:41:14 +00:00
Bryan Boreham
f9615c34dc
CNI IPAM plugin
2016-03-17 12:41:14 +00:00
Matthias Radestock
86bfc91ac9
refactor: clearer IPAM config
2016-03-15 10:29:32 +00:00
Adam Harrison
2eeb754454
refactor: Introduce IPAM config object
2016-03-14 17:41:20 +00:00
Bryan Boreham
f2e38ae6c5
Abstract out logging function from weave api package to reduce dependencies
2016-03-07 15:37:51 +00:00
Adam Harrison
b84ef98de8
Support non-electing peers via --observer
2016-03-03 17:48:50 +00:00
Bryan Boreham
604309fb53
Parse CIDR strings without separating into subnet and address
2016-03-02 17:21:52 -08:00
Bryan Boreham
95cbc8940e
Sync 'owned' data with existing containers at startup
2016-03-02 11:35:24 -08:00
Adam Harrison
adf56d316d
Remove obsolete alternative procfs support
2016-03-01 20:10:47 +00:00
Adam Harrison
71af1f3120
Merge pull request #1972 from weaveworks/persist-peers
...
Persist set of peers to connect to
2016-02-29 15:54:54 +00:00
Tom Wilkie
6ff7419981
Review feedback
2016-02-26 15:35:12 +00:00
Tom Wilkie
b228bbb9fb
Periocially check for up to date versions of weave.
2016-02-26 15:35:12 +00:00
Adam Harrison
c5361801c9
Fix typo in weaver CLI help
2016-02-25 12:02:28 +00:00
Bryan Boreham
b064bcce49
Log when command-line peer list overridden by persisted list
...
Reworked interface to router so we split setting up the initial list
from beginning to make connections - we shouldn't do that until
after router.Start().
2016-02-19 14:29:33 +00:00
Bryan Boreham
ba8926a6ea
Persist set of peers to connect to
2016-02-17 18:12:16 +00:00
Bryan Boreham
ad036499eb
Add db infra to IPAM
2016-02-12 18:12:26 +00:00
Bryan Boreham
38c6eb28e8
Add basic infrastructure to use BoltDB for persistence
2016-02-12 18:12:26 +00:00
Adam Harrison
4cee647e73
Make weaveutil container-addrs observe $PROCFS
2016-02-09 22:25:47 +00:00
Bryan Boreham
ed3c50f43e
Merge pull request #1951 from weaveworks/issues/1940-remove-proxy-dockerbridgeip-dep
...
Use netlink instead of shelling out to `weave docker-bridge-ip`
2016-02-08 11:05:10 +00:00
Bryan Boreham
9ac62e8005
Extract common getenv-testing code
2016-02-08 10:46:18 +00:00
Matthias Radestock
98d76e1099
Merge pull request #1941 from weaveworks/issues/1873-check-running-master
...
Improve visibility of startup problems
Fixes #1873 .
2016-02-04 16:50:50 +00:00
Adam Harrison
e2ec2b436d
Use netlink instead of shelling out to weave docker-bridge-ip
2016-02-04 14:00:01 +00:00
Bryan Boreham
1d3c80ab49
Merge pull request #1944 from weaveworks/issues/1940-remove-proxy-weaveps-dep
...
Use netlink instead of shelling out to `weave ps`
2016-02-04 13:45:58 +00:00
Adam Harrison
65c48707f6
Use netlink instead of shelling out to weave ps
2016-02-04 12:51:18 +00:00
Matthias Radestock
ae725e333a
make plugin pay attention to WEAVE_HTTP_ADDR
2016-02-03 11:54:05 +00:00
Adam Harrison
1e01a31939
Support --host argument to weave launch
...
Allow the weave router bind to a specific host IP address instead of
INADDR_ANY.
2016-02-02 20:48:49 +00:00
Bryan Boreham
0a4b3a04ba
Wait for plugin status via unix socket
2016-02-01 10:11:46 +00:00
Bryan Boreham
78f2d82984
Extract function to listen on Unix socket
2016-02-01 10:11:46 +00:00
Matthias Radestock
2e9c1ee046
Merge branch '1.4'
2016-01-29 16:07:20 +00:00
Matthias Radestock
be9d64b2cc
Merge pull request #1936 from weaveworks/issues/1934-rm-socket
...
Remove Unix domain sockets on shutdown
Fixes #1934 .
2016-01-29 15:46:24 +00:00
Matthias Radestock
b2c9802aa2
Merge branch '1.4'
2016-01-29 15:25:50 +00:00
Bryan Boreham
e4828ad30a
Remove 'nameserver' option
2016-01-29 14:03:04 +00:00
Bryan Boreham
3320a9e7d4
Re-organise code so we can clean up using defer and return error codes to top level
2016-01-29 11:41:24 +00:00
Bryan Boreham
9b90a938f5
Remove Unix domain sockets on shutdown
2016-01-28 18:26:34 +00:00
Bryan Boreham
598efe5d1a
Reduce docker volumes for weavewait to just one set.
...
- Create an auxilliary container 'weavevolumes' to hold the '/w/w'
files, and map into that instead of creating new volumes every time.
- Show "/bin/false" as its command in `docker ps` instead of
"/home/weave/sigproxy".
- Remove volumes when cleaning up smoketest containers.
2016-01-28 15:57:22 +00:00
Matthias Radestock
31f736b37e
fix errors spotted by usage analysis
2016-01-26 18:13:29 +00:00
Peter Bourgon
e27b320ede
Update import location for mesh
2016-01-15 15:57:01 +01:00
Matthias Radestock
d770532b08
improve error handling
2016-01-15 08:53:04 +00:00
Matthias Radestock
31b303a419
move plugin network creation into weaveutil
...
Note that we remove the ability to set the weavemesh network name, or
disabling it altogether. This was always poorly support, since the
removal operation only ever operated on the default name. The option
was also not listed in the usage, though it was in the docs.
2016-01-15 08:52:57 +00:00
Matthias Radestock
9578798ec0
move plugin network removal into weaveutil
...
This does require starting containerised weaveutil with docker.sock
volume mounts.
2016-01-15 07:58:21 +00:00
Matthias Radestock
8061ea4079
don't attempt to delete the mesh network on plugin termination
...
It's pointless and inconsistent. Firstly, deletion will fail if there
are any attached containers. Secondly, we run the plugin with
restart=always, so it will get restarted and the network re-created.
Removal of the network does still happen on `weave stop|reset`, if
possible.
2016-01-15 06:21:11 +00:00
Matthias Radestock