Changes between Version 2 and Version 3 of TIEDClearinghouse


Ignore:
Timestamp:
06/30/09 17:20:35 (10 years ago)
Author:
faber@isi.edu
Comment:

Checkpoint

Legend:

Unmodified
Added
Removed
Modified
  • TIEDClearinghouse

    v2 v3  
    1010This page outlines those services and how an experimenter can make use of them.  Most of these services are provided to one extent or another by DETER's [http://fedd.isi.deterlab.net fedd] software.  We [wiki:TIEDFeddMapping describe] the mapping to fedd as well.
    1111
    12 == User Registration ==
     12== Experimenter Registration ==
    1313
    1414TIED 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.
     
    1616== Slice Management ==
    1717
    18 For TIED, slice management is the creation and manipulation of experiments that span multiple facilities.  One can think of the facilities as aggregates, each of whaich controls access to a set of resources.  Currently TIED supports creation of slices across testbeds with an Emulab interface and that run instances of [http://fedd.isi.deterlab.net fedd] that act as aggregate managers.
     18For TIED, slice management is the creation and manipulation of experiments that span multiple facilities.  One can think of the facilities as aggregates, each of whaich controls access to a set of resources.  Currently TIED supports creation of slices across testbeds with an Emulab interface and that run instances of [http://fedd.isi.deterlab.net fedd] that act as aggregate managers.  In addition ti the experimenter interface to slices, TIED provides interfaces that allow experimental tools to be used in the slice.
     19
     20== Component/Aggregate Management ==
     21
     22The TIED clearinghouse manages the access control of multiple sites as aggregates.  It provides a unified access control model across aggregates and provides a unified interface for alloacting resources from them.  Currently Emulab-based testbeds are used as aggregates, but development is underway to access other systems through the same interfaces.
     23
     24== Experiment Tools ==
     25
     26Most tools that use the Emulab testbed interfaces can be seamlessly used on TIED slices.  In particular the DETER [http://seer.isi.deterlab.net SEER] tool can be used to transparently manipulate experiments inside TIED slices.
     27
     28= Using the TIED Clearinghouse =
     29
     30This brief tutorial will show how to register with TIED, create a slice, connect to it using SEER, and finally to terminate the slice.
     31
     32== Registering with TIED ==
     33
     34Registering with TIED is a two phase process.  An experimenter first joins a DETER project that is set aside for TIED/GENI users, and then [http://fedd.isi.deterlab/net fedd] is configured with the additional attributes that allow slice operation.  The experimenter sees only the step of joining the DETER group.
     35
     36Joining the TIED project on DETER is just like joining a project on any Emulab-based testbed.  If you are a DETER user, just log in and choose "Join an Existing Project" from the Experimentation menu.  If not the detailed instructions follow.
     37
     38Connect to http://www.isi.deterlab.net and click on the "Request Account" button and from the next screen the "Join an Existing Project" link.  Fill out the form as instructed and be sure to enter "TIED" in the "Project Name" field.  Shortly the TIED staff will approve you as a TIED member and also add appropriate configuration to the slice management portion of fedd to allow you to create slices.  You will receive two e-mail messages, one stating you've been approved in the TIED group and one indicating that you've been granted the authority to create slices.  Once you have received both messages, you can create slices.
     39
     40(Incidentally, you also have a fully functional DETER account.)
     41
     42== Slice Management ==
     43
     44TIED 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