reweave/weave
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge branch '1.5'

Browse Source
This commit is contained in:
Matthias Radestock committed 2016-06-06 11:51:19 +01:00
2 parents 39ba706a9b aa4980bbda
commit faef371a8c
1 file changed
+12 -28
Download Patch File Download Diff File Expand all files Collapse all files
site/plugin.md
+12 -28
View File
@@ -5,13 +5,13 @@ menu_order: 60
* [Launching Weave Net and Running Containers Using the Plugin](#launching)
* [Restarting the Plugin](#restarting)
* [Bypassing the Central Cluster Store When Building Docker Apps](#cluster-store)
* [Using other plugin command-line arguments](#plugin-args)
* [Configuring the Plugin](#configuring)
Docker versions 1.9 and later have a plugin mechanism for adding
different network providers. Weave Net installs itself as a network plugin
when you start it with `weave launch`. The Weave Docker Networking plugin is fast and easy to use and
best of all doesn't require an external cluster store in order to use it.
different network providers. Weave Net installs itself as a network
plugin when you start it with `weave launch`. The Weave Docker
Networking Plugin is fast and easy to use, and, unlike other
networking plugins, does not require an external cluster store.
To create a network which can span multiple Docker hosts, Weave Net peers must be connected to each other, by specifying the other hosts during `weave launch` or via
[`weave connect`](/site/using-weave/finding-adding-hosts-dynamically.md).
@@ -24,7 +24,7 @@ After you've launched Weave Net and peered your hosts, you can start containers
on any of the hosts, and they can all communicate with each other.
>**Warning!** It is inadvisable to attach containers to the Weave network using the Weave Docker Networking Plugin and Weave Docker API Proxy simultaneously. Such containers will end up with two Weave network interfaces and two IP addresses, which is rarely desirable. To ensure that the proxy is not being used, do not run eval $(weave env), or docker $(weave config).
>**Warning!** It is inadvisable to attach containers to the Weave network using the Weave Docker Networking Plugin and Weave Docker API Proxy simultaneously. Such containers will end up with two Weave network interfaces and two IP addresses, which is rarely desirable. To ensure that the proxy is not being used, do not run `eval $(weave env)`, or `docker $(weave config) ...`.
In order to use Weave Net's [Service Discovery](/site/weavedns.md) you
must pass the additional arguments `--dns` and `-dns-search`, for
@@ -66,26 +66,17 @@ If you are using `systemd` with Docker 1.9, it is advised that you modify the Do
TimeoutStartSec=0
###<a name="cluster-store"></a>Bypassing the Central Cluster Store When Building Docker Apps
To run a Docker cluster without a central database, you need to ensure the following:
###<a name="configuring"></a>Configuring the Plugin
1. Run in "local" scope. This tells Docker to ignore any cross-host coordination.
2. Allow Weave to handle all the cross-host coordination and to set up all networks. This is done by using the `weave launch` command.
3. Provide an IP Address Management (IPAM) driver, which links to Weave Net's own IPAM system
All cross-host coordination is handled by Weave Net's "mesh" communication, using gossipDNS and eventual consistency to avoid the need for constant communication and dependency on a central cluster store.
###<a name="plugin-args"></a>Using other plugin command-line arguments
If you need to give additional arguments to the plugin independently, don't
use `weave launch`, but instead run:
The plugin accepts a number of configuration parameters. To supply
these, instead of running `weave launch`, start the router and plugin
separately with:
$ weave launch-router [other peers]
$ weave launch-plugin [plugin arguments]
$ weave launch-plugin [plugin parameters]
The plugin command-line arguments are:
The plugin configuration parameters are:
* `--log-level=debug|info|warning|error` --tells the plugin
how much information to emit for debugging.
@@ -99,13 +90,6 @@ To turn this off, e.g. you want to configure your own multicast
route, add the `--no-multicast-route` flag to `weave launch-plugin`.
>Note: When using the Docker Plugin, there is no need to run `eval
$(weave env)` to enable the Proxy. If you do, you may end up with two
weave network interfaces and two IP addresses for each container.
**See Also**
* [How the Weave Network Plugin Works](/site/plugin/plugin-how-it-works.md)
* [Plugin Command-line Arguments](/site/plugin/plug-in-command-line.md)