Changes between Version 17 and Version 18 of TIEDClearinghouse


Ignore:
Timestamp:
07/01/09 17:16:18 (10 years ago)
Author:
faber@isi.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TIEDClearinghouse

    v17 v18  
    1212== Experimenter Registration ==
    1313
    14 TIED currently makes access control decisions based on both the identity of a user and on the attributes that TIED knows about the user.  The user's identity is encoded in a [http://fedd.isi.deterlab.net/trac/wiki/FeddAbout#GlobalIdentifiers:Fedids fedid], the TIED version of a GENI ID.  A fedid can be created by any user using standard SSL commands, but the advantage of using the TIED experimenter registry is that it binds additional information to that identity.  Specifically, this creates a [http://fedd.isi.deterlab.net/trac/wiki/FeddAbout#GlobalIdentifiers:Three-levelNames three-level name] for the experimenter.  This allows the TIED federation daemon to negotiate different levels of access with the aggregates with which the TIED clearinghouse federates.
     14TIED currently makes access control decisions based on both the identity of a user and on the attributes that TIED knows about the user.  The user's identity is encoded in a [http://fedd.isi.deterlab.net/trac/wiki/FeddAbout#GlobalIdentifiers:Fedids fedid], the TIED version of a GENI ID.  A [http://fedd.isi.deterlab.net/trac/wiki/FeddConfig#MakingaFedidCertificate fedid can be created by any user using standard SSL commands], but the advantage of using the TIED experimenter registry is that it binds additional information to that identity.  Specifically, this creates a [http://fedd.isi.deterlab.net/trac/wiki/FeddAbout#GlobalIdentifiers:Three-levelNames three-level name] for the experimenter.  This allows the TIED federation daemon to negotiate different levels of access with the aggregates with which the TIED clearinghouse federates.
    1515
    1616== Slice Management ==
     
    4444== Slice Management ==
    4545
     46TIED's slice management features can be accessed through a simple web interface that makes common actions straightforward, and a command line interface that is more expressive for users with sophisticated needs.  We expect that the web interface is sufficient for many early adopters.  Both interfaces are undergoing development
     47
     48=== Using the Web Interface ===
     49
    4650TIED keeps a record of slices and allows users to recreate them or terminate running ones through a web interface.  The current list is available from https://www.isi.deterlab.net/fedd_list.php3 (you must be logged in using your TIED account to view this page).  An example is below.
    4751
     
    5054The 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.
    5155
    52 === Creation ===
     56==== Creation ====
    5357
    5458One 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.
     
    6064Fedd'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).
    6165
    62 === Termination ===
     66==== Termination ====
    6367
    6468The 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.
    6569
    66 === Slice Status ===
     70==== Slice Status ====
    6771
    6872Both 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.
    6973
     74=== Using the Command-line Interface ===
     75
     76Creating, terminating and accessing information about the slice can be done through the [http://fedd.isi.deterlab.net/trac/wiki/FeddDevelop published fedd interfaces] accessible through the command line using the [http://fedd.isi.deterlab.net/trac/wiki/FeddCommands#Fedd_client.py fedd_client.py program].
     77
     78Replicating the detailed information at [http://fedd.isi.deterlab.net/trac/wiki/FeddCommands#Fedd_client.py the link above] unnecessary, but it is worth noting that one creates a slice using '''create''', terminates a slice using '''terminate''' and that there is a range of information available about a slice using the other informational requests.  Of particular interest are the '''image''' and '''ns_image''' commands that produce graphical representations of the topologies of either an existing slice or a slice description file.
     79
     80All of these commands can be run from `users.isi.deterlab.net` and will use the experimenter's default GID/fedid by default.  Using the command line interface allows more fine-grained control of slice management functions.  Specifically, by capturing an experiment capability using the '''--experiment_cert''' parameter to '''create''' and the '''--experiment_file''' parameters to information and '''terminate''' commands, the creator of the slice can allow others to manipulate the slice.
     81
     82When using the command line, be sure to use the '''--url='''''!https://users.isi.deterlab.net:23235'' parameter.
     83
     84Not all actions taken through the command line interface are reflected in the web interface.
     85
     86
    7087=== DETER resources in the slice ===
    7188
    72 Access 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.
     89Regardless of how it is created, access 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.
    7390
    7491== Experiment Tools ==