Changes between Version 10 and Version 11 of FeddUsersGuide

Timestamp:

May 20, 2014 3:20:00 PM (11 years ago)

Author:

faber

Comment:

--

FeddUsersGuide

@@ -60 +60 @@
 The this layout connects 2 experiment on DETERLab.  This is because the testbeds are all prefixed with the {{{deter}}} testbed name.  The ''testbed''/''sub-testbed'' syntax allows multiple instantiations of experiments on the same testbed.  This layout creates 2 experiment on DETERLab (DETERLab's [NewFeddAbout#TheExperimentController experiment contoller] maps the {{{deter}}} testbed name to DETERLab).
 
-To create the federated experiment, execute the following command on {{{users.isi.deterlab.net}}}:
+To create the federated experiment, execute the [FeddCommands#fedd_create.py fedd_create.py] command on {{{users.isi.deterlab.net}}}:
 
 {{{
@@ -82 +82 @@
 Assuming that {{{status}}} is {{{starting}}} the experiment is being created.  If there has been a error, there will be an error message as well.
 
-At any time a user can poll the current status of their federated experiment using the {{{fedd_multistatus.py}} command.  Run it like this on {{{users.isi.deterlab.net}}} and you should see similar output:
+At any time a user can poll the current status of their federated experiment using the [FeddCommands#fedd_multistatus.py fedd_multistatus.py] command.  Run it like this on {{{users.isi.deterlab.net}}} and you should see similar output:
 
 {{{
@@ -105 +105 @@
 }}}
 
-A user can certainly use the fedd_multistatus.py command to poll and monitor experiment creation, but output is fairly terse and polling is inefficient.  The {{{fedd_spewlog.py}}} command will output a debugging log from the experiment controller.  If the experiment is being created or terminated, the command puts out the log so far and continues updating it until the operation succeeds or fails.  A user can follow the progress of the creation in real time using this command.
+A user can certainly use the fedd_multistatus.py command to poll and monitor experiment creation, but output is fairly terse and polling is inefficient.  The [FeddCommands#fedd_spewlog.py fedd_spewlog.py] command will output a debugging log from the experiment controller.  If the experiment is being created or terminated, the command puts out the log so far and continues updating it until the operation succeeds or fails.  A user can follow the progress of the creation in real time using this command.
 
 
@@ -172 +172 @@
 == Examining the Federated Experiment ==
 
-To gather detailed information about how the system has created the experiment, use the {{{fedd_ftopo.py}}} command (ftopo is short for "federated topology").  Here's a sample invocation; again the {{{--experiment_name}}} parameter is the shorthand name returned by {{{fedd_create.py}}} or picked from {{{fedd_multistatus.py}}}.
+To gather detailed information about how the system has created the experiment, use the [FeddCommands#fedd_ftopo.py fedd_ftopo.py] command (ftopo is short for "federated topology").  Here's a sample invocation; again the {{{--experiment_name}}} parameter is the shorthand name returned by {{{fedd_create.py}}} or picked from {{{fedd_multistatus.py}}}.
 
 {{{
@@ -275 +275 @@
 Similar work can be done to present unified login information and shared filesystems.  That is not done in this case because the experiments are both in the same DETER project and testbed.
 
+== Releasing Resources ==
+
+When the federated experiment is no longer needed, the [FeddCommands#fedd_terminate.py fedd_terminate.py] command is used to release resources.  Individual testbeds release resources and the experiment controller purges all its data.  To release the experiment above:
+
+{{{
+users:~$ fedd_terminate.py --experiment_name fed1
+}}}
+
+The command does not return until the individual testbeds have released their resources.
+
+The {{{--force}}} parameter can be used to terminate experiments that are not in the {{{active}}} state, or that have other problems.
+
+
+