|
21 | 21 |
|
22 | 22 | Avoid deeper levels because they do not render well.
|
23 | 23 |
|
24 |
| -======================================= |
25 |
| -Open vSwitch Advanced Features Tutorial |
26 |
| -======================================= |
| 24 | +============================== |
| 25 | +Open vSwitch Advanced Features |
| 26 | +============================== |
27 | 27 |
|
28 | 28 | Many tutorials cover the basics of OpenFlow. This is not such a tutorial.
|
29 | 29 | Rather, a knowledge of the basics of OpenFlow is a prerequisite. If you do not
|
@@ -54,18 +54,16 @@ hardware or even supervisor privilege on your system. Instead, we will use a
|
54 | 54 | script called ``ovs-sandbox``, which accompanies the tutorial, that constructs
|
55 | 55 | a software simulated network environment based on Open vSwitch.
|
56 | 56 |
|
57 |
| -.. TODO(stephenfin): Update installation guide link when this is moved. |
58 |
| -
|
59 | 57 | You can use ``ovs-sandbox`` three ways:
|
60 | 58 |
|
61 | 59 | * If you have already installed Open vSwitch on your system, then you should be
|
62 | 60 | able to just run ``ovs-sandbox`` from this directory without any options.
|
63 | 61 |
|
64 | 62 | * If you have not installed Open vSwitch (and you do not want to install it),
|
65 |
| - then you can build Open vSwitch according to the instructions in the |
66 |
| - `installation guide`, without installing it. Then run ``./ovs-sandbox -b |
67 |
| - DIRECTORY`` from this directory, substituting the Open vSwitch build |
68 |
| - directory for ``DIRECTORY``. |
| 63 | + then you can build Open vSwitch according to the instructions in |
| 64 | + :doc:`/intro/install/general`, without installing it. Then run |
| 65 | + ``./ovs-sandbox -b DIRECTORY`` from this directory, substituting the Open |
| 66 | + vSwitch build directory for ``DIRECTORY``. |
69 | 67 |
|
70 | 68 | * As a slight variant on the latter, you can run ``make sandbox`` from an Open
|
71 | 69 | vSwitch build directory.
|
|
0 commit comments