Project Number
1609
Project Title
TIED: Trial Integration Environment in DETER
a.k.a. DETER
Technical Contacts
Principal Investigator: John Wroclawski jtw@isi.edu
Co-Principal Investigator: Terry Benzel tbenzel@isi.edu
Ted Faber faber@ISI.EDU
Participating Organizations
- University of Southern California Information Sciences Institute, Marina del Rey
- University of California, Berkeley
Scope
The scope of work on this project is to develop and evangelize a control framework that particularly emphasizes usability across different communities, through federation, rich trust/security models, and similar enabling mechanisms.
Milestones
Spiral 1
- TIED: S1.a Identify specific year 1 outreach communities. (Due 01/01/09 (late))
- TIED: S1.b Initial component and clearinghouse documentation. (Completed late 07/17/09)
- TIED: S1.c Release v 0.1 of component manager and clearinghouse. (Completed late 07/02/09)
- TIED: S1.d Begin prototype clearinghouse operation. (Completed late 07/17/09)
- TIED: S1.e Provide user access to DETER via TIED. (Due 05/01/09 (late))
- TIED: S1.f Participate in NSF TRUST Science and Technology Center's teacher education program. (Due 09/01/09 (late))
- TIED: S1.g Demonstrate extended functionalities for outreach communities. (Due 09/30/09 (late))
- TIED: S1.h Provide direct VLAN interface to TIED resources (Due 09/30/09 (late))
- TIED: S1.i Support running federated experiments. (Due 09/30/09 (late))
Spiral 2
- TIED: S2.a Design specification for plugin (Due 01/30/10 (late))
- TIED: S2.b TIED GEC demo (Due 03/16/10 (late))
- TIED: S2.c Fedd release with ProtGeni plug-in (Due 06/30/10 (late))
- TIED: S2.d Preliminary design document for Unified/SFA (GENIAPI) plugin (Due 07/30/10)
- TIED: S2.e review S2.f milestone and revise if necessary (Due 08/15/10)
- TIED: S2.f Demo TIED/GENIAPI Experiment (Due 09/30/10)
Project Technical Documents
TIED is based on the TIED/DETER federation system, which allows a researcher to construct experiments that span testbeds by dynamically acquiring resources from other testbeds and configuring them into a single experiment. As closely as possible that experiment will mimic a single DETER/Emulab experiment.
This model fundamentally supports creation of cohesive experiments (slices) from independently administered resources (components/aggregates). Because resources are independently administered and serve different communities, the authorization system needs to support a rich delegation structure, formal semantics, efficient negotiation, and clear auditing. The ABAC system meets those requirements; TIED is integrating this into the federation system.
To make use of widely distributed components it is helpful to establish guaranteed network connections between them. TIED is addressing this by federating with testbeds that represent dynamically allocatable wide-area network resources. The prototyping plan is to use DRAGON interfaces to configure these resources.
- The TIED/DETER Federation architecture and implementation
- Information about the TIED/DETER federation system, including overview, detailed user and developer documentation, pointers to published papers, and released code.
- The TIED Clearinghouse
- Description of how the TIED stsyem provides GENI clearinghouse functionality, including how to join
- The ABAC model in TIED
- Discussion of ABAC concepts and how they relate to TIED implementation
- An ABAC demo
- A worked example of ABAC applied to a GENI scenario. Also shows the TIED attribute explorer.
- ProtoGENI Plug-in
- A description of the design for the upcoming TIED/ProtoGENI subsystem.
- Release of fedd 3.00
- Release of fedd that includes the ProtoGENI plugin (as per milestone S2.c). It also includes information for developers who want to write their own plug-ins.
Quarterly Status Reports
Spiral 1 Connectivity
TBD
GPO Liaison System Engineer
Heidi Picher Dempsey hdempsey@geni.net
