Version 4 (modified by Tom Lehman, 11 years ago) (diff)


GENI MAX Stitching Project Status Report - Post GEC15

I. Major accomplishments

A. Milestones status

MAXREGIONAL: S4.c: Demonstration at GEC15
Work with Internet2 and MAX to deploy a stitching prototype ION/DYNES AM and a stitching prototype MAX AM that provides appropriate functions for an end-to-end stitching demo between MAX and CRON. (CRON AM is covered under CRON SOW.) Assumptions: This deployment will be of ION/DYNES AM based on MAX AM.

In this demonstration we showed multi-aggregate stitching between the MAX, ION, CRON, LONI, and ProtoGENI Aggregates. Use of the MAX Aggregate Manager (AM) which is compatible with the GENIv3 RSpec formats was demonstrated. Instances of the MAX AM were utilized to cover ION and LONI networks. This functionality was described in the context of the larger multi-aggregate stitching architecture vision consisting of a GENI Topology Service, Computation Service, GENI AM APIv3, and multi-aggregate slice instantiation workflows.

More detailed descriptions of this demonstration, including example RSpecs and demo scripts are located here:

We are now working with Internet2 to have the ION GENI AM capability formally deployed and managed by the Internet2 NOC on a trial basis.

This milestone is complete.

MAXREGIONAL: S4.d: MAX is an operational GENI aggregate
(GEC15) (10/25/12)

  • Implement the GENI AM API v3
  • Provide resources to experimenter credentials signed by one of the GENI slice authorities
  • Agree to the GENI Aggregate Providers Agreement
  • Updated description of the MAX aggregate on the GENI wiki including a description of resources available to experimenters.

The MAX AM has been upgraded to be compatible with GENI AM APIv3. The MAX GENI AM is also been federated with ProtoGENI and PlanetLab. Experimenters are able to utilize credentials and slices from those aggregates to instantiate experiments. Prototype ION and LONI AMs (based on the MAX AM) have also been deployed for experimental use.

We have some remaining items on this milestone. This includes updating the MAX Aggregate Information on the GENI Wiki, and returning the GENI Aggregate Providers Agreement. This milestone is partially complete pending completion of these items.

B. Deliverables made

During this reporting period we completed the following deliverables:

GEC14 Stitching Demonstration

  • ====> Publications ====> GEC15

or direct

MAX Aggregate Manager support for GENI v3 RSpecs:

MAX Aggregate Manager federated with ProtoGENI and PlanetLab and available for use via user and slice credentials from these aggregates.

II Description of work performed during last quarter

A. Activities and findings

Based on the work we have completed with our prototype deployments of ION and LONI GENI Aggregate Managers, we believe we are ready for a more production level deployment. We have started working with Internet2 NOC to deploy an instance of a GENI AM that they will maintain and support on a trial basis.

We have a well defined stitching architecture which consists of the following components:

  1. Stitching Extensions for RSpec Schemas
  2. Stitching WorkFlow Function (basic and w/negotiation)
  3. GENI AM API Extensions for Stitching
  4. Stitching Topology Service
  5. Stitching Computation Service

Based on already completed design, implementation, testing, and demonstrations, the indications are that we will be able to implement a GENI multi-aggregate stitching capability which will satisfy the needs of the initial GENI Rack deployments as well as other sites which will have GENI Aggregate Managers. Now that the GENI AM API v3 has been finalized, we will need to update the current design for item ii (stitching w/ negotiation). These updates are primarily message type and format in nature, and do not change the planned architecture or design.

This initial capability set will likely be based on items i and iii (with basic stitching workflow). This capability will allow GENI experimenters to utilize the initially deployed infrastructure to instantiate slices which span multiple aggregates. Parallel to this initial stitching deployment, work will continue on items ii (stitching w/negotiation), and iv-v to prepare for larger scale deployments.

B. Project participants

Tom Lehman (MAX)
Xi Yang (MAX)

C. Publications (individual and organizational)

No formal publications were funded by this projects during this time period.

D. Outreach activities

The current focus of our outreach activities is thru our collaborations with other Aggregates such as CRON, ProtoGENI, ExoGENI, and GENI Rack deployment sites. We also plan to encourage more outreach to potential experimenters at University of Maryland and other universities in the MAX footprint.

We are participating in conversations with the NSF CC-NIE community to discuss GENI. We also have a NSF CC-NIE project at MAX and will be working on the integration of this with our GENI capabilities on UMD campus and MAX member institutions.

E. Collaborations

As part of the activities and milestones described here, we have had extensive collaborations with many in the GENI community. This includes CRON, ProtoGENI, ExoGENI, and GPO developers. A large focus of our milestones during this reporting period revolved around network stitching architecture, design, and software development. These activities required collaborations with other GENI aggregate manager developers.

F. Other Contributions