Consisten spacing in Markdown headings
Jekyll doesn't tolerate this, and it's generally cosidered a cleaner style, we've had a bit of mixed style and this makes it consistent.
This commit is contained in:
24 files changed
+111
-111
No files matched your search
@@ -16,7 +16,7 @@ on which they live.
|
||||
|
||||

|
||||
|
||||
###Configuring EC2 Instances to use Weave AWS-VPC Mode
|
||||
### Configuring EC2 Instances to use Weave AWS-VPC Mode
|
||||
|
||||
First, your AWS instances need to be given write access to the route
|
||||
table via its
|
||||
@@ -59,7 +59,7 @@ addresses will flow over the AWS network unmodified.
|
||||
Finally, since Weave will be operating with IP addresses outside of the
|
||||
range allocated by Amazon, you must disable "Source/Destination check" on each machine.
|
||||
|
||||
###Using AWS-VPC Mode
|
||||
### Using AWS-VPC Mode
|
||||
|
||||
Launch Weave Net with the `--awsvpc` flag:
|
||||
|
||||
@@ -68,7 +68,7 @@ Launch Weave Net with the `--awsvpc` flag:
|
||||
>>**Note:** You will still need to supply the names or IP addresses of other hosts in
|
||||
your cluster.
|
||||
|
||||
###Present Limitations
|
||||
### Present Limitations
|
||||
|
||||
- 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
|
||||
@@ -85,7 +85,7 @@ your cluster.
|
||||
- All of your containers must be on the same network, with no subnet
|
||||
isolation. (We hope to ease this limitation in future.)
|
||||
|
||||
###Packet size (MTU)
|
||||
### Packet size (MTU)
|
||||
|
||||
The Maximum Transmission Unit, or MTU, is the technical term for the
|
||||
limit on how big a single packet can be on the network. Weave Net
|
||||
|
||||
@@ -20,7 +20,7 @@ where,
|
||||
|
||||
>Note If you are using the Weave Docker API proxy, it will have modified `DOCKER_HOST` to point to the proxy and therefore you will have to pass `-e WEAVE_CIDR=none` to start a container that _doesn't_ get automatically attached to the weave network for the purposes of this example.
|
||||
|
||||
###Dynamically Detaching Containers
|
||||
### Dynamically Detaching Containers
|
||||
|
||||
A container can be detached from a subnet, by using the `weave detach` command:
|
||||
|
||||
|
||||
@@ -10,13 +10,13 @@ When Weave Net cannot use the fast data path between two hosts, it falls back to
|
||||
|
||||
See [How Fastdp Works](/site/how-it-works/fastdp-how-it-works.md) for a more in-depth discussion of this feature.
|
||||
|
||||
###Disabling Fast Datapath
|
||||
### Disabling Fast Datapath
|
||||
|
||||
You can disable fastdp by enabling the `WEAVE_NO_FASTDP` environment variable at `weave launch`:
|
||||
|
||||
$ WEAVE_NO_FASTDP=true weave launch
|
||||
|
||||
###Fast Datapath and Encryption
|
||||
### Fast Datapath and Encryption
|
||||
|
||||
Fast datapath implements encryption using IPsec which is configured with IP
|
||||
transformation framework (XFRM) provided by the Linux kernel.
|
||||
@@ -28,7 +28,7 @@ Cloud Platform denies ESP packets by default.
|
||||
See [How Weave Implements Encryption](/site/how-it-works/encryption-implementation.md)
|
||||
for more details for the fastdp encryption.
|
||||
|
||||
###Viewing Connection Mode Fastdp or Sleeve
|
||||
### Viewing Connection Mode Fastdp or Sleeve
|
||||
|
||||
Weave Net automatically uses the fastest datapath for every connection unless it encounters a situation that prevents it from working. To ensure that Weave Net can use the fast datapath:
|
||||
|
||||
@@ -48,7 +48,7 @@ Where fastdp indicates that fast datapath is being used on a connection. If fast
|
||||
$ weave status connections
|
||||
<- 192.168.122.25:54782 established sleeve 8a:50:4c:23:11:ae(ubuntu1204)
|
||||
|
||||
###<a name="mtu"></a>Packet size (MTU)
|
||||
### <a name="mtu"></a>Packet size (MTU)
|
||||
|
||||
The Maximum Transmission Unit, or MTU, is the technical term for the
|
||||
limit on how big a single packet can be on the network. Weave Net
|
||||
|
||||
@@ -23,7 +23,7 @@ hosts run:
|
||||
Any other existing hosts on the Weave network will attempt to
|
||||
establish connections to the new host as well.
|
||||
|
||||
###Instructing Peers to Forget a Host
|
||||
### Instructing Peers to Forget a Host
|
||||
|
||||
To instruct a peer to forget a particular host specified to it via
|
||||
`weave launch` or `weave connect` run:
|
||||
@@ -34,14 +34,14 @@ This prevents the peer from reconnecting to that host once
|
||||
connectivity to it is lost, and can be used to administratively remove
|
||||
any decommissioned peers from the network.
|
||||
|
||||
###Bulk Replacing Hosts
|
||||
### Bulk Replacing Hosts
|
||||
|
||||
Hosts can also be bulk-replaced. All existing hosts will be forgotten,
|
||||
and the new hosts added:
|
||||
|
||||
host# weave connect --replace $NEW_HOST1 $NEW_HOST2
|
||||
|
||||
###Restarting Docker and Weave Net
|
||||
### Restarting Docker and Weave Net
|
||||
|
||||
If Weave Net is restarted by Docker it automatically remembers any
|
||||
previous connect and forget operations, however if you stop it
|
||||
|
||||
@@ -22,7 +22,7 @@ And you can also ping the `a1` netcat application container residing on `$HOST1`
|
||||
|
||||
host2$ ping $(weave dns-lookup a1)
|
||||
|
||||
###Exposing Multiple Subnets
|
||||
### Exposing Multiple Subnets
|
||||
|
||||
Multiple subnet addresses can be exposed or hidden using a single command:
|
||||
|
||||
@@ -31,14 +31,14 @@ Multiple subnet addresses can be exposed or hidden using a single command:
|
||||
host2$ weave hide net:default net:10.2.2.0/24
|
||||
10.2.1.132 10.2.2.130
|
||||
|
||||
###Adding Exposed Addresses to weaveDNS
|
||||
### Adding Exposed Addresses to weaveDNS
|
||||
|
||||
Exposed addresses can also be added to weaveDNS by supplying fully qualified domain names:
|
||||
|
||||
host2$ weave expose -h exposed.weave.local
|
||||
10.2.1.132
|
||||
|
||||
###<a name="routing"></a>Routing from Another Host
|
||||
### <a name="routing"></a>Routing from Another Host
|
||||
|
||||
After running `weave expose`, you can use Linux routing to provide
|
||||
access to the Weave network from hosts that are not running Weave Net:
|
||||
|
||||
@@ -4,7 +4,7 @@ menu_order: 100
|
||||
---
|
||||
|
||||
|
||||
###Enabling Multi-Cloud Networking
|
||||
### Enabling Multi-Cloud Networking
|
||||
|
||||
Before multi-cloud networking can be enabled, you must configure the network to allow
|
||||
connections through Weave Net's control and data ports on the Docker hosts. By default, the
|
||||
@@ -20,7 +20,7 @@ port and UDP 9000/9001 for its data port.
|
||||
the same setting.
|
||||
|
||||
|
||||
###Multi-hop routing
|
||||
### Multi-hop routing
|
||||
|
||||
A network of containers across more than two hosts can be
|
||||
established even when there is only partial connectivity
|
||||
|
||||
@@ -13,7 +13,7 @@ This section contains the following topics:
|
||||
|
||||
|
||||
|
||||
###<a name="exporting"></a>Exporting Services
|
||||
### <a name="exporting"></a>Exporting Services
|
||||
|
||||
Services running in containers on a Weave network can be made
|
||||
accessible to the outside world (and, more generally, to other networks)
|
||||
@@ -43,7 +43,7 @@ With the above in place, you can connect to the 'nc' service from anywhere using
|
||||
|
||||
Similar NAT rules to the above can be used to expose services not just to the outside world but also to other, internal, networks.
|
||||
|
||||
###<a name="importing"></a>Importing Services
|
||||
### <a name="importing"></a>Importing Services
|
||||
|
||||
Applications running in containers on a Weave network can be given access to services, which are only reachable from certain
|
||||
Weave hosts, regardless of where the actual application containers are located.
|
||||
@@ -73,7 +73,7 @@ You can now connect to it from the application container running on `$HOST2` usi
|
||||
|
||||
Note that you should be able to run this command from any application container.
|
||||
|
||||
###<a name="binding"></a>Binding Services
|
||||
### <a name="binding"></a>Binding Services
|
||||
|
||||
Importing a service provides a degree of indirection that allows late and dynamic binding, similar to what can be achieved with a proxy.
|
||||
|
||||
@@ -81,7 +81,7 @@ Referring back to the [netcat services example that is running on three hosts](#
|
||||
|
||||
You can point application containers to another service location by changing the above NAT rule, without altering the applications.
|
||||
|
||||
###<a name="routing"></a>Routing Services
|
||||
### <a name="routing"></a>Routing Services
|
||||
|
||||
You can combine the service export and service import features to establish connectivity between applications and services residing on disjointed networks, even if those networks are separated by firewalls and have overlapping IP ranges.
|
||||
|
||||
@@ -103,7 +103,7 @@ Now any host on the same network as `$HOST2` is able to access the service:
|
||||
|
||||
echo 'Hello, world.' | nc $HOST2 4433
|
||||
|
||||
###<a name="change-location"></a>Dynamically Changing Service Locations
|
||||
### <a name="change-location"></a>Dynamically Changing Service Locations
|
||||
|
||||
Furthermore, as explained in Binding Services, service locations can be dynamically altered without having to change any of the applications that access them.
|
||||
|
||||
|
||||
Reference in new issue
Block a user