wiki:GENIStitch-GENI-Status-Report-GEC22

Version 3 (modified by tlehman@maxgigapop.net, 5 years ago) (diff)

--

GENIStitch Project Status Report - Post GEC22

GENIStitch
Project Status Report
Project 1948 (GENIStitch)
Post GEC 22 (March 23-26, 2015) Report

I. Major accomplishments

A. Milestones status

For GEC22 (March 2015)

  • Extend SCS to support the multi-point and the additional stitching technologies as defined in the updated stitching architecture document. Demonstrate multi-point stitching capabilities across AL2S or other infrastructures at GEC22. Demonstrate stitching based on VTS or GRE technologies at GEC22.
  • Develop designs for SCS to enable user and user tools (OMNI, JACKS, Portal) to determine what options are available for inter-aggregate connections. This should include options based on GRE, VLAN based Stitching (point-to-point and multipoint), and the Virtual Topology Service (VTS). Provide an updated stitching architecture and design document that describes these feature set and designs one week before GEC22.
  • 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.

Status:

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.

During this reporting period, we worked with the GPO and Internet2 to transition the Production SCS to the GRNOC. We have developed an SCS Software Release and Upgrade Plan that is available here:

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

The Internet2 NOC has now deployed and is running the production SCS. We continue to work with them to provide patches and testing support as needed.

During this reporting period we worked with working with the GPO and others to development of a vision document for a GENI powered Software Defined Exchange (SDX). This document is available here:

We also deployed a prototype GENI powered SDX on the Washington International Exchange (WIX). We created a direct connection between WIX SDX and the iMINDS SDX in Belgium. This infrastructure was used as part of Demonstrations at GEC22. The Poster and slides from this demo are available here:

or direct via:

We also continued working with Internet2 and GPO on implementation and testing of AL2S based stitching. The AL2S stitching was utilized during GEC22 and seems to be working as expected.

We also generated an update to the GENI Stitching Architecture Document. This document includes long term options for future stitching feature sets as well as specific near term focus areas. Based on discussions with GPO and at GEC 22 Developer sessions, we have identified the following key areas for near term stitching feature focus and development:

  • AL2S Multipoint: Work with Internet to design, implement, and test multi-point stitching across AL2S using their Aggregate Manager (FOAM/OESS based).
  • SDX: Further refined the SDX concept and design. Study options and evaluate best approach to transition WIX prototype SDX to production status.
  • GENI AM for NSI networks: Study options and evaluate best approach have a GENI AM for networks which use the NSI API. Options for this include a) modify MAX AM to talk the NSI protocol, b) modify GPO OpenGENI/GRAM and add NSI support.
  • GENI AM APIv3: Review status of ProtoGENI support for VLAN negotiation via AM APIv3 and help with testing of that feature as it becomes available
  • Evaluate overall SCS and Stitching design and proposes features to increase level of monitoring, automation, and general ease of use and configuration.
  • User Tool/SCS Integration: Develop designs, and implementations where possible, to enable user and user tools to determine what options are available for inter-aggregate connections. This should include options based on GRE, eGRE, VLAN based Stitching, and the Virtual Topology Service (VTS). This will likely focus on possibility of Jacks server interacting with SCS.

This document is available here:

B. Deliverables made

During this reporting period we completed the following deliverables:

  • Presented a poster and demonstration at the GEC22 Demonstration Session on the topic of International Software Defined Exchange (SDX). This was in collaboration with GPO and iMinds.
  • Presented a demonstration GEC22 Plenary Session on the topic of International Software Defined Exchange (SDX). This was in collaboration with GPO and iMinds.
  • Supported Stitching demonstrations at GEC22, which included many demonstrations using AL2S stitching.
  • Completed transition of the Production SCS to Internet2 GRNOC.

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. ION has been decommissioned and AL2S is now the primary wide areas stitching infrastructure.

We are now increasing our focus on enabling multipoint stitching topologies. We have initial discussions regarding the options. We believe we have identified a path forward which leverages existing capabilities in AL2S that just need to be exposed via the GENI AM interface.

We made good progress on defining a vision and architecture for SDX, and how GENI software can be utilized to enable this functionality. Prototype SDXs have been deployed at WIX and iMinds. We are now evaluating options for adding policy features and determining the best approach to transition these prototype SDXs to production status.

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 this reporting period we began to evaluate what will be needed to support NSI networks within GENI. We plan to look into this in more detail during the next reporting period and identify implementation options which may include modifications to the MAX, GRAM, or AL2S AM software.

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

none.