wiki:MAXREGIONAL-GENI-Status-Report-GEC20

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

--

GENI MAXREGIONAL Project Status Report - Post GEC20

MAX REGIONAL
Project Status Report
Project 1860 (MAXREGIONAL)
Post GEC 20 (June 21-24, 2014) Report

I. Major accomplishments

A. Milestones status

MAXREGIONAL.S5.a Continue to support the stitching interoperation and testing between GENI Racks/Aggregates, and across network infrastructures such as Internet2 ION, AL2S, regional networks, and other networks that may be available for GENI stitching use.

Status:
During this period the stitching support activities included deploying and testing the GPO monitoring infrastructure. This included deploying the GPO provided software on the MAX Aggregate and assistance for Internet2 deployment on the Internet2 ION Aggregate. We also supported general stitching troubleshooting and testing activities.

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: As part of SFA bug fixes and upgrades we have develop an MAX AM configuration which no longer requires MyPLC and the associated Postgres database. The result is the MAX AM software now only relies on the SFA component from the PlanetLab software base. We have deployed this system on the MAX Infrastructure. A similar configuration will be deployed on the ION AM before the next GEC.

The upgrade of the MAX Aggregate Manager software to support the version of PlanetLab SFA (v3.x) software that includes GENI AM APIv3 remains unchanged during this reporting period. 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. We do not think SFA GENI AM APIv3 version provides backward compatibility with GENI AM APIv2. However, we are not clear if this will be added in a future revision. We will check with PlanetLab team regarding this before the next GEC. If there is no backward compatibility, we will likely need to run two instances of the GENI AM API during a transition period.

We have evaluated the possibility of switching the MAX AM to be a FOAM or GRAM based as opposed to SFA. However, with the recent removal of MyPLC requirement, we do not feel this is an urgent need at this time. We are planning to further evaluate this during the next reporting period.

MAXREGIONAL.S5.c Develop designs and prototype systems for facilitating and managing VLAN delegation by statically provisioned network regions. Work GPO and network providers to test and refine designs.

Status: We have not made changes to this static VLAN description system during this reporting period. We currently are running and maintaining a script that automatically pulls Advertisement RSpecs from GENI Aggregates and generates a wiki page. This wiki page provides information regarding networks where statically provisioned VLANs are utilized to connect two GENI Aggregates. Information formatted in accordance with a configuration file schema indicates which GENI Aggregates should be included in this process. This wiki page is located here:

B. Deliverables made

During this reporting period we completed the following deliverables:

  • Upgrades of the deployed GPO monitoring software infrastructure on MAX Aggregate.
  • Provided support for Internet ION AM upgrade of the GPO monitoring software infrastructure
  • Provided support for general stitching testing

II Description of work performed during last quarter

A. Activities and findings

GENI stitching across Internet2 ION saw significant utilization by some of the GENI experimenters during this reporting period. We received some positive feedback regarding their ability to build topologies that included multiple stitched links.

MAX is also planning to deploy an instance of the Inernet2 Software suite (FOAM/OESS/FlowSpace Firewall) on parts of the MAX Infrastructure for help with future testing and evaluation across 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.

We have received and installed the MAX InstaGENI rack. This has been connected to the MAX Aggregate which enables stitching thru Internet2 ION and AL2S. The MAX InstaGENI rack is also connected thru Internet2 AL2S to the GENI Mesoscale infrastructure. This rack has completed acceptance testing and is now available for GENI community use. We plan to conduct outreach to potential experimenters at University of Maryland and other universities in the MAX footprint.

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.