Changes between Version 1 and Version 2 of TIEDClearinghouse

06/30/09 14:47:25 (13 years ago)



  • TIEDClearinghouse

    v1 v2  
    55 * Experimenter Registration
    66 * Slice Management
     7 * Aggregate Management
     8 * Experimental tools
    8 This page outlines those services and how an experimenter can make use of them.
     10This 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 [ fedd] software.  We [wiki:TIEDFeddMapping describe] the mapping to fedd as well.
    1012== User Registration ==
    1214TIED 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 [ 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 [ 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.
     16== Slice Management ==
     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 [ fedd] that act as aggregate managers.