Changes between Version 3 and Version 4 of MAX-GENI-Status-Report-GEC16

05/29/13 22:29:43 (9 years ago)
Tom Lehman



  • MAX-GENI-Status-Report-GEC16

    v3 v4  
    15 __''MAXREGIONAL: S4.e:  Prototype GENI Topology and Path Computation Services''__[[BR]]
    16 (GEC15) (10/25/12)(partially complete) [[BR]]
     15__''MAXREGIONAL: S4.e:  Prototype GENI Topology and Path Computation Services''__[[BR]]
    1716  * Initial Prototype:  January 2013
    1817  * Production Ready Service:  May 1, 2013
    23 The 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.  Prototype ION and LONI AMs (based on the MAX AM) have also been deployed for experimental use.   
     22We have completed an initial version of the Stitching Computation Service (SCS).   This has been utilized for development of the workflow service (which is the next milestone).  A description of the SCS is available here:
     23   *
    25 We have some remaining items on this milestone. This includes updating the MAX Aggregate Information on the GENI Wiki, and returning the GENI Aggregate Providers Agreement.  This milestone is partially complete pending completion of these items.
     25The SCS software is available here:
     26   *
     28We consider this software to be beyond prototype, but not yet transitioned to operational use.  This transition will happen as part of the conduct of the Stitching Testing defined here:
     29   *
     31The stitching topology service  prototype implementation is still underway.  We currently have a very basic topology service prototype 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.
     33We 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.   We have not implemented a mechanism to pull the information from the GEMINI Topology service.  The topology service final design will likely be either based on extending what we currently have embedded in the SCS or via utilizing the GEMINI Topology Service. During the next reporting period we will finalize the plan for the GENI Topology Service and continue with implementation.