Changes between Version 9 and Version 10 of MAX-GENI-Status-Report-GEC13


Ignore:
Timestamp:
04/03/12 11:22:24 (7 years ago)
Author:
Tom Lehman
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MAX-GENI-Status-Report-GEC13

    v9 v10  
    1 = GENI MAX Project Status Report =
     1= GENI MAX  Stitching Project Status Report =
    22'''Post GEC 13 (March 13-15, 2012) Report'''[[BR]]
    33'''Period: Jan 26 - GEC13'''
     
    3838   * https://geni.maxgigapop.net/twiki/bin/view/GENI/NetworkStitchingGeniApiAndRspec
    3939
    40 We 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.
     40We 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 with 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
    4242In 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.