Changes between Initial Version and Version 1 of MAX-GENI-Final-Report

10/03/13 22:30:49 (9 years ago)



  • MAX-GENI-Final-Report

    v1 v1  
     1= GENI MAX  Stitching Project Status Report - Post GEC17 =
     2Project Status Report[[BR]]
     3Project 1658 (MAX)[[BR]]
     4Final Report [[BR]]
     5Period of performance[[BR]]
     6September 10, 2012 - August 31, 2013[[BR]]
     9==  I. Major accomplishments ==
     10=== A. Milestones status ===
     13__''MAX: S4.d: Continue to federate the MAX Network with GENI and make it available to GENI experimenters, as well as for testing and demonstrations of network stitching in GENI''__[[BR]]
     14  * Implement the GENI RSpec v3
     15  * Provide resources to experimenter credentials signed by one of the GENI slice authorities
     18The MAX AM has been upgraded to be compatible with GENI RSpec v3.  The MAX GENI AM is also been federated with ProtoGENI and PlanetLab.  Experimenters are able to utilize credentials and slices from those aggregates to instantiate experiments.
     21__''MAX: S4.e:  Prototype GENI Topology and Path Computation Services''__[[BR]]
     22  * Initial Prototype:  January 2013
     23  * Production Ready Service:  May 1, 2013
     24  * Prototype GENI Topology and Path Computation Services (previous SOW is just for a design)
     28We have completed a version of the Stitching Computation Service (SCS).   This has been utilized for development of the workflow service  and is available for general use.  A description of the SCS is available here:
     29   *
     31The SCS software is available here:
     32   *
     34The SCS service was tested as part of the GENI Network Stitching Plan as described here:
     35   *
     37The stitching topology service prototype implementation is implemented as part of the computation service.  This provides the topology information that the SCS needs, but does not currently provide a generally available query mechanism or an automated update function via GENI AM API calls.
     39We have also been working with the GEMINI project to utilize their topology services for stitching services.  They have implemented the ability to dynamically and automatically obtain topology information from the GENI AM API as well as the existing PerfSonar Topology Service.   Additional coordination with the GEMINI group is needed to determine if their topology service will be the basis for a more generally available service.  Future topology service functionality will likely be either based on extending what we currently have embedded in the SCS or via utilizing the GEMINI Topology Service.
     42__''MAX: S4.f:  Prototype shared GENI Stitching Workflow Service, based on Omni libstitch library, and use it from Omni, and make it available to Flack''__[[BR]]
     43   * Initial Prototype:  February 2013
     44   * Production Ready Service:  May 1, 2013
     47The Stitching Computation Service (SCS) includes functionality to generate workflow data as part of experimenter RSpec computation requests.  OMNI developers are utilizing this workflow data as input for stitching library which is implemented as part of the OMNI package.  This functionality was demonstrated as part of the GENI Network Stitching Test Plan activity noted above, and also demonstrated during GEC 17.  The SCS service is available to Flack.  We have worked with the Flack developer to get proper Flash security policies running on ION and MAX AM, and allow access to SCS by Flack.  There is expected to be continued work in this area to make this part of the standard Flack experience and also associated with the upgrade to Flack to be HTML5 based.
     51__''MAX: S4.g:  Update MAX/ION AMs to AM API v3 and to work with above services''__[[BR]]
     52   * Initial Prototype: March 2013
     53   * Production Ready Version:  May 30, 2013
     56We have completed initial design work for the update of the MAX AM API v3.  The support for GENI AM APIv3 by other GENI Aggregates (ProtoGENI and ExoGENI) was not available during this time period.  As a result we focused on additional stitching activities and are planning to complete the MAX AM APIv3 implementation and upgrade in December 2013.
     59__''MAX: S4.h:  Demo an InstaGENI and an ExoGENI rack stitched dynamically together using above services across a backbone at GEC16''__[[BR]]
     60   * Initial InstaGENI and ExoGENI stitching demonstration:  March 2013 (GEC 16)
     61   * Experimenter ready InstaGENI and ExoGENI stitching capability:  May 30, 2013
     64We demonstrated stitching between InstaGENI Racks at Utah, ProtoGENI main, and GPO ExoGENI Rack resources connected across ION during GEC17.  This included a slice topology with three GENI AMs.  The details for this demonstration are available here:
     66   *
     68__''MAX: S4.i: Prototype DYNES/ION proxy AMs (extension of existing prototype ION AM, and includes the features from item iii above)''__[[BR]]
     69Initial Prototype: March 2013
     70Production Ready Version:  May 30, 2013
     73An instance of the MAX Aggregate Manager has been deployed as the ION Aggregate Manager.   The Internet2 NOC has deployed this and is running as an operational service.  We will continue to work with the I2 NOC to upgrade their GENI AM as we add new features to the MAX Aggregate Manager software.  This same software can also be used to cover any DYNES deployment.
     76=== B. Deliverables made ===
     77During this reporting period we completed the following deliverables:
     79GEC17 Stitching Demonstration
     80   *  ====> Publications  ====> GEC17
     81or direct
     82   *
     83   *
     85MAX Aggregate Manager support for GENI v3 RSpecs:
     86   *
     88Stitching Computation Service (SCS) Design
     89   *
     91The SCS software:
     92   *
     94MAX Aggregate Manager federated with ProtoGENI and PlanetLab and available for use via user and slice credentials from these aggregates.
     96==  II Description of work performed during last quarter ==
     97=== A. Activities and findings ===
     99Based on the work we have completed with our prototype deployments of ION and LONI GENI Aggregate Managers, we believe we are ready for a more production level deployment.  We have started working with Internet2 NOC to deploy an instance of a GENI AM that they will maintain and support on a trial basis.
     101We have a well defined stitching architecture which consists of the following components:[[BR]]
     103i.      Stitching Extensions for RSpec Schemas[[BR]]
     104ii.     Stitching !WorkFlow Function (basic and w/negotiation)[[BR]]
     105iii.    GENI AM API Extensions for Stitching[[BR]]
     106iv.     Stitching Topology Service[[BR]]
     107v.      Stitching Computation Service[[BR]]
     109Based on completed design, implementation, testing, and demonstrations, we are now have a multi-aggregate stitching capability in place.
     111=== B. Project participants ===
     112Tom Lehman (MAX)[[BR]]
     113Xi Yang (MAX)[[BR]]
     116=== C. Publications (individual and organizational) ===
     117No formal publications were funded by this projects during this time period.
     120=== D. Outreach activities ===
     121The current focus of our outreach activities is thru our collaborations with other Aggregates such as ProtoGENI, ExoGENI, and GENI Rack deployment sites.
     123We have received the MAX InstaGENI rack.  This has been installed and connected to the MAX Aggregate which enables stitching thru Internet2 ION.  The MAX InstaGENI rack is also connected thru Internet2 AL2S to the GENI Mesoscale infrastructure.  This rack has completed acceptance testing and will soon be generally available for GENI community use.  We also plan to encourage more outreach to potential experimenters at University of Maryland and other universities in the MAX footprint.
     125=== E. Collaborations ===
     126As part of the activities and milestones described here, we have had extensive collaborations with many in the GENI community.  This includes CRON, ProtoGENI, ExoGENI, and GPO developers.  A large focus of our milestones during this reporting period revolved around network stitching architecture, design, and software development.  These activities required collaborations with other GENI aggregate manager developers.
     128=== F. Other Contributions ===