create new tag
, view all tags
-- TomLehman - 31 Jul 2012

MAXREGIONAL: S4.b: Demonstration at GEC14

  • Demonstrate stitching between GENI resources at MAX and CRON using the prototype GENI stitching AMs for MAX, CRON and Internet2. Demonstrate GENI slices using stitched layer2 connections between MAX and CRON over Internet2. We anticipate that MAX will use the DYNES rack that should be installed in MAX before this demo, and that CRON will use traditional ION services provided by their LONI regional connection to Internet2, which will use appropriate services to interconnect them.

  • Evaluate modifications required to PerfSonar Topology Service to build a GENI Topology Service. Share design on GENI wiki and review at a GENI teleconference. Assumptions: This is design work; no implementation is expected. However design will be to the level of detail where implementation could begin.

Our GEC14 demonstration showed multi-aggregate stitching involving four aggregate managers: MAX, ION, LONI, and CRON. This included demonstration of the MAX (and ION, LONI) Aggregate Managers compatibility with the GENIv3 RSpec formats (MAX:S4.c).

This functionality was demonstrated in the context of the larger multi-aggregate stitching architecture and implementation work underway. The OMNI Client was used to submit requests to the four aggregates (CRON AM, LONI AM, ION AM, MAX AM). We demonstrated 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.

A GENI Rack at MAX was not available, so we utilized PlanetLab Resources at MAX for the host resources in that aggregate.

More detailed descriptions of this demonstration, including example RSpecs and demo scripts are located here:

Future work will include; i) enhancements to OMNI client to further automate the multi-aggregate stitching process, ii) updates to support latest RSpecs and stitching extensions, and iii) additional changes associated with other aggregates and GENI Racks.

The PerfSonar Topology Service has been evaluated in the context of modifying to create a GENI Topology Service. We believe that there is much we can leverage and learn from the PerfSonar system and we also see benefits in developing some degree of interoperation between GENI and PerfSonar systems. We also participated in network stitching focused discussions as part of the GENI Architecture group regular telecons. During these calls we discussed the overall GENI Stitching design which includes a GENI Topology Service and a GENI Computation Service.

We believe we have a good plan to create a GENI Topology Service. We are working the another GENI Project, GEMINI, to see if their UNIS system can be used as the foundation for a GENI Topology Service implementation. This will also us to build a bridge between the GENI and PerfSonar and Dynamic Circuit Service worlds.

Additional plans for GENI Topology Service design and implementation and drawing/slides from the GENI Architecture telecons are available here:

Future work for the GENI Topology Service includes: i) working with GEMINI project to see if implementation activities can leverage their work, ii) develop a GENI Topology Service API for GENI clients and computation service use.

Topic revision: r3 - 2012-12-09 - TomLehman
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback