From 4ea9cfca48fbac566fb7e3608b422b0acb3c0ca9 Mon Sep 17 00:00:00 2001 From: Bryan Boreham Date: Mon, 18 May 2015 16:49:45 +0100 Subject: [PATCH] Expanded description of 'weave launch' parameters for IPAM --- site/ipam.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/site/ipam.md b/site/ipam.md index cfc9d841..43693237 100644 --- a/site/ipam.md +++ b/site/ipam.md @@ -59,6 +59,25 @@ flag to specify how many peers there will be. It isn't a problem to over-estimate by a bit, but if you supply a number that is too small then multiple independent groups may form. +To illustrate, suppose you have three hosts, accessible to each other +as `$HOST1`, `$HOST2` and `$HOST3`. You can start weave on those three +hosts with these three commands: + + host1$ weave launch -iprange 10.3.0.0/16 $HOST2 $HOST3 + + host2$ weave launch -iprange 10.3.0.0/16 $HOST1 $HOST3 + + host3$ weave launch -iprange 10.3.0.0/16 $HOST1 $HOST2 + +Or, if it is not convenient to name all the other hosts at launch +time, you can give the number of peers like this: + + host1$ weave launch -iprange 10.3.0.0/16 -initpeercount 3 + + host2$ weave launch -iprange 10.3.0.0/16 -initpeercount 3 $HOST3 + + host3$ weave launch -iprange 10.3.0.0/16 -initpeercount 3 $HOST2 + ### Stopping and removing peers You may wish to `weave stop` and re-launch to change some config or to