Commit 73144f44 authored by Leigh B. Stoller's avatar Leigh B. Stoller
Browse files

Minor updates to widearea usage page, including some planetlab

specific notes. Also convert examples to use physical nodes in
tb-fix-node, and fix the types using in tb-set-hardware statements.
parent 17f04217
<!--
EMULAB-COPYRIGHT
Copyright (c) 2000-2002 University of Utah and the Flux Group.
Copyright (c) 2000-2003 University of Utah and the Flux Group.
All rights reserved.
-->
<center>
......@@ -16,22 +16,32 @@ exclusive use of your local nodes, you are most likely sharing your
wide-area nodes with others. For that reason, there are a number of
features that are not available on wide-area nodes. <b>Note:</b> many of
these restrictions will be lifted when we switch to Unix virtual
machines on wide-are nodes (eg: jail on Freebsd and vservers on Linux).
machines on wide-are nodes (eg: jail on Freebsd and vservers on
Linux).
<em> PlanetLab nodes have a slightly different set of features and
restrictions. These differences are noted where appropriate. </em>
<ul>
<li> You may not reboot or power cycle a wide-area node.
<li> You may not reboot or power cycle a wide-area node. However, you
<em>may</em> reboot the virtual node in which you are running.
<li> There is no root access for experimentors.
<li> There is no root access for experimentors, except when running
inside a virtual node (jail on FreeBSD, vservers on PLab nodes).
<li> You may not select the OS; all wide-area nodes run the
same version of FreeBSD (currently 4.6 or later).
<li> RPM and tarball installs are not supported; you need to copy over
and install your software on your own.
same version of FreeBSD (currently 4.6 or later) and Linux on PLab
nodes.
<li> There is no NFS access to your files on <tt>users.emulab.net</tt>.
Instead, we provide access via the
<a href=http://www.fs.net>Self-certifying File System.</a>
<a href=http://www.fs.net>Self-certifying File System on FreeBSD
nodes. There is no remote file access on PLab nodes.
<li> Traffic generators and program objects are not available on
widearea nodes. More generally, anything requiring the event
system for its control plane is not available. We hope to have
the event system working in the widearea real soon now ...
</ul>
......@@ -49,21 +59,24 @@ wide-area nodes:
<ul>
<li> You can let the system choose a completely random set:
<code><pre>
tb-set-hardware $nodea pcRemote </code></pre>
tb-set-hardware $nodea pcvwa
tb-set-hardware $nodea pcplab </code></pre>
<li> You can select a particular node by choosing a virtual node
on that node. To aid in that selection, you can use our
<a href="https://www.emulab.net/widearea_info.php3">wide-area
<li> You can select a particular node by choosing the physical
node, and using the "fix-node" directive. A free virtual node on
that physical node will be choosen for you. To aid in that
selection, you can use our
<a href="https://www.emulab.net/widearea_info.php3">wide-area
info</a> table to determine the bandwidth and latency
characteristics of the widearea nodes. For example:
characteristics of widearea nodes.
<a href="https://www.emulab.net/plabmetrics.php3">PlanetLab node
metrics</a> are also available. For example:
<code><pre>
tb-fix-node $nodea vwa35-4 </code></pre>
tb-fix-node $nodea ron10 </code></pre>
At present there is a fixed number of virtual nodes per wide-area
node. To determine which virtual nodes are free for use, please
consult the
<a href="https://www.emulab.net/nodecontrol_list.php3?showtype=virtnodes">
reservations table</a>.
At present there are a fixed number of virtual nodes per wide-area
node. If there are no free virtual nodes on the physical node you
have choosen, the experiment will fail to map.
<li> Lastly, you can let the system choose the most approriate
set of virtual nodes for your toplogy. The system will look at
......@@ -73,33 +86,31 @@ wide-area nodes:
<code><pre>
set v0 [$ns node]
set v1 [$ns node]
tb-set-hardware $v0 pcRemote
tb-set-hardware $v1 pcRemote
tb-set-hardware $v0 pcvwa
tb-set-hardware $v1 pcvwa
set l0 [$ns duplex-link $v0 $v1 10Mb 45ms DropTail] </code></pre>
If you use this method, an overlay network will be created for
you so that you can treat your wide-area nodes just like local
nodes with respect to network interfaces. In the above example,
IP addresses 10.1.1.1 and 10.1.1.2 will be assigned to ends of
the link, and an overlay will be created between the physical
nodes so that things like "ping 10.1.1.2" will work normally.
Or, you can elect to ignore the overlays we have created for you
and use the IP addresses of the physical nodes. You can also
create a link between a wide-area node and a local node; an
overlay link will be established for this connections as
well. Note that overlays are currently implemented using the <a
href=http://vtun.sourceforge.net>vtun package</a> (UDP mode, no
compression, no encryption). We plan to switch to ipsec in the
future.
If you use this method, an optional overlay network can be
created for you so that you can treat your wide-area nodes just
like local nodes with respect to network interfaces. However,
this only works on the FreeBSD based pcvwa nodes. The PlanetLab
nodes do not support overlay networks. For example:
<code><pre>
tb-set-usewatunnels 1 </code></pre>
In the above example, IP addresses 10.1.1.1 and 10.1.1.2 will be
assigned to ends of the link, and an overlay will be created
between the physical nodes so that things like "ping 10.1.1.2"
will work normally. Or, you can elect to ignore the overlays we
have created for you and use the IP addresses of the physical
nodes. You can also create a link between a wide-area node and a
local node; an overlay link will be established for this
connections as well. Note that overlays are currently implemented
using the
<a href=http://vtun.sourceforge.net>vtun package</a> (UDP mode, no
compression, <b>no</b> encryption).
</ul>
<li> Traffic generation via the TG tool set is available on wide-area
nodes just like it is on local nodes. You may also set up traffic
generators between local and wide-area nodes. Traffic generation
is discussed in more detail in the
<a href="docwrapper.php3?docname=advanced.html">advanced
tutorial</a>.
<li> Routing support within experiments that use wide-area nodes with
overlay links (see above) is also available. While we do not
support NS' <code>Session</code> option when your experiment uses
......@@ -120,7 +131,7 @@ wide-area nodes:
<code><pre>
set v0 [$ns node]
set n0 [$ns node]
tb-set-hardware $v0 pcRemote </code></pre>
tb-set-hardware $v0 pcvwa </code></pre>
Then you will be assigned one local node and one wide-area node.
If you want to establish network connections between these two nodes,
......@@ -143,7 +154,8 @@ wide-area nodes:
nodes if your project leader has approved you with root
permissions).
<li> Remote file access to your account on <tt>users.emulab.net</tt>
<li> Remote file access (pcvwa FreeBSD nodes only) to your account on
<tt>users.emulab.net</tt>
is currently provided via the <a href=http://www.fs.net>Self-certifying
File System (SFS).</a> Much like ssh, SFS requires distribution
of your <a href="https://www.emulab.net/showsfskeys.php3">sfs
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment