Version 11 (modified by 14 years ago) (diff) | ,
---|
Project Number
1743
Project Title
Integrating New Projects into the ProtoGENI Control Framework
a.k.a. PGINTEGRN
Technical Contacts
Principal Investigator John Regehr regehr@cs.utah.edu
Co-PI Robert Ricci ricci@cs.utah.edu
Participating Organizations
University of Utah, School of Computing
50 S. Central Campus Dr. Rm. 3190
Salt Lake City, UT 84112
GPO Liaison System Engineer
Vic Thomas vthomas@geni.net
Scope
This effort will integrate additional projects with the ProtoGENI control framework (Cluster C). This work will support the activities of the Utah ProtoGENI team toward this goal. This proposal will provide new Cluster C projects with the software, standards, and technical assistance required to integrate their projects into the ProtoGENI control framework, and to refine the design of ProtoGENI to make smooth integration possible. These projects span a wide range of the GENI ecosystem, including international collaboration, instrumentation and measurement, hybrid environments involving multiple network technologies, early experiments, and aggregate deployments of sliceable networks, routers, storage, and hosts. The project will also support researchers running experiments on ProtoGENI.
Current Capabilities
BRIEF descriptions of resources/functions/tools that are available to anyone in the GENI community
Milestones
MilestoneDate(PGINTEGRN: S2.a API document)? Component Manager API document (Version 2)
MilestoneDate(PGINTEGRN: S2.b RSpec extension spec)? RSpec extension specification
MilestoneDate(PGINTEGRN: S2.c Reference Component Manager)? Reference Component Manager implementation
MilestoneDate(PGINTEGRN: S2.d Experimenters guide)? Guide for experimenters using ProtoGENI
MilestoneDate(PGINTEGRN: S2.e Service implementer's guide)? Guide for projects implementing services on ProtoGENI
MilestoneDate(PGINTEGRN: S2.f API document)? Component Manager API document (Version 3)
MilestoneDate(PGINTEGRN: S2.g Reference Component Manager)? Updated reference Component Manager implementation
MilestoneDate(PGINTEGRN: S3.a API for AM<->AM coordination during stitching)?
MilestoneDate(PGINTEGRN: S3.b Implement AM <-> AM coordination API)?
MilestoneDate(PGINTEGRN: S3.c Update ProtoGENI SA and Clearinghouse/Registry APIs)?
MilestoneDate(PGINTEGRN: S3.d Export more operational information to GMOC)?
MilestoneDate(PGINTEGRN: S3.e Add root CAs to trust all other GENI clearinghouses)?
Project Technical Documents
Component/Aggregate Manager API document
RSpec Specification
Quarterly Status Reports
2Q2010 report
April 2011 report
Spiral 2 Connectivity
Links to wiki pages about details of infrastrcture that the project is using (if any). Examples include IP addresses, hostnames, URLs, DNS servers, local site network maps, VLANIDs (if permanent VLANs are used), pointers to public keys. GPO may do first drafts of any of these and have the PI correct them to bootstrap. May also include ticket links for pending or known connectivity issues. Many projects will have a full tree of wiki pages here.
Related Projects
Includes non-GENI projects.