Changes between Version 3 and Version 4 of MAX-GENI-Status-Report-2011-08-20


Ignore:
Timestamp:
08/31/11 07:28:38 (10 years ago)
Author:
Tom Lehman
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MAX-GENI-Status-Report-2011-08-20

    v3 v4  
    1717
    1818Status:[[BR]]
    19 We generated extensive documentation on stitching in general and on a specific GENI Stitching Architecture.  This included the following documents:
    2019
    21    * GENI Network Stitching Architecture - Overview
    22      This document provides an overview of a proposed stitching architecture.
    23    * GENI Network Stitching Architecture - Example[[BR]]This document provides an example of the proposed architecture base on Use Cases.
    24    * GENI Network Stitching Component Design - Example[[BR]]This document provides an example of a specific design for each of the architecture components. The intent is to convince ourselves that a detailed design can be develop to support the proposed architecture, not necessarily to define the final design details.
    25    * GENI Network Stitching Schema Example[[BR]]This is an xsd file of an example Common Stitching Topology Schema.
    26    * GENI Network Stitching RSPEC Instance Example[[BR]] The is an example instantiation of a Stitching Resource Element (Stitching RSPEC info) that an Aggregate would use to describe an external link to another aggregate. In this example, the MAX Aggregate is describing an external link to the !ProtoGENI Aggregate. This Stitching RSPEC is in accordance with the above schema. 
    27    * The same Stitching RSPEC instance as above was also formatted in accordance with the !ProtoGENI RSPEC v2 schema.
     20The MAX GENI Aggregate has now transitioned to operational aggregate status. This includes the following capabilities and features:
     21   * Compliant with the latest GENI AM API
     22   * Federated with Princeton PlanetLab and ProtoGENI allowing for User and Slice Credential Exchange
     23   * Exports Status to GMOC via the MyPLC based Plastic Slices monitoring capability
     24      * Plastic Slices Monitoring information is available here: http://groups.geni.net/geni/wiki/PlasticSlices/MonitoringRecommendations/MyplcConfiguration
     25      * MAX site is selectable here: https://gmoc-db.grnoc.iu.edu/api-demo
     26   * Prepared to support GMOC as required for MAX GENI operations
    2827
    29 All of these documents and additional information on stitching is available at the web site below:
     28A high level diagram of the MAX Aggregate Manager architecture is show below.
    3029
    31    * https://geni.maxgigapop.net/twiki/bin/view/GENI/NetworkStitching
    3230
    33 We also organized multiple teleconferences with various organizations and groups including ProtoGENI, !OpenFlow, and ORCA/BEN.
     31__MAX.S3.e:  Demonstration and outreach at GEC11__
    3432
    35 __MAX.S3.c:  Demonstration and outreach at GEC10__
     33   * Demonstrate updated MAX Aggregate Manager design, functions, and user interface. This should include demonstration of an operational workflow showing how a GENI researcher goes from initial request, to experiment topology instantiation, to operational support functions, to experiment termination.
     34   * Demonstrate trust of all four GENI clearinghouses
     35   * Organize workshop on network stitching (if the community feels a need for such a workshop). This workshop would be similar in focus and objectives to the GEC10 workshop.
    3636
    37    * Demonstrate updated MAX Aggregate Manager design, functions, and user interface. This demonstration should include instantiation of GENI Experiment Topologies which crosses multiple GENI Aggregates.
    38 
    39    * Organize a workshop on network stitching in GENI. The objective of this workshop will be to discuss architecture and design alternatives for multi-aggregate network stitching in GENI. The target participation group is the GENI design and development community. The specific topics will be determined in consultation with the GPO and the larger community. The anticipated topics include: what is the GENI Network Stitching architecture and design? should this service be integrated natively into GENI AMs or as a higher level service built on top of the control framework? Who is responsible for implementing this service? How do users access the stitching services? What is the operational model for this service in terms of monitoring and troubleshooting? What is the current state of network stitching in GENI, and how do we evolve to a broadly available and supportable GENI network stitching service from here?
    4037
    4138Status:[[BR]]
    42 We completed the first item of this milestone via our demonstration at GEC10.  This demonstration showed how the !PlanetLab SFI/SFA can be used to submit requests to the Mid-Atlantic Crossroads (MAX) GENI Aggregate Manager (AM) for the purpose of dynamic instantiation of an experiment topology.  The dynamically instantiated topologies were constructed from a diverse set of resources including !PlanetLab slices, dynamically provisioned network paths across the MAX network, and dynamically provisioned network paths across !ProtoGENI and Internet2 ION.  Details on this demo and the associated MAX AM Functionality are available here:
     39We updated our extensive documentation on stitching in general and on a specific GENI Stitching Architecture.  This included the following documents:
    4340
    44    * http://geni.maxgigapop.net/twiki/bin/view/GENI/Publications  ===> GEC10
     41   * GENI Stitching Description and Examples
     42      * https://geni.maxgigapop.net/twiki/bin/view/GENI/NetworkStitchingOverview
     43   * GENI Network Stitching Architecture - Overview
     44      * This document provides an overview of a proposed stitching architecture.
     45   * GENI Network Stitching Architecture - Example
     46      * This document provides an example of the proposed architecture base on Use Cases.
     47   * GENI Network Stitching Component Design - Example
     48      * This document provides an example of a specific design for each of the architecture components. The intent is to convince ourselves that a detailed design can be develop to support the proposed architecture, not necessarily to define the final design details.
     49   * GENI Network Stitching Schema Example
     50      * This is an xsd file of an example Common Stitching Topology Schema.
     51   * GENI Network Stitching RSPEC Instance Example
     52      * The is an example instantiation of a Stitching Resource Element (Stitching RSPEC info) that an Aggregate would use to describe an external link to another aggregate. In this example, the MAX Aggregate is describing an external link to the ProtoGENI Aggregate. This Stitching RSPEC is in accordance with the above schema. 
     53      * The same Stitching RSPEC instance as above was also formatted in accordance with the ProtoGENI RSPEC v2 schema.
    4554
    46 This includes slides, the Demonstration Poster, Slice RSpecs, and commands which can be used to provision resources on MAX, !ProtoGENI, and Internet2 ION.
     55We also organized multiple teleconferences and worked with with various organizations and groups including ProtoGENI, PlanetLab, GPO, OpenFlow, and ORCA/BEN.
    4756
    48 We also took advantage of the GEC10 to conduct outreach and coordination with users for the MAX GENI Substrate.  This included planning sessions and discussions with the following groups:
    49 
    50    * ERM Project, Columbia University, Lightwave Research Laboratory[[BR]]A collaboration is planned which includes placement of instrumentation device in the MAX network by the ERM project as part of GENI experiment and development activity
    51 
    52    * iGENI Project[[BR]]A collaboration is planned between the MAX and iGENI projects to interconnect our aggregates.  This will include a 10 Gbps connection (across NLR) between the MREN facilities in Chicago and the MAX node in !McLean Virginia
    53 
    54    * Capital College[[BR]] Initial discussions were held with a researcher from Capital College who is interested in using GENI.  This college is within the MAX regional footprint in Washington D.C.  Further conversations are planned to see how to best make MAX GENI and the larger GENI infrastructure available for their use.
    55 
    56 We plan to follow up with these projects and individuals as part of future GENI experimentation activities.
    57 
    58 For the second item we organized a GENI Stitching Workshop which was held at GEC10.  This included many pre-GEC10 activities including document preparation, teleconferences, and other workshop planning activities.  The following web sites contain additional information about the workshop preparation and workshop event.
    59 
    60    * Pre-Workshop Preparations:[[BR]]https://geni.maxgigapop.net/twiki/bin/view/GENI/NetworkStitching
    61 
    62    * GEC10 Stitching Workshop:[[BR]]http://groups.geni.net/geni/wiki/GEC10Stitching
    6357
    6458=== B. Deliverables made ===
    65 During this reporting period we completed our deliverables for the GENI Network Stitching paper development, Stitching Workshop, and GEC10 Demonstration an Outreach.  These are documented at the following web sites:
     59Stitching paper development, Stitching Workshop, and GEC11 Demonstration an Outreach.  These are documented at the following web sites:
    6660
    67    * Network Stitching Papers:[[BR]]https://geni.maxgigapop.net/twiki/bin/view/GENI/NetworkStitching
     61   * Network Stitching Information:
     62      * http://geni.maxgigapop.net/twiki/bin/view/GENI/NetworkStitchingOverview
     63      * http://geni.maxgigapop.net/twiki/bin/view/GENI/NetworkStitchingRpecsandWorkFlow
     64      * http://geni.maxgigapop.net/twiki/bin/view/GENI/NetworkStitchingWorkFlowExamples
    6865
    69    * Network Stitching Workshop:[[BR]]http://groups.geni.net/geni/wiki/GEC10Stitching
     66   * Network Stitching Documents:
     67http://geni.maxgigapop.net/twiki/bin/view/GENI/NetworkStitching
     68      * GENI Network Stitching Architecture - Overview
     69      * GENI Network Stitching Architecture - Example
     70      * GENI Network Stitching Component Design - Example
     71      * GENI Network Stitching AM Extension Design Proposal
     72      * GENI Network Stitching Schema Example
     73      * GENI Network Stitching RSPEC Instance Example
    7074
    71    * GEC10 Demonstration and Outreach:[[BR]]http://geni.maxgigapop.net/twiki/bin/view/GENI/Publications  ===> GEC10
     75   * Network Stitching Workshop:
     76http://groups.geni.net/geni/wiki/GEC11Stitching
     77
     78   * GEC11 Demonstration and Outreach:
     79http://geni.maxgigapop.net/twiki/bin/view/GENI/Publications  ===> GEC11
     80
    7281
    7382==  II Description of work performed during last quarter ==
    7483=== A. Activities and findings ===
    75 As a result of our initial stitching implementation in the MAX Aggregate Manager users now have the ability to include stitching across !ProtoGENI and Internet2 ION infrastructures as part of MAX GENI Slices.  We leveraged this work to develop a proposed GENI Stitching Architecture and held multiple conversations with interested parties.  Our key finding is that the proposed stitching architecture provides a point from which we can move forward on the development of the general GENI stitching capability.
     84As a result of our initial stitching implementation in the MAX Aggregate Manager users now have the ability to include stitching across ProtoGENI and Internet2 ION infrastructures as part of MAX GENI Slices.  We leveraged this work to develop a proposed GENI Stitching Architecture and held multiple conversations with interested parties.  Our key finding is that the proposed stitching architecture provides a point from which we can move forward on the development of the general GENI stitching capability.
    7685
    7786=== B. Project participants ===
     
    8493We have produced several internal documents as part of our stitching work:
    8594
    86    * Network Stitching Papers:[[BR]]https://geni.maxgigapop.net/twiki/bin/view/GENI/NetworkStitching
     95   * Network Stitching Papers:
     96https://geni.maxgigapop.net/twiki/bin/view/GENI/NetworkStitchingOverview
     97
    8798
    8899=== D. Outreach activities ===
    89 We are continuing to reach out to potential GENI users as part of our collaborations with other GENI community members as described in our milestone status above and collaborations section below.
     100We are continuing to reach out to potential GENI users as part of our collaborations with other GENI community members as described in our milestone status above and collaborations section below
    90101
    91102=== E. Collaborations ===
    92 In addition to the outreach and collaboration activities described in the milestone section above, below are collaborations which were initiated during previous reporting periods.   We will maintain this list here as we expect additional collaborations in the future.
    93 
    94    * GpENI, UNL: We have had collaborations with the !GpENI project.  In particular we have been working with the University of Nebraska Lincoln (UNL) to build GENI Experiment topologies which span our Aggregates.  This has involved interconnection of our substrates across !ProtoGENI and Internet ION network infrastructures.  We expect that this collaboration will continue to expand in the future.
    95 
    96    * JGN2, !CoreLab:  We have had initial discussion and conducted initial testing with the JGN2 and !CoreLab (Japan Research Network and !PlanetLab deployment) team.  We have plans to build GENI Experiment topologies which will include resources from MAX AM and JGN2/CoreLab as part of future activities.
     103As part of the activities and milestones described here, we have had extensive collaborations with many in the GENI community.  This includes 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.
    97104
    98105=== F. Other Contributions ===