git://git.onelab.eu
/
sliver-openvswitch.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
305b76d
)
updated info in the exp-tool/README
author
Giuseppe Lettieri
<g.lettieri@iet.unipi.it>
Fri, 1 Feb 2013 11:09:55 +0000
(12:09 +0100)
committer
Giuseppe Lettieri
<g.lettieri@iet.unipi.it>
Fri, 1 Feb 2013 11:09:55 +0000
(12:09 +0100)
planetlab/exp-tool/README
patch
|
blob
|
history
diff --git
a/planetlab/exp-tool/README
b/planetlab/exp-tool/README
index
6cb2e4d
..
a932b42
100644
(file)
--- a/
planetlab/exp-tool/README
+++ b/
planetlab/exp-tool/README
@@
-17,16
+17,24
@@
has an IP address chosen by the experimenter. The idea is to connect
all the tap devices through the overlay network made up of Open vSwitch
bridges and tunnels among them.
all the tap devices through the overlay network made up of Open vSwitch
bridges and tunnels among them.
+Please note that the tap device IP address is required for technical
+reasons, even if you do not plan to use it.
+
* Installation
* Installation
-On each sliver we need to install sliver-openvswitch and obtain the
-following tags:
+In new slices, sliver-openvswitch comes preinstalled together with
+the vsys scripts it needs. All you have to do is ask your administrator
+for a private IP subnet for your slice.
+
+On older slices you may have to install sliver-openvswitch on each sliver
+and obtain the following tags:
NAME VALUE
vsys fd_tuntap
vsys vif_up
vsys vif_down
NAME VALUE
vsys fd_tuntap
vsys vif_up
vsys vif_down
+vsys promisc
vsys_net (some subnet)
vsys_net (some subnet)
@@
-59,8
+67,8
@@
contains four nodes:
4) planetlab2.urv.cat
4) planetlab2.urv.cat
-Assume we have
reserved subnet 10.0.9.0/24 using vsys_net
. We are
-goin
t
to build the following overlay network:
+Assume we have
obtained subnet 10.0.9.0/24 for our slice
. We are
+goin
g
to build the following overlay network:
10.0.9.1/24 10.0.9.2/24 10.0.9.3/24
1 ----------- 2 ------------ 3
10.0.9.1/24 10.0.9.2/24 10.0.9.3/24
1 ----------- 2 ------------ 3
@@
-150,17
+158,16
@@
all: do wathever is needed to setup all the links in the 'links' file.
clean: tear down all existing links
clean: tear down all existing links
-L/N1-N2: setup a link between nodes
HOST_N1 and
HOST_N2
+L/N1-N2: setup a link between nodes
$HOST_N1 and $
HOST_N2
-U/N1-N2: tear down the link (if it exists) between nodes HOST_N1
- and HOST_N2
+U/N1-N2: tear down the link (if it exists) between nodes
$
HOST_N1
+ and
$
HOST_N2
-del-bridge.N: delete the bridge running on node HOST_N (this also tears down
- all links that have an endpoint in N)
+del-bridge.N: delete the bridge running on node
$
HOST_N (this also tears down
+ all links that have an endpoint in
$HOST_
N)
graph.ps create a postscript file containing a (simple) graphical
graph.ps create a postscript file containing a (simple) graphical
- representation
- of the current topology
+ representation of the current topology
====================================================
====================================================