Version 2 (modified by, 4 years ago) (diff)


GENIStitch Project Status Report - Post GEC21

Project Status Report
Project 1948 (GENIStitch)
Post GEC 21 (October 20-23, 2014) Report

I. Major accomplishments

A. Milestones status

For GEC21 (October 2014) and through December 2014

  • Continue work on the GENI stitching architecture to extending GENI stitching for a range of connection/transport types and L2 broadcast domains. Based on work from Year 1 of this project, the stitching enhancements focus areas are expected to be Virtual Topology Service (VTS), GRE, and multipoint. An update to the stitching architecture document that defines the stitching architecture and implementation plan in the context of these focus areas will be generated. Deliver an updated stitching architecture document update to the GENI Program Manger by the end CY 2014.
  • Continue work on defining architecture for Software Defined Network Exchange (SDX) and Software Defined Infrastructure Exchange (SDIx) in the context GENI infrastructures. Work with the GPO and others to define these design concepts, architectures, and support demonstrations.


We have continued to support and update the Stitching Computation Service (SCS). This includes the running three instances of the SCS: Production SCS, Test SCS, and Development SCS. The Development and Test SCS allows us to stage and test various combinations of software and Advertisement RSpec combinations.

We have begun discussions with GPO and Internet2 about transitioning the Production SCS to the GRNOC. We have developed a draft SCS Software Release and Upgrade Plan which is available here:

This plan is very similar to the ION AM Software Release and Upgrade Plan which is already utilized for coordinating ION AM upgrades with the GRNOC.

We have also continued working with Internet2 and GPO on implementation and testing of AL2S based stitching.

We are currently working on an update to the GENI Stitching Architecture Document. This will address the latest plans for stitching based on Virtual Topology Service (VTS), GRE, and multipoint technologies. The multipoint design is based on the capability set that is available on Internet2 AL2S. We expect to have this updated document available per the above schedule in December 2014.

During this reporting period we have also been working with the GPO and others to develop a document defining a vision for Software Defined Exchange (SDX) and Software Defined Infrastructure Exchange (SDIX) architectures. This document is expected to be distributed soon. We presented a poster on this subject at the GEC21 that is available here:

or direct via:

B. Deliverables made

During this reporting period we completed the following deliverable:

  • Presented a poster at GEC21 Demonstration Session on the topic of Software Defined Exchange (SDX) and Software Defined Infrastructure Exchange (SDIX). This was a collaboration with GPO and iMinds.
  • Supported Stitching demonstrations at GEC21, which included a plenary demo showing stitching between InstaGENI and ExoGENI resources.
  • Completed several updates of the MAX AM, ION AM, and the Production SCS.

II Description of work performed during last quarter

A. Activities and findings

Our focus continues to be on enhancing the robustness and features for stitching and the Stitching Computation Service (SCS). This includes working with Internet2 to get full stitching support on AL2S. There has been good progress in this area. The AL2S AM is able to support basic stitching. This includes production of an Advertisement Rspec, and processing a basic Request RSpec. We will continue to work with Internet2 to support and test AL2S stitching.

Our key focus will be in testing and enhancing the robustness of basic point-to-point stitching operations. A secondary focus will be on enabling multipoint stitching topologies. Toward this goal, we have begun evaluation and discussions for supporting multipoint stitching across AL2S. The some unique features regarding how AL2S provisions Multipoint topologies across its OpenFlow infrastructure that we need to consider.

We have also evaluating how GENI technologies can be utilized as the basis for Software Defined Exchange (SDX) and Software Defined Infrastructure Exchange (SDIX). This is collaboration with GPO and iMinds. We are working on architecture documents in this area, and we expect to work toward some demonstrations for GEC22. It appears that the GENI infrastructure provides many of the features sets needed for an SDIX.

As part of our work with iMinds on SDX/SDIX architectures, we have identified GENI AM integration with NSI infrastructures as a capability that may be needed. This is based on the expectation that GEANT and some exchange points may have NSI APIs in the near future. During the next reporting period we are planning to evaluate what would be needed to adapt the current MAX/ION AM to also support a network which has an NSI Interface. We will also evaluate if GRAM may be another alternative for NSI based networks.

We have a couple of tickets open relating to ION provisioning. These revolve around large stitched topologies, and some issues with ION circuits not getting deleted properly when a slice is deleted. We will investigate the issues here and see if any fixes are required. We will also evaluate if this is something that is unique to ION, or something that we may expect to also see on AL2S.

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 ProtoGENI, ExoGENI, and GENI Rack deployment sites.

E. Collaborations

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

F. Other Contributions