From 425f17aab13218ae540e3101bbd3b93f95ad4dd4 Mon Sep 17 00:00:00 2001 From: Bryan Boreham Date: Mon, 13 Jun 2016 11:59:37 +0100 Subject: [PATCH] Mention that 'weave launch' now waits --- site/using-weave/awsvpc.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/site/using-weave/awsvpc.md b/site/using-weave/awsvpc.md index 011cfc85..75fe7d2c 100644 --- a/site/using-weave/awsvpc.md +++ b/site/using-weave/awsvpc.md @@ -73,6 +73,11 @@ your cluster. - AWS-VPC mode does not inter-operate with other Weave Net modes; it is all or nothing. In this mode, all hosts in a cluster must be AWS instances. (We hope to ease this limitation in future.) +- The `weave launch` command waits until the + [IP address manager](/site//operational-guide/concepts.md#ip-address-manager-ipam) + is ready, i.e. until after this peer has been able to make contact + with other peers and confirm that it has joined the cluster the + bridge. Without AWS-VPC, `weave launch` returns without waiting. - The AWS network does not support multicast. - The number of hosts in a cluster is limited by the maximum size of your AWS route table. This is limited to 50 entries though you