summaryrefslogtreecommitdiff
path: root/tutorial
diff options
context:
space:
mode:
Diffstat (limited to 'tutorial')
-rw-r--r--tutorial/ovn-tutorial.rst5
-rw-r--r--tutorial/tutorial.rst8
2 files changed, 8 insertions, 5 deletions
diff --git a/tutorial/ovn-tutorial.rst b/tutorial/ovn-tutorial.rst
index 8d9fc1a43..bb5f6201f 100644
--- a/tutorial/ovn-tutorial.rst
+++ b/tutorial/ovn-tutorial.rst
@@ -873,11 +873,12 @@ of what the resulting OpenFlow flows look like.
Container Ports
---------------
+.. TODO(stephenfin): Update Docker link when this is moved.
+
OVN supports containers running directly on the hypervisors and running
containers inside VMs. This example shows how OVN supports network
virtualization to containers when run inside VMs. Details about how to use
-docker containers in OVS can be found in the `Docker installlation guide
-<../INSTALL.Docker.rst>`__.
+docker containers in OVS can be found in the `Docker installlation guide`.
To support container traffic created inside a VM and to distinguish network
traffic coming from different container vifs, for each container a logical port
diff --git a/tutorial/tutorial.rst b/tutorial/tutorial.rst
index fab635030..422bc0d61 100644
--- a/tutorial/tutorial.rst
+++ b/tutorial/tutorial.rst
@@ -54,6 +54,8 @@ hardware or even supervisor privilege on your system. Instead, we will use a
script called ``ovs-sandbox``, which accompanies the tutorial, that constructs
a software simulated network environment based on Open vSwitch.
+.. TODO(stephenfin): Update installation guide link when this is moved.
+
You can use ``ovs-sandbox`` three ways:
* If you have already installed Open vSwitch on your system, then you should be
@@ -61,9 +63,9 @@ You can use ``ovs-sandbox`` three ways:
* If you have not installed Open vSwitch (and you do not want to install it),
then you can build Open vSwitch according to the instructions in the
- `installation guide <INSTALL.rst>`__, without installing it. Then run
- ``./ovs-sandbox -b DIRECTORY`` from this directory, substituting the Open
- vSwitch build directory for ``DIRECTORY``.
+ `installation guide`, without installing it. Then run ``./ovs-sandbox -b
+ DIRECTORY`` from this directory, substituting the Open vSwitch build
+ directory for ``DIRECTORY``.
* As a slight variant on the latter, you can run ``make sandbox`` from an Open
vSwitch build directory.