wiki:GENIStitch-GENI-Status-Report-GEC20

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

--

GENIStitch Project Status Report - Post GEC20

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

I. Major accomplishments

A. Milestones status

GENIStitch.S5.a: Develop high-level architecture for extending GENI stitching for a range of connection/transport types and L2 broadcast domains. Pursue a detailed architecture/design for specific cases of pure OpenFlow and GRE-tunneled connections. Present enhanced stitching architecture and design at GEC19. Deliver draft architecture and design document to the GENI Project Manager one week prior to GEC19.

Status:
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:

  • wiki.maxgigapop.net/twiki/bin/view/GENI/Milestone-genistitch-s5b

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

  • wiki.maxgigapop.net/twiki/pub/GENI/Milestone-genistitch-s5b/geni-stitch-enhancements-architecture-v4.pdf

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

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.

MAXREGIONAL.S5.b Update the MAX Aggregate Manager to keep up to date with latest GENI AM APIs in use by other GENI Aggregates and GENI Experimenter tools.

Status: We have upgraded a development instance of the MAX Aggregate Manager software to support the version of PlanetLab SFA (v3.x.x) software that includes GENI AM APIv3. This required an upgrade of the base Fedora OS, and required some adaptations of the MAX Aggregate Manager software as well. These changes do enable the MAX AM to support the GENI AM APIv3. However, the SFA AM APIv3 is not backward compatible with the GENI AM APIv2 version. As a result we will likely need to run two instances of the GENI AM API during a transition period. This needs to be discussed further. In addition, we are also evaluating the possibility of switching to be FOAM based as opposed to SFA.

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.

Status: We have started working on the revised architecture and design document for GENI stitching to include multi-aggregate, multi-point, multi-path stitching capabilities. Much of this will likely be based on the actual capability set available in AL2S to begin with, since that is the initial real infrastructure where we will be able to utilize these features.

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:

II Description of work performed during last quarter

A. Activities and findings

Based conversations at GEC19 and after, we will likely focus our initial advanced/enhanced stitching activities on features sets we can expect to utilized on Internet2 AL2S. This will include multi-point in the context of the AL2S multipoint capability set. The unique features of the AL2S Multipoint is that it is as follows:

  • VLAN based
  • VLAN Firewall control for per slice isolation
  • MAC flooding
  • Generally not provisioned in full connected multi-point graph topologies

We are planning to discuss further with Internet2 and see if there is a way to modify the MAC flooding behavior to better control bandwidth utilization for slices with high bandwidth requirements.

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.