Changes between Version 10 and Version 11 of FeddUsersGuide


Ignore:
Timestamp:
May 20, 2014 3:20:00 PM (5 years ago)
Author:
faber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FeddUsersGuide

    v10 v11  
    6060The 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).
    6161
    62 To create the federated experiment, execute the following command on {{{users.isi.deterlab.net}}}:
     62To create the federated experiment, execute the [FeddCommands#fedd_create.py fedd_create.py] command on {{{users.isi.deterlab.net}}}:
    6363
    6464{{{
     
    8282Assuming that {{{status}}} is {{{starting}}} the experiment is being created.  If there has been a error, there will be an error message as well.
    8383
    84 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:
     84At 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:
    8585
    8686{{{
     
    105105}}}
    106106
    107 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.
     107A 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.
    108108
    109109
     
    172172== Examining the Federated Experiment ==
    173173
    174 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}}}.
     174To 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}}}.
    175175
    176176{{{
     
    275275Similar 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.
    276276
     277== Releasing Resources ==
     278
     279When 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:
     280
     281{{{
     282users:~$ fedd_terminate.py --experiment_name fed1
     283}}}
     284
     285The command does not return until the individual testbeds have released their resources.
     286
     287The {{{--force}}} parameter can be used to terminate experiments that are not in the {{{active}}} state, or that have other problems.
     288
     289
     290