Changes between Version 2 and Version 3 of MAX-GENI-Status-Report-GEC13


Ignore:
Timestamp:
04/02/12 23:36:28 (12 years ago)
Author:
Tom Lehman
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • MAX-GENI-Status-Report-GEC13

    v2 v3  
    77The milestones due during this reporting period are listed below:
    88
    9 __MAX: S4.a: Incorporation of Stitching Extension into OpenFlow AMs__
     9__MAX: S4.a: Incorporation of Stitching Extension into !OpenFlow AMs__
    1010
    11 Work with FOAM developer so that OpenFlow AM or other AMs that include Openflow switches support basic stitching through OpenFlow switches in the GENI mesoscale network.  This will include support for current stitching schema in advertisements RSpec, request RSpecs, and manifest RSpecs.  Support for the AM API negotiation extensions and Tree mode workflow will also be included.  Stitching technology for this task will focus on VLANs with objective to make the OpenFlow AM interoperate with other AMs for GENI stitching.  Share design on GENI wiki and in GENI mailing lists, and present at GEC13.
     11Work with FOAM developer so that !OpenFlow AM or other AMs that include !Openflow switches support basic stitching through !OpenFlow switches in the GENI mesoscale network.  This will include support for current stitching schema in advertisements RSpec, request RSpecs, and manifest RSpecs.  Support for the AM API negotiation extensions and Tree mode workflow will also be included.  Stitching technology for this task will focus on VLANs with objective to make the !OpenFlow AM interoperate with other AMs for GENI stitching.  Share design on GENI wiki and in GENI mailing lists, and present at GEC13.
    1212
    1313
    1414Status:[[BR]]
    1515
    16 We have completed a design for how OpenFlow AMs can include the GENI Stitching Extension as part of their Advertisement, Request, and Manifest RSpecs.  This is presented here:
     16We have completed a design for how !OpenFlow AMs can include the GENI Stitching Extension as part of their Advertisement, Request, and Manifest RSpecs.  This is presented here:
    1717
    18 OpenFlow Aggregate included in Stitching Workflow:
     18!OpenFlow Aggregate included in Stitching Workflow:
    1919   * https://geni.maxgigapop.net/twiki/bin/view/GENI/NetworkStitchingGeniApiAndRspec
    2020
    21 Here is a direct link to an example OpenFlow Advertisement RSpec with Stitching:
     21Here is a direct link to an example !OpenFlow Advertisement RSpec with Stitching:
    2222   * https://geni.maxgigapop.net/twiki/pub/GENI/NetworkStitchingGeniApiAndRspec/bbn-of-advertisement-v1.xml
    2323
    … …  
    2626The RSpec Stitching Schema Extension can be used for GENI Stitching workflows with or without negotiation.  We developed this design in the context of a multi-aggregate stitching operation which included a set of GENI AM API extensions to support stitching with negotiation. See MAX:S4.b for an extended discussion on GENI Stitching workflows options, implementation, and deployment plans.
    2727
    28 We still need to coordinate with the FOAM developer on the incorporation of these Stitching Extensions into the OpenFlow AM.   We will do this prior to GEC14.
     28We still need to coordinate with the FOAM developer on the incorporation of these Stitching Extensions into the !OpenFlow AM.   We will do this prior to GEC14.
    2929
    3030__MAX: S4.b:  Help Define GENI AM API Extensions to support Stitching w/negotiation__
    … …  
    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/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 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.
    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.
    … …  
    5555    * review stitching workflow with negotiation design
    5656    * review stitching workflow steps for both basic ORCA aggregate and the "ORCA" GeniRack.
    57 Work with OpenFlow AM developers:
     57Work with !OpenFlow AM developers:
    5858    * assist them with initial implementation of Stitching Extension
    5959    * verify proper use of Stitching Extension with basic stitching workflow
    … …  
    7474    * https://geni.maxgigapop.net/twiki/bin/view/GENI/NetworkStitchingGeniApiAndRspec
    7575
    76 Initial Design for OpenFlow use of Stitching Extension:
     76Initial Design for !OpenFlow use of Stitching Extension:
    7777    * geni.maxgigapop.net  ====> Publications   or direct
    7878    * https://geni.maxgigapop.net/twiki/pub/GENI/NetworkStitchingGeniApiAndRspec/bbn-of-advertisement-v1.xml
    … …  
    9393
    9494i.      Stitching Extensions for RSpec Schemas
    95 ii.     Stitching WorkFlow Function (basic and w/negotiation)
     95ii.     Stitching !WorkFlow Function (basic and w/negotiation)
    9696iii.    GENI AM API Extensions for Stitching
    9797iv.     Stitching Topology Service
    … …  
    115115
    116116=== E. Collaborations ===
    117 As part of the activities and milestones described here, we have had extensive collaborations with many in the GENI community.  This includes CRON, ProtoGENI, PlanetLab, 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.
     117As part of the activities and milestones described here, we have had extensive collaborations with many in the GENI community.  This includes CRON, ProtoGENI, !PlanetLab, 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.
    118118
    119119=== F. Other Contributions ===