Publications
GENI Engineering Conference #3 - Oct 2008
October 28-30, 2008
HP Labs
Palo Alto, California
GEC3 presentation archives
Mid-Atlantic Crossroads Update
-
Full text: pdf
-
Keynote source: zip
DRAGON API Slides
-
Powerpoint: ppt — animation included
Demonstration Movie
-
Quicktime Movie: mov — refer to slides 19-21 of pdf for explanation
Poster
Cluster B Integration Meeting - Feb 2009
Feburary 13, 2009
Denver Airport Marriott at Gateway Park
Denver, Colorado
Cluster B integration wiki page
MANFRED Update and Current Issues
-
Full text: pdf
-
Keynote source: zip
Meeting Minutes
GENI Engineering Conference #4 - Mar/Apr, 2009
March 31 - April 2, 2009
Hilton Miami Downtown
Miami, Florida
GEC4 presentation archives
Recent Activities and Demonstration Details
-
Full text: pdf
-
Keynote source: zip
Substrate-WG - Generalized Interfaces for GENI: Integrating Dynamic Circuits
-
Full text: pdf
-
Keynote source: zip
Demo
- Description: GENI Ticket #59
-
Quicktime Movie: mov? — refer to slides 7-12 of pdf for explanation
- Additional Slides: "Aggregates' Integration: using aggregate managers to create complex systems for experimentation"
Poster
Network RSpec Mini-workshop - Jun 2009
June 25, 2009
Chicago O'Hare Hilton
Chicago, Illinois
Network RSpec Mini-workshop wiki page
SOAP-based GENI Aggregate Manager
End-to-End Slices Across Network Aggregates
-
Full text: pdf
-
Part 1 — Keynote source: unavailable
-
Part 2 — Powerpoint: ppt
Demo
-
Quicktime Movie: mov? — refer to slides 9-10 of pdf for explanation
GENI Engineering Conference #5 - Jul 2009
July 20-22, 2009
Sheraton Seattle Hotel
Seattle, Washington
GEC5 presentation archives
Cluster B Update: Recursive, Portable Aggregate Manager
Control Framework WG: Network Stitching
-
Full text: pdf
-
Keynote source: zip
Substrate-WG: Horizontal/Vertical Integration
-
Full text: pdf
-
Keynote source: zip
Poster
Spiral 1 Proposed Physical Intra/Inter-Cluster WAN Connectivity
GENI Engineering Conference #7- March 2010
March 16-18, 2010
Duke University
Durham, North Carolina
GEC7 presentation archives
GEC7 Demonstration Page
Cluster B Update: MAX MANFRED and Aggregate Manager Status and Update
-
PDF Version: pdf
-
Powerpoint Version: ppt
Demo
Poster
GENI Engineering Conference #8- July 2010
July 20-22, 2010
UCSD University
San Diego, California
GEC8 presentation archives
Cluster B Update Presentation
Demo at Cluster B Meeting
- Demonstration of using MAX Aggregate Manager to instantiate an triangle topology on MAX
GENI Engineering Conference #9- November 2010
November 2-4, 2010
Washington D.C.
GEC9 presentation archives
GEC9 Demonstration Page
Cluster B Update Presentation
Demonstration Session - Using SFI/SFA and MAX Aggregate Manager to instantiate GENI Slices
- Demonstration of using MAX Aggregate Manager to instantiate an triangle topology on MAX
- Demonstration of using MAX Aggregate Manager to instantiate an experiment topology which includes ProtoGENI resources
Poster
Control Framework - Network Stitching Presentation
GENI Engineering Conference #10- March 2011
March 15-17, 2011
San Juan
Puerto Rico
GEC10 presentation archives
GEC10 Demonstration Page
Demonstration Session - Using SFI/SFA and MAX Aggregate Manager to instantiate GENI Slices
- Stitching Between MAX and ProtoGENI:
- Stitching Between MAX and Internet2 ION:
- Stitching locally on a MAX triangle topology between PlanetLab Slices via Dynamic Network Provisioning:
Poster
-
MAX GENI GEC10 Poster PDF: pdf
GENI Engineering Conference #11 - July 2011
July 25-28, 2011
Denver
Colorado
GEC11 presentation archives
Poster Session - MAX Aggregate Manager, Federation and Stitching
The MAX project has constructed the "Mid-Atlantic Crossroads GENI (MAX GENI) Facility" which enables the MAX Regional Network resources to be made available for GENI experiments. This includes development of a MAX Aggregate Manager which integrates the dynamic provision of network and host based resources. The host based resources include PlanetLab node virtual slices. MAX Network Stitching capabilities allow the host resources to be stitched together with Ethernet VLANs. The MAX AM is also federated with PlanetLab Princeton and ProtoGENI. In addition, a separate instance of a MAX Aggregate Manager has been deployed to "cover" the Internet2 ION Network.
This combination of these capabilities now allows us to provide multi-aggregate sliver creation and stitching operations in response to Experimenters requests.
Poster
-
MAX GENI GEC11 Poster: pdf
Demonstration Overview
Stitching Session
GENI Engineering Conference #12 - November 2-4 2011
November 2-4, 2011
University of Missouri
Kansas City, MO
GEC12 presentation archives
ControlFramework Session - Stitching Session
GENI Engineering Conference #13 - March 2012
March 13-15, 2012
UCLA
Los Angeles, CA
GEC13 presentation archives
Poster Session - Multi-Aggregate Network Stitching
Demo participants:
Tom Lehman (USC/ISI)
Xi Yang (USC/ISI)
Abdella Battou (MAX)
Balu Pillai (MAX)
Seung-Jong Park (LSU)
Lin Xue (LSU)
In this demonstration we will show multi-aggregate stitching between the MAX and CRON Aggregates. This will include the provision of resources across the MAX Aggregate, CRON Aggregate, Internet2 ION, and LONI Regional network. In addition, we will describe this functionality in the context of the larger tree-mode multi-aggregate stitching architecture and implementation work underway. We will also show the incorporation of OpenFlow network regions into the overall stitching process.
Poster
Demonstration Overview
Stitching Session
GENI Engineering Conference #14 - July 2012
July 9-12, 2012
MIT
Boston, MA
GEC14 presentation archives
Multi-Aggregate Network Stitching Demonstration
Demo participants:
Tom Lehman (USC/ISI)
Xi Yang (MAX)
Abdella Battou (MAX)
Balu Pillai (MAX)
Seung-Jong Park (LSU)
Chui-Hui Chiu (LSU)
In this demonstration we will show multi-aggregate stitching between the MAX and CRON Aggregates. This will include the provision of resources across the MAX Aggregate, CRON Aggregate, Internet2 ION, and LONI Regional network. Use of the MAX and ION Aggregate Managers which are now compatible with the GENIv3 RSpec formats will be demonstrated. This functionality will be described in the context of the larger multi-aggregate stitching architecture and implementation work underway. The OMNI Client will be used to coordinate Sliver creation across multiple aggregates as part of multi-aggregate slice stitching. Demonstration will include the cases where the Dynamic Circuit Network (DCN) networks in between the GENI Aggregates all have a GENI Aggregate Manager "covering" them, and the case where some (or all) of the DCN networks do not have a GENI AM API.
- GEC 14 Demo Overview: (click or download image to see a larger version)
Below are the specific scenarios and RSpecs from this demo.
- Create a single slice with stitching path across four aggregates (AMs): MAX--ION--LONI--CRON. A stitched, dedicated P2P VLAN connects compute resources from MAX to CRON.
- GENI version 3 RSpec
- MAX, ION and LONI have the same RSpec that describes stitching resources in all the four aggregates This is to comply with the GENI Stitching Architecture design. CRON is controlled by an Emulab / ProtoGENI style AM, which does not support the "longer" version of RSpec yet. cron.rspec only contains resource description for its local aggregate.
- Alternatively we can perform this stitching by only using three AMs: MAX--ION--CRON, where the ION AM will create VLAN circuit across both ION and CRON by leveraging their inherent Dynamic Circuit Network (DCN) capability.
Stitching Demo Scripts
- The simple demo scripts use hard-coded workflow to determine sequence of operations. This will be replaced by OMNI stitching library (libstitch) and possibly a standalone Stitching Workflow Service.
- A script for four-AM stitching: demogec14.sh
- A script for three-AM stitching: demogec14-alt.sh
- Clean-up script: cleanup.sh
Poster
GENI WIKI Demonstration Overview
GENI Engineering Conference #15 - October 2012
October 23-25, 2012
University of Houston
Houston, TX
GEC15 presentation archives
Poster
-
MAX GENI GEC15 Poster: pdf
Multi-Aggregate Network Stitching Demonstration
We demonstrate four stitching scenarios.
- Scenario A A single VLAN stitching path across MAX, ION and ProtoGENI with compute hosts attached at both ends with VLAN interfaces.
- Scenario B The same stitching path as A but involving only two AMs. MAX AM will set up the MAX-ION as one DCN stitching segment.
- Scenario C Two VLAN parallel stitching paths in one RSpec, each being attached to hosts at both ends.
- Scenario D Two VLAN disjoint stitching paths in one RSpec, one path CRON--LONI--ION--MAX and the other PG--ION--MAX, both having hosts attached at both ends. ION AM will be responsible for setting up the ION--LONI DCN stitching segment.
Stitching Demo Scenario A
- A single RSpec for all three aggregates: gec15-demo.rspec
- ProtoGENI can only consume VLAN tags. A specific VLAN tag is pre-determinted in the RSpec for that aggregate.
- ProtoGENI code only takes kbps as default bandwidth unit. Bandwidth values in the above RSpec need to be converted to accommodate that.
- Script for setting up PG--ION--MAX stitching: demogec15.sh
- Script for cleaning up: cleanupgec15.sh
- Example manifests generated by stitching:
Stitching Demo Scenario B
- A single RSpec for both MAX and PG aggregates: gec15-demo2.rspec
- We can use one AM to setup a stitching segment spanning multiple aggregates only if all the involved aggregates are DCN capable.
- To represent this request in stitching extension RSpec, we use an implicit rule in stitching path definition: There should be one and only one hop in the initiating aggregate to indicate the source of the DCN segment and the next hop should be in a remote aggregate as the destination of the DCN segment.
- One catch is that the destination hop in remote aggregate can only be a network port/link, not a host interface. Otherwise, the AM at source cannot map the remote hop into a network port/link URN. Therefore RSpec in this scenario must have stitching path going from MAX-->PG direction because MAX AM sets up stitching segment starting from a host interface URN and spanning both MAX and ION.
- Script for setting up MAX--PG stitching: gec15-demo2.sh
- Example manifests generated by stitching:
Stitching Demo Scenario C
- A single RSpec for two parallel stitching paths: gec15-demo3.rspec
- Script for setting up two-path MAX-ION-PG stitching: gec15-demo3.sh
- This may take 10 minutes or more as it is time consuming to instantiate multiple DCN paths in ION and multiple bare mental nodes in PG.
- Example manifests generated by stitching:
Stitching Demo Scenario D
- A single RSpec for two disjoint stitching paths: gec15-demo4.rspec
- ION AM sets up DCN VLAN circuit across ION and LONI to stitch MAX and CRON
- ION AM also sets up DCN VLAN circuit across ION to stitch MAX and PG as a second path in the same slice
- Script for setting up CRON-LONI-ION-MAX stitching: gec15-demo4.sh
- Example manifests generated by stitching:
Package containing all scripts and RSpec templates:
gec15-demo.tar
GENI Engineering Conference #16 - March 2013
March 19-21, 2013
University of Utah
Salt Lake City, UT
GEC16 presentation archives
Poster
-
MAX GENI GEC16 Poster: pdf
Automated Network Stitching Across GENI Infrastructure Demonstration
For the first time we demonstrate fully automated GENI stitching across ProtoGENI networks, ION and InstaGENI racks. The new capabilities are highlighted below.
- Stitching Computation Service (SCS) a) collects topology advertisement from GENI aggregates, b) serves client stitching computation requests via SCS API, c) computes stitching paths and workflow dependencies, and d) returns service RSepc with expanded stitching path and stitching workflow data.
- Stitching Client API has been implemented by omni stitcher client code. The client supports sophisticated workflow logic by using SCS query, dependency tree iteration and crank back etc. functions.
- Stitching aware GENI AM at all the participating aggregates. GENI Stitching Architecture is now supported via GENI AM API 2.0 and Stitching Extension 1.0 by all the ProtoGENI, InstaGENI and DCN GENI aggregates.
- Client users can be stitching agnostic. No stitching extension is required in the original request RSpec. The stitcher client will consult SCS to add stitching extension when needed.
Advertisement RSepcs learned by SCS:
The following stitching paths are demonstrated.
- ProtoGENI_Utah --- I2_ION --- GPO_InstaGENI
- ProtoGENI_Utah --- I2_ION --- ProtoGENI_UKentucky
- ProtoGENI_UKentucky --- I2_ION --- GPO_InstaGENI