Commit 53e7acc7 authored by jessem's avatar jessem

testing_php_include_with_docwrapper

parent d8443aa2
<!--
EMULAB-COPYRIGHT
Copyright (c) 2000-2003 University of Utah and the Flux Group.
All rights reserved.
-->
<a NAME="Beginning"></a>
<h3>Beginning an Experiment</h3>
<p>
After logging on to the Emulab Web Interface, choose the "Begin
Experiment" option from the menu. First select which project you want
the experiment to be configured in. Most people will be a member of just
one project, and will not have a choice. If you are a member of
multiple projects, be sure to select the correct project from the
menu.
<p>
Next fill in the `Name' and `Description fields. The Name should be a
single word (no spaces) identifier, while the Description is a multi
word description of your experiment. In the "Your NS file" field,
place the <i>local path</i> of a NS file which you have created to
describe your network topology. This file will be uploaded through
your browser when you choose "Submit."
<p>
In submitting a topology, you can ask for as many nodes as are currently available. You can
click on the "Node Reservation Status" link at your left to see
how many nodes are currently free. If you ask for more than are
currently available, your experiment will be rejected (you
will receive email notification shortly after you submit your NS
file to the web interface).
</p>
<p>
<em>We urge all new Emulab users to begin with a small 3-4 node
experiment so that you will become familiar with NS syntax and the
practical aspects of Emulab operation.</em>
</p>
<p>
After submission, Emulab will begin processing your
request. This will likely take several minutes, depending on how large
your topology is, and what other features (such as delay nodes and
bandwidth limits) you are using. Assuming all goes well, you will
receive an email message indicating success or failure, and if
successful, a listing of the nodes and IP address that were allocated
to your experiment.
<p><h3>Problem?</h3>
If your submission fails because there are not enough nodes available, do not repeatedly re-submit
the experiment every few minutes. It wastes your time and floods
us with email (we get every failure message you do!)
Instead, you can now use the
<a href="tutorial/tutorial.php3#BatchMode">Batch System</a> <!-- bad link -->
to queue an interactive job. By submitting your experiment as
a batch job, but without any
<a href="tutorial/tutorial.php3#Startupcmd"><tt>tb-set-node-startcmd</tt></a> <!-- bad link? -->
directives in your NS file, the job will be queued until nodes are
available. For most experiments, this means just using your regular
NS file, and checking the Batch Mode Experiment box when you create
the experiment. <b>Note:</b> if your experiment requires a large proportion
of the total Emulab nodes, you likely require <A HREF="mailto:testbed-ops@flux.utah.edu">Testbed Operations intervention</A>
to get your experiment off the ground.
</p><p>
When your queued job is swapped in, you will be sent email to
inform you, and you can start working!
<b>Please note</b> that the
experiment will be idle when it is swapped in, and will be
<a href="swapping.html#idleswap">idle swapped</a> <!-- bad link -->if you do not
get things running on the nodes in a short period of time. If your
experiment does get swapped out before you can get to it, you can
always visit the experiment's information page and try again by
using the Queue Batch Experiment menu item.
</p>
<!--
EMULAB-COPYRIGHT
Copyright (c) 2000-2003 University of Utah and the Flux Group.
All rights reserved.
-->
<a NAME="Beginning"></a>
<h3>Experiments: Swapping</h3>
<a name="swapping"></a>
<p>
Swapping is the process of instantiating your experiment,
i.e., allocating nodes, configuring links, etc. It also refers
to the reverse process, in which nodes are released. These are
called "swapping in" and "swapping out" respectively. Swapping is when you (or
we, or the Emulab system) temporarily swaps
out your experiment,
releasing all of the nodes in the experiment. Your experiment is
still resident in the Emulab database, and you can see its status
in the web interface, but no nodes are allocated.
</p>
<P>In general, you should do your work, and then
terminate your experiment as soon as you're done with it. If
you're not done with it, but are through for a while, you should
probably "swap out" your experiment It is
especially important to swap out your experiment if you're through
with it for the weekend. Emulab usually gets heavy use on the
weekends by users who need to make very large experiments, so it
is important to leave as many nodes available as possible.
</p>
<p>
<b>Caution</b>: Be aware that we do not currently save any files that you
may have
placed on your nodes. When your experiment is swapped back in, you
will likely get different nodes, with fresh copies of the disk
images. For that reason, you should not swap your experiment out
unless you make arrangements to save and restore any state you need.
</p>
<p>Once an
experiment is swapped out, you can swap it back in via the web
interface by going to the Experiment Information page for your
experiment, and clicking on the swapin option. See the Project File Storage
module for more information <!-- link here --></p>
<p>You will sometimes
notice that the Experiment Information page does not contain the swap
link. That is because experiments cannot be swapped when they are in
transition. For example, when the experiment is being swapped in (say,
after first being created) the link will disappear until the experiment
is fully swapped in, and it is capable of being swapped out. You will
need to occasionally reload the page so that the updated state is
recognized and the swap link appears. </p>
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