wiki:MAXREGIONAL-GENI-Final-Status-Report

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

--

GENI MAXREGIONAL Project Status Report - Post GEC21

MAX REGIONAL
Project Status Report
Project 1860 (MAXREGIONAL)
Final Status Report
Contract End Date: February 15, 2015

I. Major accomplishments

This project no cost extension phase was from October 1, 2014 thru February 15, 2015. The no cost extension milestones status is provided below. The milestone status from the previous budget period for this project is also provided below.

A. Milestones status

No Cost Extension Activities: During this No Cost Extension (NCE) period, the activities will focus on the update and maintenance of the MAX and ION Aggregate Manager software. This will include incorporating needed changes related to the GENI Aggregate Manager APIs and SFA software releases and bug fixes. These activities are continuations of a task defined from the previous budget period of this project. The MAX and Internet2 ION network run separate instances of the MAX Aggregate Manager software. The activities during this period will also include coordination and testing associated with deploying upgraded Aggregate Manager software on the ION network.

Status:
During this time period we worked with the Internet2 NOC and the GPO to update the ION Aggregate Manager with the latest software to support the GENI monitoring service. This included generation of multiple patches for the ION AM software, and working with the Internet2 NOC and GPO on deployment and testing. During this time period we also worked with Internet2 and the GPO to move GENI users off of ION and onto AL2S. This work was in preparation for the Internet2’s decommission of the ION service.

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 updating and testing the GPO monitoring infrastructure. This included working with the GPO to define the proper representations for inter-aggregate links in the monitoring local database. This work also included updates to the MAX Aggregate Manager to support the latest monitoring schemas. This work was completed and the most recent GPO monitoring software is currently deployed on the MAX aggregate. During this time period we also worked with the Internet2 NOC to update the ION Aggregate Manager with the latest updates to support the GENI monitoring service.

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: During this time period we have worked with GPO and Internet2 to support several upgrades to the ION Aggregate Manager. Most of these upgrades were to support the monitoring system. There were also upgrades to fix bugs, updated SFA, and to add support for SFA speaks-for.

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. This configuration was also deployed on the ION AM during this reporting period.

The ION AM software version and upgrade procedures are documented here:

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

II Description of work performed during last quarter

A. Activities and findings

A GENI Aggregate Manager covering the Internet2 ION Service was deployed from July 2011 thru the ION decommission in April 2015. The ION AM was initially run by MAX, and then transitioned to the Internet2 NOC. The GENI AM deployment for ION proved to be a very useful step which helped the GENI community start using wide area network stitching features. In addition, it also provided a use case and a reference point for Internet2 to develop a GENI AM to cover the AL2S network.

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

Outreach activities were thru 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.