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


GENI MAX Project Status Report

Post GEC 13 (March 13-15, 2012) Report
Period: Jan 26 - GEC13

I. Major accomplishments

A. Milestones achieved

MAX: S4.a: Incorporation of Stitching Extension into OpenFlow AMs

Work with FOAM developer so that OpenFlow AM or other AMs that include !Openflow switches support basic stitching through OpenFlow switches in the GENI mesoscale network. This will include support for current stitching schema in advertisements RSpec, request RSpecs, and manifest RSpecs. Support for the AM API negotiation extensions and Tree mode workflow will also be included. Stitching technology for this task will focus on VLANs with objective to make the OpenFlow AM interoperate with other AMs for GENI stitching. Share design on GENI wiki and in GENI mailing lists, and present at GEC13.


We have completed a design for how OpenFlow AMs can include the GENI Stitching Extension as part of their Advertisement, Request, and Manifest RSpecs. This is presented here:

OpenFlow Aggregate included in Stitching Workflow:

Here is a direct link to an example OpenFlow Advertisement RSpec with Stitching:

This information is also linked from the GENI Wiki on the MAX project pages.

The RSpec Stitching Schema Extension can be used for GENI Stitching workflows with or without negotiation. We developed this design in the context of a multi-aggregate stitching operation which included a set of GENI AM API extensions to support stitching with negotiation. See MAX:S4.b for an extended discussion on GENI Stitching workflows options, implementation, and deployment plans.

We still need to coordinate with the FOAM developer on the incorporation of these Stitching Extensions into the OpenFlow AM. We will do this prior to GEC14.

MAX: S4.b: Help Define GENI AM API Extensions to support Stitching w/negotiation

Help define GENI AM API extensions for negotiation, focusing on tree mode stitching. Work with Internet2 to design and document a prototype ION/DYNES/Oscars GENI AM (semantics, data fields, and usage policies) using these extensions. Document workflows for example stitching negotiations in the GENI mesoscale (e.g. CRON and MAX resources connected over Internet2 or NLR). Share design on GENI wiki and in GENI mailing lists, and present at GEC13.

We have completed a design for how multi-aggregate stitching can be accomplished which includes negotiation. This design is presented here:

Network Stitching with GENI API and RSPEC:

We developed this design in the context of using "tickets" as the basis for AM resource negotiation. The use of tickets in the GENI API is broader then just the stitching use case we present in our designs. However, the introduction of tickets into the GENI AM API, is still under discussion by the GENI development community. For this reason, we expect that we will have to modify some aspects of the above design. We are planning next to discuss these concepts with the AM developers from ProtoGENI, ORCA, and OpenFlow. We will also seek broader community inputs once there is a loose consensus on the basic mechanism in the GENI AM API for a "ticket" mechanism or something similar as currently being discussed. We believe that the general stitching/w negotiation design we have defined can be easily adapted to any of the specifics that the GENI AM development community is now discussing in this area.

In addition to work to finalize the Stitching w/negotiation design, we will also continue toward the implementation and deployment of the Stitching Extension schemas and the basic workflow stitching (i.e., no negotiation required) across from ProtoGENI, ORCA, MAX, ION, and OpenFlow Aggregates.

We demonstrated multi-aggregate stitching across the MAX and CRON Aggregates at GEC13. This included the provision of resources across the MAX Aggregate, CRON Aggregate, Internet2 ION, and LONI Regional network. This demonstration contains many of the elements needed for the basic stitching workflow. However, there is more implementation and workflow design to be completed before we have an experimenter ready multi-aggregate stitching capability. These remaining tasks are described below.

ProtoGENI AM has implemented Stitching Extensions into RSpecs (Advertisement, Request, Manifest). ORCA AM has implemented an initial version of the Advertisement RSpec with a Stitching. Moving forward we have the following items to complete on this milestone:

Work with ProtoGENI AM developers:

  • verify proper use of Stitching Extension with basic stitching workflow
  • review stitching workflow with negotiation design
  • review stitching workflow steps for both basic ProtoGENI aggregate and the "HP" GeniRack.

Work with ORCA AM developers:

  • assist them with finalization of Stitching Extension implementation
  • verify proper use of Stitching Extension with basic stitching workflow
  • review stitching workflow with negotiation design
  • review stitching workflow steps for both basic ORCA aggregate and the "ORCA" GeniRack.

Work with OpenFlow AM developers:

  • assist them with initial implementation of Stitching Extension
  • verify proper use of Stitching Extension with basic stitching workflow
  • review stitching workflow with negotiation design

Work with Internet2 to develop a plan to support GENI Stitching Operations:

  • design stitching workflow plans for use of ION and NDDI
  • Work with NLR to develop a plan to support GENI Stitching Operations :
  • design stitching workflow plans for use of NLR

The items are scheduled be completed by GEC14.

B. Deliverables made

During this reporting period we completed the following deliverables:

Network Stitching Design with Ticket Based Negotiation:

Initial Design for OpenFlow use of Stitching Extension:

GEC13 Stitching Presentation:

GEC13 Stitching Demonstration

II Description of work performed during last quarter

A. Activities and findings

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. This initial capability set will likely be based on items i and ii (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 should continue on items ii (stitching w/negotiation), and iii-iv to prepare for larger scale deployments and more vigorous use by experimenters.

B. Project participants

Tom Lehman (USC/ISI)
Xi Yang (USC/ISI)
Abdella Battou (MAX)
Balasubramania Pillai (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. We also plan to encourage MAX users who are currently using dynamic layer2 services to utilize GENI.

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, PlanetLab, 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