edits from awh

This commit is contained in:
Anita Buehrle committed 2016-03-08 12:14:27 -06:00
1 parent e2c8dba981
commit be2dfda78e
3 files changed
+4 -4

No files matched your search

+1 -1
View File
@@ -60,7 +60,7 @@ through three states: 'deferred', 'waiting' and 'achieved':
themselves successfully themselves successfully
* 'achieved' - consensus achieved; allocations proceed normally * 'achieved' - consensus achieved; allocations proceed normally
Finally, you some peers can be launched as election observers using the Finally, some peers can be launched as election observers using the
`--observer` option: `--observer` option:
host4$ weave launch --observer $HOST3 host4$ weave launch --observer $HOST3
+2 -2
View File
@@ -14,8 +14,8 @@ if Weave Net is run again on that node it will start from scratch.
For failed peers, the `weave rmpeer` command can be used to For failed peers, the `weave rmpeer` command can be used to
permanently remove the ranges allocated to said peer. This allows permanently remove the ranges allocated to said peer. This allows
other peers to allocate IPs in the ranges previously owned by the removed peer other peers to allocate IPs in the ranges previously owned by the removed peer,
peer, and as such should be used with extreme caution - if the removed and as such should be used with extreme caution - if the removed
peer had transferred some range of IP addresses to another peer but peer had transferred some range of IP addresses to another peer but
this is not known to the whole network, or if it later rejoins this is not known to the whole network, or if it later rejoins
the Weave network, the same IP address may be allocated twice. the Weave network, the same IP address may be allocated twice.
+1 -1
View File
@@ -48,7 +48,7 @@ Weave hosts, regardless of where the actual application containers are located.
Using the netcat service example described in Using the netcat service example described in
[Deploying Applications](/site/using-weave/deploying-applications.md), and expanding upon it, you now decide to add a third containerized netcat service. This additional netcat service runs on `$HOST3`, and listens on port 2211, but it is not on the Weave network. [Deploying Applications](/site/using-weave/deploying-applications.md), and expanding upon it, you now decide to add a third containerized netcat service. This additional netcat service runs on `$HOST3`, and listens on port 2211, but it is not on the Weave network.
An additional caveat is that `$HOST3` can only be reached from `$HOST1`, which is not accessible via `$HOST2`. Nonetheless, you still need to make a `$HOST3` service available to an application that is running in a container on `$HOST2`. An additional caveat is that `$HOST3` can only be reached from `$HOST1`, which is not accessible via `$HOST2`. Nonetheless, you still need to make the `$HOST3` service available to an application that is running in a container on `$HOST2`.
To satisfy this scenario, first expose the [application network to the host](/site/using-weave/host-network-integration.md) by running the following on `$HOST1`: To satisfy this scenario, first expose the [application network to the host](/site/using-weave/host-network-integration.md) by running the following on `$HOST1`: