Version 12 (modified by Tom Lehman, 6 years ago) (diff)


GENI MAX Stitching Project Status Report - Post GEC16

I. Major accomplishments

A. Milestones status

MAX: S4.d: Continue to federate the MAX Network with GENI and make it available to GENI experimenters, as well as for testing and demonstrations of network stitching in GENI

  • Implement the GENI RSpec v3
  • Provide resources to experimenter credentials signed by one of the GENI slice authorities

The MAX AM has been upgraded to be compatible with GENI RSpec v3. 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. We still need to update the MAX information on the Aggregate Information page on the GENI Wiki.

MAX: S4.e: Prototype GENI Topology and Path Computation Services

  • Initial Prototype: January 2013
  • Production Ready Service: May 1, 2013
  • Prototype GENI Topology and Path Computation Services (previous SOW is just for a design)

We have completed an initial version of the Stitching Computation Service (SCS). This has been utilized for development of the workflow service (which is the next milestone). A description of the SCS is available here:

The SCS software is available here:

We consider this software to be beyond prototype, but not yet transitioned to operational use. This transition will happen as part of the conduct of the Stitching Testing defined here:

The stitching topology service prototype implementation is still underway. We currently have a very basic topology service prototype implemented as part of the computation service. This provides the topology information that the SCS needs, but does not currently provide a generally available query mechanism or an automated update function via GENI AM API calls.

We have also been working with the GEMINI project to utilize their topology services for stitching services. They have implemented the ability to dynamically and automatically obtain topology information from the GENI AM API as well as the existing PerfSonar Topology Service. We have not implemented a mechanism to pull the information from the GEMINI Topology service. The topology service final design will likely be either based on extending what we currently have embedded in the SCS or via utilizing the GEMINI Topology Service. During the next reporting period we will finalize the plan for the GENI Topology Service and continue with implementation.

MAX: S4.f: Prototype shared GENI Stitching Workflow Service, based on Omni libstitch library, and use it from Omni, and make it available to Flack

  • Initial Prototype: February 2013
  • Production Ready Service: May 1, 2013

The Stitching Computation Service (SCS) includes functionality to generate workflow data as part of experimenter RSpec computation requests. OMNI developers are utilizing this workflow data as input for stitching library which is implemented as part of the OMNI package. This is currently under test and will be utilized as part of the stitching testing mentioned above as part of milestone S4.e status.

We have also worked with the Flack developer to incorporate use of the SCS workflow rules in to Flack provisioning. This work is still in progress.

MAX: S4.g: Update MAX/ION AMs to AM API v3 and to work with above services

  • Initial Prototype: March 2013
  • Production Ready Version: May 30, 2013

The MAX AM update for AM API v3 is now scheduled to occur after GEC 17. The current focus is on enhancing existing stitching functionality before GEC 17. In addition, the other GENI Aggregates (ProtoGENI and ExoGENI) are not expected to have GENI AM APIv3 support until after GEC17. As a result, the current plan is to focus on current stitching features before GEC17, and then add support for GENI AM APIv3 afterwards.

MAX: S4.h: Demo an InstaGENI and an ExoGENI rack stitched dynamically together using above services across a backbone at GEC16

  • Initial InstaGENI and ExoGENI stitching demonstration: March 2013 (GEC 16)
  • Experimenter ready InstaGENI and ExoGENI stitching capability: May 30, 2013

We demonstrated stitching between InstaGENI Racks at BBN and ProtoGENI main resources connected across ION during GEC16. This included a slice topology with three GENI AMs. The details for this demonstration are available here:

ExoGENI racks which supported stitching were not available before GEC 16. We hope to be able to demonstrate stitching with ExoGENI racks as part of GEC 17 demonstrations.

MAX: S4.i: Prototype DYNES/ION proxy AMs (extension of existing prototype ION AM, and includes the features from item iii above)

  • Initial Prototype: March 2013
  • Production Ready Version: May 30, 2013

An instance of the MAX Aggregate Manager has been deployed as the ION Aggregate Manager. The Internet2 NOC has deployed this and is running as an operational service. We will continue to work with the I2 NOC to upgrade their GENI AM as we add new features to the MAX Aggregate Manager software. This same software can also be used to cover any DYNES deployment.

B. Deliverables made

During this reporting period we completed the following deliverables:

GEC16 Stitching Demonstration

  • ====> Publications ====> GEC16

or direct

MAX Aggregate Manager support for GENI v3 RSpecs:

Stitching Computation Service (SCS) Design

The SCS software:

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, we are now working to complete the implementation and testing of the GENI multi-aggregate stitching capability. 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.

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 have made arrangements to receive an InstaGENI rack, which is expected to arrive prior to GEC17. We will place this on the UMD Campus and also make it available to other MAX participants.

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