Skip to content
GitLab
Menu
Projects
Groups
Snippets
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
emulab
emulab-devel
Commits
9a979522
Commit
9a979522
authored
Sep 11, 2003
by
Mike Hibler
Browse files
Entry for queueing interactive experiments
parent
1d0420cb
Changes
2
Hide whitespace changes
Inline
Side-by-side
www/faq.html
View file @
9a979522
...
...
@@ -35,6 +35,8 @@
<li>
<a
href=
"#UTT-TOPO"
>
Are there any constraints on my topology?
</a>
<li>
<a
href=
"#UTT-NODES"
>
How many nodes can I ask for?
</a>
<li>
<a
href=
"#UTT-HOWLONG"
>
How long can I keep using my nodes?
</a>
<li>
<a
href=
"#UTT-QUEUE"
>
I only need a couple of nodes but none are
free, should I just keep trying?
</a>
<li>
<a
href=
"#UTT-TOOFEW"
>
What if I need more nodes than are free?
</a>
<li>
<a
href=
"#UTT-2"
>
Do I get root access on my nodes?
</a>
<li>
<a
href=
"#UTT-3"
>
Do my nodes have consoles I can look at?
</a>
...
...
@@ -417,6 +419,34 @@
is important to leave as many nodes available as possible.
</p>
<li><a
NAME=
"UTT-QUEUE"
></a>
<font
size=
'+1'
><b>
I only need a couple of nodes but none are free,
should I just keep trying?
</b></font>
<p>
It is better for you and us if you don't just keep hitting the
submit button 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>
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>
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.
</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>
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>
<li><a
NAME=
"UTT-TOOFEW"
></a>
<font
size=
'+1'
><b>
What if I need more nodes than are free?
</b></font>
<p>
...
...
www/tutorial/tutorial.html
View file @
9a979522
...
...
@@ -981,6 +981,12 @@ regular experiment and a batch mode experiment:
</ul>
<p>
The batch system may also be used for "queuing" interactive experiments.
By leaving out
<tt>
tb-set-node-startcmd
</tt>
commands, an experiment
will be started when enough nodes are available, but then remain active
until you (or the system) swap or terminate it.
<p>
<li>
<a
NAME=
"BatchExample"
></a>
<h3>
A Batch Mode Example
</h3>
...
...
Write
Preview
Supports
Markdown
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment