From 2bc5fd30c0894f7b7ea2804c1420aa3c04b4e644 Mon Sep 17 00:00:00 2001 From: Adam Harrison Date: Fri, 11 Mar 2016 10:35:47 +0000 Subject: [PATCH] Make image paths absolute with respect to repo --- site/fastdp/fastdp-how-it-works.md | 6 +++--- site/introducing-weave.md | 2 +- site/router-topology/overview.md | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/site/fastdp/fastdp-how-it-works.md b/site/fastdp/fastdp-how-it-works.md index 3ed4033e..41c262b5 100644 --- a/site/fastdp/fastdp-how-it-works.md +++ b/site/fastdp/fastdp-how-it-works.md @@ -6,16 +6,16 @@ layout: default Weave Net implements an overlay network between Docker hosts. Without fast datapath enabled, each packet is encapsulated in a tunnel protocol header and sent to the destination host, where the header is removed. The Weave router is a user space process, which means that the packet follows a winding path in and out of the Linux kernel: -![Weave Net Encapsulation](/images/weave-net-encap1-1024x459.png) +![Weave Net Encapsulation](/site/images/weave-net-encap1-1024x459.png) The fast datapath in Weave Net uses the Linux kernel's [Open vSwitch datapath module](https://www.kernel.org/doc/Documentation/networking/openvswitch.txt). This module enables the Weave Net router to tell the kernel how to process packets: -![Weave Net Encapsulation](/images/weave-net-fdp1-1024x454.png) +![Weave Net Encapsulation](/site/images/weave-net-fdp1-1024x454.png) Because Weave Net issues instructions directly to the kernel, context switches are decreased, and so by using `fast datapath` CPU overhead and latency is reduced. The packet goes straight from your application to the kernel, where the Virtual Extensible Lan (VXLAN) header is added (the NIC does this if it offers VXLAN acceleration). VXLAN is an IETF standard UDP-based tunneling protocol that enable you to use common networking tools like [Wireshark](https://www.wireshark.org/) to inspect the tunneled packets. -![Weave Net Encapsulation](/images/weave-frame-encapsulation-178x300.png) +![Weave Net Encapsulation](/site/images/weave-frame-encapsulation-178x300.png) Prior to version 1.2, Weave Net used a custom encapsulation format. Fast data path uses VXLAN, and like Weave Net's custom encapsulation format, VXLAN is UDP-based, and therefore needs no special configuration with network infrastructure. diff --git a/site/introducing-weave.md b/site/introducing-weave.md index 090db762..bbb7c6c3 100644 --- a/site/introducing-weave.md +++ b/site/introducing-weave.md @@ -15,7 +15,7 @@ Services provided by application containers on the weave network can be exposed Weave Net simplifies setting up a container network. Because containers on a Weave network use standard port numbers, (for example MySQL’s default is port 3306), managing microservices is straightforward. Every container can find the IP of any other container using a simple DNS query on the container's name, and it can also communicate directly without NAT, without using port mappings or complicated ambassador linking. And best of all deploying a Weave container network requires zero changes to your application’s code. -![Weave Net Encapsulation](/images/weave-net-overview.png) +![Weave Net Encapsulation](/site/images/weave-net-overview.png) ###Service Discovery diff --git a/site/router-topology/overview.md b/site/router-topology/overview.md index 4a96a3ef..fc69ee31 100644 --- a/site/router-topology/overview.md +++ b/site/router-topology/overview.md @@ -43,9 +43,9 @@ changing topology. For example, in this network, peer 1 is connected directly to 2 and 3, but if 1 needs to send a packet to 4 or 5 it must first send it to peer 3: -![A Partially Connected Weave Network](images/top-diag1.png "Partially connected Weave Network") +![A Partially Connected Weave Network](/site/images/top-diag1.png "Partially connected Weave Network") **See Also** * [Weave Router Encapsulation](/site/router-topology/router-encapsulation.md) - * [How Weave Inteprets Network Topology](/site/router-topology/network-topology.md) \ No newline at end of file + * [How Weave Inteprets Network Topology](/site/router-topology/network-topology.md)