Changes between Version 8 and Version 9 of TIEDClearinghouse


Ignore:
Timestamp:
06/30/09 22:06:45 (10 years ago)
Author:
faber@isi.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TIEDClearinghouse

    v8 v9  
    5050The image is of the logical slice topology, it does not indicate which aggregates donated which nodes.  The master testbed column indicates which testbed is exporting its user environment into the experiment.  For TIED slices, this will usually be the DETER testbed.  The project column will be TIED for TIED experimenters; it indicates that the DETER TIED project is being exported into the slice.  The name of the slice is a mnemonic name attached to the slice.  It also has a [http://fedd.isi.deterlab.net/trac/wiki/FeddAbout#GlobalIdentifiers:Fedids fedid] this is not visible from this interface.  Finally there are buttons to create or terminate this slice, active based on the current status of the slice.
    5151
    52 One can create a slice either by activating one of the existing slice descriptions, which will create the slice based on its last configuration, or by going directly to the [https://www.isi.deterlab.net/fedd_create.php3 slice creation page] and providing a slice description. Slice descriptions are written in a modified ns2 language, extended to describe the embedding of nodes in the various aggregates.  The language is [http://fedd.isi.deterlab.net/trac/wiki/FeddAbout#ExperimentDescriptions briefly described] in the fedd documentation.  The configuration file used to describe each of the examples on [ttps://www.isi.deterlab.net/fedd_list.php3 the slice listing page] is available from that page as a starting point.
     52=== Creation ===
     53
     54One can create a slice either by activating one of the existing slice descriptions, which will create the slice based on its last configuration, or by going directly to the [https://www.isi.deterlab.net/fedd_create.php3 slice creation page] and providing a slice description and a name. Slice descriptions are written in a modified ns2 language, extended to describe the embedding of nodes in the various aggregates.  The language is [http://fedd.isi.deterlab.net/trac/wiki/FeddAbout#ExperimentDescriptions briefly described] in the fedd documentation.  The configuration file used to describe each of the examples on [https://www.isi.deterlab.net/fedd_list.php3 the slice listing page] is available from that page as a starting point.
     55
     56Giving a slice a new name will create a new slice, specifying an existing name will overwrite an inactive slice.
     57
     58[[Image(screen4.png)]]
    5359
    5460Fedd's documentation on [http://fedd.isi.deterlab.net/trac/wiki/FeddAbout#Experiments experiment creation] provides detail on how experiments are created from the description.  In reading that document from a GENI perspective, it helps to think of experiments as slices and testbeds as aggregates (the aggregate interface is provided by fedd).
    5561
     62=== Termination ===
    5663
     64The simplest way to return a slice's resources is to use the terminate button from [https://www.isi.deterlab.net/fedd_list.php3 the slice listing page], which is active when a slice is active.  Only the experimenter who created the slice can delete it from the web interface, though the command line interface is more versatile.  Alternatively, one can terminate a slice from the [https://www.isi.deterlab.net/fedd_terminate.php3 termination page], where one must type the slice name by hand.
    5765
     66=== Slice Status ===
     67
     68Both the creation and termination pages give the experimenter an indication that their slice operation has begun, but do not provide ongoing updates on the status of that operation.  Creation can be a lengthy process, especially if there are allocation or configuration errors in aggregates.  Currently the only way to track progress of a slice creation is through [https://www.isi.deterlab.net/fedd_list.php3 the slice listing page].  This is an area of ongoing improvement.
     69
     70=== DETER resources in the slice ===
     71
     72Access to the slice is through the DETER TIED account and the resources allocated on the DETER testbed.  Those resources will be housed in an DETER experiment with the same name as the slice created.  Information on the nodes allocated is available from the MyDETERLab selection from the experimentation interface when logged on to [https://www.isi.deterlab/net the DETER web site].  An experimenter can access the allocated nodes on DETER and through them into the rest of the slice.  The Emulab event system and SEER provide simpler ways of reaching into the slice.
     73
     74== Experiment Tools ==
     75