Commit 84032a78 authored by Jay Lepreau's avatar Jay Lepreau

missing <p> separators. new plab support address.

parent 927a2f88
<!--
EMULAB-COPYRIGHT
Copyright (c) 2003 University of Utah and the Flux Group.
Copyright (c) 2003-2004 University of Utah and the Flux Group.
All rights reserved.
-->
<center>
......@@ -27,7 +27,9 @@ actually instantiated on any nodes). It will also show you which nodes were
allocated to you, and perform operations on these nodes such as rebooting them.
Rebooting a sliver kills off all processes running on it, and re-runs the
Emulab sliver setup code (including your startup command if you supplied one.)
</p>
<p>
For your convenience, we set up DNS names for all of the nodes in your slice -
each sliver can be addressed like
<code>&lt;node&gt;.&lt;exp&gt;.&lt;proj&gt;.emulab.net</code>, where:
......@@ -35,7 +37,9 @@ each sliver can be addressed like
form, the names will be 'node-N', starting with 'node-1', up to the number of
nodes in your slice). <code>exp</code> is the name of your experiment (same as
the slice name) and <code>pid</code> is the name of your project on Emulab.
</p>
<p>
Unlike 'raw' PlanetLab slices, you log into an Emulab-created slice using your
own (Emulab) username. To do this, all of the slivers in your slice run their
own <code>sshd</code>, which must be run on a non-standard port so that it
......@@ -44,6 +48,7 @@ your slice's <code>sshd</code>s are listed in the experiment creation mail. For
interactive use, there are links on the experiment page to <code>ssh</code>
(with a helper application, linked from the column header) using the correct
hostname, correct port number, etc.
</p>
<h3>Getting More Advanced</h3>
......@@ -53,7 +58,9 @@ slice. But what if you want to do something more fancy, like ask for 10 nodes
inside North America, and 10 outside? Or run a certain command, on startup, only
on one of your nodes? Well, luckily, there's a lot more power to the
specification interface than what you see on the 'EZ' pages.
</p>
<p>
What's going on behind the scenes here is that Emulab actually takes as input
an NS file - a very similar file to the one used for the NS network simulator.
The 'EZ' forms are generating an NS file for you, but, of course, you can write
......@@ -62,7 +69,9 @@ on 'View NS File' to view (and/or save) a copy of the generated NS file. You
can then use this (very commented) file as a starting point for creating your
own, more complicated file. You can then submit this file to the
'Begin/Advanced Experiment' page.
</p>
<p>
The Emulab documentation covers the parts of NS that are and are not supported,
and Emulab's own extensions to the language.
......@@ -76,11 +85,13 @@ toggle the interface view you get.
<h3>Where Should I Look for Help?</h3>
When using our interface to PlanetLab, there two different entities responsible
When using our interface to PlanetLab, there are two different entities responsible
for support: us and the PlanetLab team. Each is responsible for a different
part of the system you are using. So, below are some guidelines on which types
of questions/problems should be addressed to who.
</p>
<p>
In an emergency, such as being unable to create a slice with a deadline
looming, you can try asking both places at once. However, under normal
circumstances, we suggest trying one at a time.
......@@ -99,14 +110,13 @@ circumstances, we suggest trying one at a time.
<li>Problems with accounts created for you on your PlanetLab slice, such as
being unable to log in or use sudo.</li>
</ul>
<h4>Questions for which the answer may be on
<a href="http://www.planet-lab.org">the PlanetLab site</a>,
<h4>Questions for which the answer may be on the
<a href="http://www.planet-lab.org">PlanetLab site</a>,
or should go to
<a href="mailto:planetlab-support@lists.sourceforge.net">
planetlab-support@lists.sourceforge.net</a>:
<a href="mailto:support@planet-lab.org">
support@planet-lab.org</a>:
</h4>
<ul>
<li>Questions about the kernels and other software on PlanetLab nodes.</li>
......
Markdown is supported
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