Changes between Version 6 and Version 7 of MAX-GENI-Status-Report-GEC13


Ignore:
Timestamp:
04/03/12 00:09:45 (12 years ago)
Author:
Tom Lehman
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MAX-GENI-Status-Report-GEC13

    v6 v7  
    4040We developed this design in the context of using "tickets" as the basis for AM resource negotiation.  The use of tickets in the GENI API is broader then just the stitching use case we present in our designs.  However, the introduction of tickets into the GENI AM API, is still under discussion by the GENI development community.  For this reason, we expect that we will have to modify some aspects of the above design.    We are planning next to discuss these concepts with the AM developers from ProtoGENI, ORCA, and !OpenFlow.  We will also seek broader community inputs once there is a loose consensus on the basic mechanism in the GENI AM API for a "ticket" mechanism or something similar as currently being discussed.   We believe that the general stitching/w negotiation design we have defined can be easily adapted to any of the specifics that the GENI AM development community is now discussing in this area.
    4141
    42 In addition to work to finalize the Stitching w/negotiation design, we will also continue toward the implementation and deployment of the Stitching Extension schemas and the basic workflow stitching (i.e., no negotiation required)  across from ProtoGENI, ORCA, MAX, ION, and !OpenFlow Aggregates.
     42In addition to work to finalize the Stitching w/negotiation design, we will also continue working toward the implementation and deployment of the Stitching Extension schemas and the basic workflow stitching (i.e., no negotiation required)  between ProtoGENI, ORCA, MAX, ION, and !OpenFlow Aggregates.
    4343
    4444We demonstrated multi-aggregate stitching across the MAX and CRON Aggregates at GEC13.  This included the provision of resources across the MAX Aggregate, CRON Aggregate, Internet2 ION, and LONI Regional network.  This demonstration contains many of the elements needed for the basic stitching workflow.  However, there is more implementation and workflow design to be completed before we have an experimenter ready multi-aggregate stitching capability.    These remaining tasks are described below.