Version 6 (modified by, 10 years ago) (diff)


GENIStitch Project Status Report - Post GEC20

Project Status Report
Project 1948 (GENIStitch)
Post GEC 20 (June 21-24, 2014) Report

I. Major accomplishments

A. Milestones status

GENIStitch.S5.b: GENIStitch.S5b: Extend RSpec Enhancements and SCS to support the extended stitching capabilities. Demonstrate multi-aggregate, multi-point, multi-path stitching capabilities at GEC20. Deliver revised architecture and design document to the GENI Project Manager one week prior to GEC20.


We have updated the architecture and design document for GENI stitching to reflect the comments and inputs from the previous version. A summary of the comments and interest areas that we noted from the email reviews of the previous version of this document are as follows:

  • A priority for the next couple of GECs is to make stitching more reliable and feature rich
  • Evaluate further the concepts for GENI Stitching Exchange Points and the Stitching as a Service
  • Help push stitching support for AL2S AM
  • Help push support and implementation for VLAN negotiation
  • Define and implement features to make SCS more automated/monitored.

We have updated the GENI Multi-Technology and Multi-Point Layer-2 Stitching Architecture and Design document to reflect these comments and also included some other updates.

We have generated the following document:

  • GENI Multi-Technology and Multi-Point Layer-2 Stitching Architecture and Design, version 4

It is available on the MAX GENI Wiki at this location:


===> GENI Enhanced Stitching Architecture and Design or direct via:

This document provides a vision for how GENI Stitching can be enhanced and covers the topics as noted below. Based on comments to the previous version of this document, as noted above, and discussions at GEC20, we are planning to focus on the more practical and immediate needs for SCS and stitching. A summary of these immediate focus areas is provided in a new section “Stitching and SCS Near Term Focus Areas”. This new section is the only change to this document as compared to the previous version.

This document provide a vision for how GENI Stitching can be enhanced and covers the following topics:

  • Multi-Technology Multi-Layer Stitching
    • Stitching with Layer-3 and Layer-2 Tunnels
    • VXLAN and NVGRE Stitching
    • OpenFlow Stitching
    • Support for Arbitrary Layers
  • Multi-Point Layer-2 Stitching
    • Model and RSpec Schema
    • MP-L2 Stitching Functions
  • General Stitching Requests and SCS Extension
    • Advanced Stitching Architecture Considerations
    • GENI Stitching Exchange Points
  • Stitching and SCS Near Term Focus Areas

We were not able to demonstrate multi-point stitched topologies at GEC20. However, we hope to be able to do so across AL2S by GEC21. This will depend on Internet2 for implementation and testing support.

We continued working with Internet2 on their implementation of AL2S based stitching. This included defining the proper formats for AL2S Advertisement and Request Rspec, and describing how they should be constructed and processed. Internet2 AL2S stitching was working in a prototype fashion for GEC20. This included the ability to stitch between two sites directly connected to AL2S as well as for a path where one site is connected to Internet2 ION. One issue noted that will require further fixes by Internet2 is addition of an ability to process more then one stitched path per Request RSpec

B. Deliverables made

During this reporting period we completed the following deliverables:

Generated a draft architecture and design document for extending GENI stitching capabilities:

or direct via:

  • Participated in GEC20 Demonstration with iMinds and ProtoGENI to show international stitching between iMinds in Belgium, Internet2 ION, and other aggregates connected to ION. This included a deployment of a dedicated SCS instance by the iMinds team.

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 since GEC19 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 that contains a single stitching path. We will continue to work with Internet2 to support multiple stitching paths per slice, and testing for basic stitching operations.

We have also 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 are also planning to evaluate further how Stitching on AL2S and native OpenFlow operations (via FlowVisor Firewall) should interact. This will require additional discussions with GPO and Internet2.

GENI Stitching capabilities across Internet2 AL2S moved much closer to being an operational service as of this GEC. The Internet2 FOAM/OESS GENI AM implementation appears to be largely complete and working for the basis point-to-point stitching case. There is some work to do to fix a few bugs and go thru the peering configurations carefully to be sure that interconnects between AL2S, GENI Site, and ION are configured properly and with sufficient VLAN resources.

We have also been working with iMinds in Belgium on international stitching testing. The iMinds group has deployed their own instance of Stitching Computation Service (SCS) and has successfully tested stitching with an aggregate path that included Belgium, Internet2 ION, and several GENI Aggregates connected to Internet2 ION.

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