replaced urls for tasks/manage section
This commit is contained in:
abuehrle committed
1 parent
70924f6f3a
commit
324d013f88
23 files changed
+39
-39
No files matched your search
@@ -211,4 +211,4 @@ Integrity Check Value of AES-GCM.
|
||||
|
||||
* [architecture documentation](https://github.com/weaveworks/weave/blob/master/docs/architecture.txt)
|
||||
* [fastdp encryption](https://github.com/weaveworks/weave/blob/master/docs/fastdp-crypto.md)
|
||||
* [Securing Containers Across Untrusted Networks](/site/using-weave/security-untrusted-networks.md)
|
||||
* [Securing Containers Across Untrusted Networks](/site/tasks/manage/security-untrusted-networks.md)
|
||||
@@ -8,7 +8,7 @@ search_type: Documentation
|
||||
Weave Net peers
|
||||
[communicate with each other over both TCP and UDP](/site/concepts/how-it-works.md). This
|
||||
communication
|
||||
[can be encrypted](/site/using-weave/security-untrusted-networks.md).
|
||||
[can be encrypted](/site/tasks/manage/security-untrusted-networks.md).
|
||||
|
||||
Encryption of control plane traffic (TCP) and data plane traffic (UDP) of sleeve
|
||||
overlay is accomplished using the [NaCl](http://nacl.cr.yp.to/)
|
||||
@@ -42,4 +42,4 @@ the IP transformation framework (XFRM).
|
||||
**See Also**
|
||||
|
||||
* [How Weave Implements Encryption](/site/concepts/encryption-implementation.md)
|
||||
* [Securing Containers Across Untrusted Networks](/site/using-weave/security-untrusted-networks.md)
|
||||
* [Securing Containers Across Untrusted Networks](/site/tasks/manage/security-untrusted-networks.md)
|
||||
@@ -26,6 +26,6 @@ Prior to version 1.2, Weave Net used a custom encapsulation format. Fast datapat
|
||||
**See Also**
|
||||
|
||||
* [Using Weave Net](/site/using-weave.md)
|
||||
* [Using Fast Datapath](/site/using-weave/fastdp.md)
|
||||
* [Using Fast Datapath](/site/tasks/manage/fastdp.md)
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ is given an IP address and netmask supplied either by the user or
|
||||
by Weave Net's IP address allocator.
|
||||
|
||||
Weave Net routes packets between containers on different hosts via two
|
||||
methods: a [fast data path](/site/using-weave/fastdp.md) method, which operates
|
||||
methods: a [fast data path](/site/tasks/manage/fastdp.md) method, which operates
|
||||
entirely in kernel space, and a fallback `sleeve` method, in which
|
||||
packets destined for non-local containers are captured by the kernel
|
||||
and processed by the Weave Net router in user space, forwarded over
|
||||
|
||||
@@ -5,7 +5,7 @@ search_type: Documentation
|
||||
---
|
||||
|
||||
When the Weave Net router forwards packets to peers in `sleeve` mode
|
||||
(rather than via the [fast data path](/site/using-weave/fastdp.md)), the
|
||||
(rather than via the [fast data path](/site/tasks/manage/fastdp.md)), the
|
||||
encapsulation looks something like this:
|
||||
|
||||
+-----------------------------------+
|
||||
|
||||
+5
-5
@@ -25,7 +25,7 @@ For more information, refer to [Manually Specifying the IP Address of a Containe
|
||||
<a name="expose-container"></a>
|
||||
**Q: How do I expose one of my containers to the outside world?**
|
||||
|
||||
Exposing a container to the outside world is described in [Exporting Services](/site/using-weave/service-management.md#exporting).
|
||||
Exposing a container to the outside world is described in [Exporting Services](/site/tasks/manage/service-management.md#exporting).
|
||||
|
||||
|
||||
<a name="legacy-network"></a>
|
||||
@@ -37,7 +37,7 @@ For example, you have a Weave network that runs on hosts A, B, C. and you have a
|
||||
|
||||
A simple way to accomplish this would be to run Weave on the host and then run, `weave expose` to expose the network to any running containers. Or you set up a route from P to one of A, B or C. See [Integrating a Network Host](/site/using-weave/host-network-integration.md).
|
||||
|
||||
Yet another option is to expose a port from the container on host B and then connect to it. You can read about exposing ports in [Exporting Services](/site/using-weave/service-management.md#exporting).
|
||||
Yet another option is to expose a port from the container on host B and then connect to it. You can read about exposing ports in [Exporting Services](/site/tasks/manage/service-management.md#exporting).
|
||||
|
||||
|
||||
<a name="duplicate-ip"></a>
|
||||
@@ -71,7 +71,7 @@ For more information about fast datapath see [How Fast Datapath Works](/site/con
|
||||
|
||||
To view whether Weave is using fastdp or not, you can run, `weave status connections`
|
||||
|
||||
For more information on this command, see [Using Fast Datapath](/site/using-weave/fastdp.md).
|
||||
For more information on this command, see [Using Fast Datapath](/site/tasks/manage/fastdp.md).
|
||||
|
||||
|
||||
<a name="encrypted-fastdp"></a>
|
||||
@@ -79,12 +79,12 @@ For more information on this command, see [Using Fast Datapath](/site/using-weav
|
||||
|
||||
Yes, 1.9 version of Weave Net added the encryption feature to fastdp.
|
||||
|
||||
See [Using Fast Datapath](/site/using-weave/fastdp.md) for more information.
|
||||
See [Using Fast Datapath](/site/tasks/manage/fastdp.md) for more information.
|
||||
|
||||
<a name="app-isolation"></a>
|
||||
**Q: Can I create multiple networks where containers can communicate on one network, but are isolated from containers on other networks?**
|
||||
|
||||
Yes, of course! Weave allows you to run isolated networks and still allow open communications between individual containers from those isolated networks. You can find information on how to do this in [Application Isolation](/site/using-weave/application-isolation.md).
|
||||
Yes, of course! Weave allows you to run isolated networks and still allow open communications between individual containers from those isolated networks. You can find information on how to do this in [Application Isolation](/site/tasks/manage/application-isolation.md).
|
||||
|
||||
|
||||
**<a name="ports"></a>Q: Which ports does Weave Net use (e.g. if I am configuring a firewall) ?**
|
||||
|
||||
@@ -34,14 +34,14 @@ There are several configuration parameters which can be set with:
|
||||
The parameters include:
|
||||
|
||||
* `WEAVE_PASSWORD` - if non empty, it will instruct Weave Net to encrypt
|
||||
traffic - see [here](/site/using-weave/security-untrusted-networks.md) for
|
||||
traffic - see [here](/site/tasks/manage/security-untrusted-networks.md) for
|
||||
more details.
|
||||
* `WEAVE_MULTICAST` - set to 1 on each host running the plugin to enable
|
||||
multicast traffic on any Weave Net network.
|
||||
* `WEAVE_MTU` - Weave Net defaults to 1376 bytes, but you can set a
|
||||
smaller size if your underlying network has a tighter limit, or set
|
||||
a larger size for better performance if your network supports jumbo
|
||||
frames - see [here](/site/using-weave/fastdp.md#mtu) for more
|
||||
frames - see [here](/site/tasks/manage/fastdp.md#mtu) for more
|
||||
details.
|
||||
* `IPALLOC_RANGE` - the range of IP addresses used by Weave Net and the subnet
|
||||
they are placed in (CIDR format; default 10.32.0.0/12).
|
||||
|
||||
@@ -34,9 +34,9 @@ create the `/etc/sysconfig/weave` environment file using the following format:
|
||||
|
||||
You can also use the [`weave connect`](/site/using-weave/finding-adding-hosts-dynamically.md) command to add participating hosts dynamically.
|
||||
|
||||
Additionally, if you want to enable [encryption](/site/using-weave/security-untrusted-networks.md) specify a
|
||||
Additionally, if you want to enable [encryption](/site/tasks/manage/security-untrusted-networks.md) specify a
|
||||
password using `WEAVE_PASSWORD="wfvAwt7sj"` in the `/etc/sysconfig/weave` environment file, and it will get picked up by
|
||||
Weave Net on launch. Recommendations for choosing a suitably strong password can be found [here](/site/using-weave/security-untrusted-networks.md).
|
||||
Weave Net on launch. Recommendations for choosing a suitably strong password can be found [here](/site/tasks/manage/security-untrusted-networks.md).
|
||||
|
||||
You can now launch Weave Net using
|
||||
|
||||
|
||||
@@ -93,7 +93,7 @@ Standard firewall rules can be deployed to restrict access to the
|
||||
Weave Net control and data ports.
|
||||
|
||||
For communication across untrusted networks, connections can be
|
||||
[encrypted](/site/using-weave/security-untrusted-networks.md).
|
||||
[encrypted](/site/tasks/manage/security-untrusted-networks.md).
|
||||
|
||||
### <a name="testing"></a>Testing Container Communications
|
||||
|
||||
@@ -136,6 +136,6 @@ Weave Net supports *any* protocol, and it doesn't have to be over TCP/IP. For ex
|
||||
|
||||
* [Installing Weave Net](/site/install/installing-weave.md)
|
||||
* [Using Weave Cloud to get started with Weave Net](/site/using-weave/weave-cloud.md)
|
||||
* [Using Fastdp With Weave Net](/site/using-weave/fastdp.md)
|
||||
* [Using Fastdp With Weave Net](/site/tasks/manage/fastdp.md)
|
||||
* [Integrating Docker via the Network Plugin (Legacy)](/site/install/plugin/plugin.md)
|
||||
* [Integrating Docker via the Network Plugin (V2)](/site/install/plugin/plugin-v2.md)
|
||||
@@ -123,6 +123,6 @@ connect to it.
|
||||
|
||||
* [Installing Weave Net](/site/install/installing-weave.md)
|
||||
* [Using Weave Net](/site/using-weave.md)
|
||||
* [Using Fastdp With Weave Net](/site/using-weave/fastdp.md)
|
||||
* [Using Fastdp With Weave Net](/site/tasks/manage/fastdp.md)
|
||||
* [Integrating Docker via the Network Plugin (Legacy)](/site/install/plugin/plugin.md)
|
||||
* [Integrating Docker via the Network Plugin (V2)](/site/install/plugin/plugin-v2.md)
|
||||
@@ -252,7 +252,7 @@ The list of variables you can set is:
|
||||
* `WEAVE_MTU` - Weave Net defaults to 1376 bytes, but you can set a
|
||||
smaller size if your underlying network has a tighter limit, or set
|
||||
a larger size for better performance if your network supports jumbo
|
||||
frames - see [here](/site/using-weave/fastdp.md#mtu) for more
|
||||
frames - see [here](/site/tasks/manage/fastdp.md#mtu) for more
|
||||
details.
|
||||
|
||||
Example:
|
||||
|
||||
+1
-1
@@ -37,7 +37,7 @@ Weave Net can forward traffic between nodes, and it works even if the mesh netwo
|
||||
|
||||
Weave Net automatically chooses the fastest path between two hosts, offering near native throughput and latency, all without your intervention.
|
||||
|
||||
See [How Fast Datapath Works](/site/using-weave/fastdp.md) for more information.
|
||||
See [How Fast Datapath Works](/site/tasks/manage/fastdp.md) for more information.
|
||||
|
||||
### Network Operations Friendly
|
||||
|
||||
|
||||
@@ -53,7 +53,7 @@ Weave Net automatically chooses the fastest available method to
|
||||
transport data between peers. The best performing of these
|
||||
(the 'fast datapath') offers near-native throughput and latency.
|
||||
|
||||
See [Using Fast Datapath](/site/using-weave/fastdp.md) and
|
||||
See [Using Fast Datapath](/site/tasks/manage/fastdp.md) and
|
||||
[How Fast Datapath Works](/site/concepts/fastdp-how-it-works.md).
|
||||
|
||||
### <a name="docker"></a>Seamless Docker Integration (Weave Docker API Proxy)
|
||||
@@ -132,7 +132,7 @@ _isolation-through-subnets_ technique. This common strategy
|
||||
techniques can be used to deploy your applications to
|
||||
containers.
|
||||
|
||||
See [Isolating Applications](/site/using-weave/application-isolation.md)
|
||||
See [Isolating Applications](/site/tasks/manage/application-isolation.md)
|
||||
for information on how to use the isolation-through-subnets
|
||||
technique with Weave Net.
|
||||
|
||||
@@ -149,7 +149,7 @@ given container in advance. In these cases, you can take
|
||||
advantage of Weave's ability to attach and detach running
|
||||
containers to and from any network.
|
||||
|
||||
See [Dynamically Attaching and Detaching Containers](/site/using-weave/dynamically-attach-containers.md)
|
||||
See [Dynamically Attaching and Detaching Containers](/site/tasks/manage/dynamically-attach-containers.md)
|
||||
for details.
|
||||
|
||||
|
||||
@@ -176,7 +176,7 @@ running alongside Weave.
|
||||
Weave Net implements encryption and security using the Go version of [Daniel J. Bernstein's NaCl library](http://nacl.cr.yp.to/index.html),
|
||||
and, additionally in the case of encrypted fast datapath using [the cryptography framework of the Linux kernel](https://en.wikipedia.org/wiki/Crypto_API_(Linux)).
|
||||
|
||||
For information on how to secure your Docker network connections, see [Securing Connections Across Untrusted Networks](/site/using-weave/security-untrusted-networks.md) and for a more technical discussion on how Weave implements encryption see, [Weave Encryption](/site/concepts/encryption.md) and [How Weave Implements Encryption](/site/concepts/encryption-implementation.md).
|
||||
For information on how to secure your Docker network connections, see [Securing Connections Across Untrusted Networks](/site/tasks/manage/security-untrusted-networks.md) and for a more technical discussion on how Weave implements encryption see, [Weave Encryption](/site/concepts/encryption.md) and [How Weave Implements Encryption](/site/concepts/encryption-implementation.md).
|
||||
|
||||
|
||||
### <a name="host-network-integration"></a>Host Network Integration
|
||||
@@ -193,7 +193,7 @@ See [Integrating with the Host Network](/site/using-weave/host-network-integrati
|
||||
* **Binding Services** - A container can be bound to a particular IP and port without having to change your application code, while at the same time will maintain its original endpoint.
|
||||
* **Routing Services** - By combining the importing and exporting features, you can connect to disjointed networks, even when separated by firewalls and where there may be overlapping IP addresses.
|
||||
|
||||
See [Managing Services - Exporting, Importing, Binding and Routing](/site/using-weave/service-management.md) for instructions on how to manage services on a Weave container network.
|
||||
See [Managing Services - Exporting, Importing, Binding and Routing](/site/tasks/manage/service-management.md) for instructions on how to manage services on a Weave container network.
|
||||
|
||||
### <a name="multi-cloud-networking"></a>Multi-Cloud Networking
|
||||
|
||||
@@ -203,7 +203,7 @@ of containers that run on [Google Compute Engine](https://cloud.google.com/compu
|
||||
(GCE), [Amazon Elastic Compute Cloud](https://aws.amazon.com/ec2/)
|
||||
(EC2) and in a local data centre all at the same time.
|
||||
|
||||
See [Enabling Multi-Cloud networking and Muti-hop Routing](/site/using-weave/multi-cloud-multi-hop.md).
|
||||
See [Enabling Multi-Cloud networking and Muti-hop Routing](/site/tasks/manage/multi-cloud-multi-hop.md).
|
||||
|
||||
|
||||
### <a name="multi-hop-routing"></a>Multi-Hop Routing
|
||||
@@ -213,7 +213,7 @@ even when there is only partial connectivity between the hosts. Weave Net
|
||||
routes traffic between containers as long as there is at least one *path*
|
||||
of connected hosts between them.
|
||||
|
||||
See [Enabling Multi-Cloud networking and Multi-hop Routing](/site/using-weave/multi-cloud-multi-hop.md).
|
||||
See [Enabling Multi-Cloud networking and Multi-hop Routing](/site/tasks/manage/multi-cloud-multi-hop.md).
|
||||
|
||||
|
||||
### <a name="dynamic-topologies"></a>Dynamic Topologies
|
||||
@@ -230,7 +230,7 @@ reconfiguration or, in many cases, restarts of other containers.
|
||||
All that is required is for the migrated container to be started
|
||||
with the same IP address as it was given originally.
|
||||
|
||||
See [Managing Services - Exporting, Importing, Binding and Routing](/site/using-weave/service-management.md), in particular, Routing Services for more information on container mobility.
|
||||
See [Managing Services - Exporting, Importing, Binding and Routing](/site/tasks/manage/service-management.md), in particular, Routing Services for more information on container mobility.
|
||||
|
||||
|
||||
### <a name="fault-tolerance"></a>Fault Tolerance
|
||||
|
||||
@@ -10,7 +10,7 @@ puts all containers into a subnet that spans the entire allocation
|
||||
range, so that every Weave-attached container can communicate with every other
|
||||
Weave-attached container.
|
||||
|
||||
If you want some [isolation](/site/using-weave/application-isolation.md), you
|
||||
If you want some [isolation](/site/tasks/manage/application-isolation.md), you
|
||||
can choose to run containers on different subnets. To request the
|
||||
allocation of an address from a particular subnet, set the
|
||||
`WEAVE_CIDR` environment variable to `net:<subnet>` when creating the
|
||||
@@ -64,5 +64,5 @@ for manual allocation.
|
||||
**See Also**
|
||||
|
||||
* [Address Allocation with IP Address Management (IPAM)](/site/ipam.md)
|
||||
* [Isolating Applications on a Weave Network](/site/using-weave/application-isolation.md)
|
||||
* [Isolating Applications on a Weave Network](/site/tasks/manage/application-isolation.md)
|
||||
* [Starting, Stopping and Removing Peers](/site/ipam/stop-remove-peers-ipam.md)
|
||||
@@ -52,7 +52,7 @@ Individual IP addresses given to containers must, of course, be unique. If you p
|
||||
|
||||
**See Also**
|
||||
|
||||
* [Managing Services - Exporting, Importing, Binding and Routing](/site/using-weave/service-management.md)
|
||||
* [Managing Services - Exporting, Importing, Binding and Routing](/site/tasks/manage/service-management.md)
|
||||
* [Allocating IPs in a Specific Range](/site/using-weave/configuring-weave.md)
|
||||
* [Automatic IP Address Management](/site/ipam.md)
|
||||
|
||||
@@ -58,4 +58,4 @@ dropping attempted connections with peers in other cliques.
|
||||
|
||||
* [Address Allocation with IP Address Management (IPAM)](/site/ipam.md)
|
||||
* [Automatic Allocation Across Multiple Subnets](/site/ipam/allocation-multi-ipam.md)
|
||||
* [Isolating Applications on a Weave Network](/site/using-weave/application-isolation.md)
|
||||
* [Isolating Applications on a Weave Network](/site/tasks/manage/application-isolation.md)
|
||||
@@ -67,4 +67,4 @@ isolation between application containers, that feature needs to be disabled by [
|
||||
**See Also**
|
||||
|
||||
* [Automatic Allocation Across Multiple Subnets](/site/ipam/allocation-multi-ipam.md)
|
||||
* [Managing Services - Exporting, Importing, Binding and Routing](/site/using-weave/service-management.md)
|
||||
* [Managing Services - Exporting, Importing, Binding and Routing](/site/tasks/manage/service-management.md)
|
||||
@@ -68,5 +68,5 @@ with `weave launch` and `weave connect` run:
|
||||
|
||||
**See Also**
|
||||
|
||||
* [Enabling Multi-Cloud, Multi-Hop Networking and Routing](/site/using-weave/multi-cloud-multi-hop.md)
|
||||
* [Enabling Multi-Cloud, Multi-Hop Networking and Routing](/site/tasks/manage/multi-cloud-multi-hop.md)
|
||||
* [Stopping and Removing Peers](/site/ipam/stop-remove-peers-ipam.md)
|
||||
@@ -61,4 +61,4 @@ hosts.
|
||||
|
||||
* [Using Weave Net](/site/using-weave.md)
|
||||
* [General information on IP Addresses, Routes and Networks](/site/concepts/ip-addresses.md)
|
||||
* [Managing Services - Exporting, Importing, Binding and Routing](/site/using-weave/service-management.md)
|
||||
* [Managing Services - Exporting, Importing, Binding and Routing](/site/tasks/manage/service-management.md)
|
||||
@@ -54,4 +54,4 @@ Be aware that:
|
||||
**See Also**
|
||||
|
||||
* [Weave Encryption](/site/concepts/encryption.md)
|
||||
* [Using Fast Datapath](/site/using-weave/fastdp.md)
|
||||
* [Using Fast Datapath](/site/tasks/manage/fastdp.md)
|
||||
@@ -114,5 +114,5 @@ For example, you can move the netcat service to `$HOST4:2211` and it will retai
|
||||
**See Also**
|
||||
|
||||
* [Adding and Removing Hosts Dynamically](/site/using-weave/finding-adding-hosts-dynamically.md)
|
||||
* [Enabling Multi-Cloud, Multi-Hop Networking and Routing](/site/using-weave/multi-cloud-multi-hop.md)
|
||||
* [Enabling Multi-Cloud, Multi-Hop Networking and Routing](/site/tasks/manage/multi-cloud-multi-hop.md)
|
||||
|
||||
@@ -14,7 +14,7 @@ limitations, we have removed `weave run`.
|
||||
If you have scripts using `weave run`, you can achieve exactly the
|
||||
same effect by combining `docker run` and `weave attach`; see
|
||||
[Dynamically Attaching and Detaching
|
||||
Containers](/site/using-weave/dynamically-attach-containers.md) for
|
||||
Containers](/site/tasks/manage/dynamically-attach-containers.md) for
|
||||
details.
|
||||
|
||||
The `weave start` and `weave restart` commands have also been removed,
|
||||
|
||||
@@ -33,7 +33,7 @@ See [Integrating Docker via the Network Plugin (Legacy)](/site/install/plugin/pl
|
||||
|
||||
**3.** Containers can also be attached to the Weave network with `weave attach` commands. This method also
|
||||
does not use the Weave Docker API Proxy.
|
||||
See [Dynamically Attaching and Detaching Containers](/site/using-weave/dynamically-attach-containers.md).
|
||||
See [Dynamically Attaching and Detaching Containers](/site/tasks/manage/dynamically-attach-containers.md).
|
||||
|
||||
### <a name="weave-api-proxy"></a>Setting Up The Weave Net Docker API Proxy
|
||||
|
||||
|
||||
Reference in new issue
Block a user