Changes between Initial Version and Version 1 of MAX-GENI-Status-Report-GEC15


Ignore:
Timestamp:
12/09/12 18:33:02 (11 years ago)
Author:
Tom Lehman
Comment:

--

Legend:

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

    v1 v1  
     1= GENI MAX  Stitching Project Status Report - Post GEC15 =
     2
     3
     4==  I. Major accomplishments ==
     5=== A. Milestones status ===
     6
     7__''MAXREGIONAL: S4.c: Demonstration at GEC15''__[[BR]]
     8(10/31/12)[[BR]]
     9Work with Internet2 and MAX to deploy a stitching prototype ION/DYNES AM and a stitching prototype MAX AM that provides appropriate functions for an end-to-end stitching demo between MAX and CRON. (CRON AM is covered under CRON SOW.) Assumptions: This deployment will be of ION/DYNES AM based on MAX AM.
     10
     11''Status:''[[BR]]
     12In this demonstration we showed multi-aggregate stitching between the MAX, ION, CRON, LONI, and ProtoGENI Aggregates.  Use of the MAX Aggregate Manager (AM) which is compatible with the GENIv3 RSpec formats was demonstrated. An instance of MAX AM was utilized to cover ION and LONI networks.  This functionality was described in the context of the larger multi-aggregate stitching architecture vision consisting of a GENI Topology Service, Computation Service, GENI AM APIv3, and multi-aggregate slice instantiation workflows.
     13
     14More detailed descriptions of this demonstration, including example RSpecs and demo scripts are located here:
     15
     16   * https://geni.maxgigapop.net/twiki/bin/view/GENI/Publications  ====> GEC15
     17
     18We are now working with Internet2 to have the ION GENI AM capability deployed and managed by the Internet2 NOC. 
     19
     20This milestone is complete.
     21
     22
     23__''MAXREGIONAL: S4.d: MAX is an operational GENI aggregate''__[[BR]]
     24(GEC15) (10/25/12)[[BR]]
     25   * Implement the GENI AM API v3
     26   * Provide resources to experimenter credentials signed by one of the GENI slice authorities
     27   * Agree to the GENI Aggregate Providers Agreement
     28   * Updated description of the MAX aggregate on the GENI wiki including a description of resources available to experimenters.
     29
     30''Status:''[[BR]]
     31The MAX AM has been upgraded to be compatible with GENI AM APIv3.   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.   
     32
     33We 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.
     34
     35
     36
     37=== B. Deliverables made ===
     38During this reporting period we completed the following deliverables:
     39
     40GEC14 Stitching Demonstration
     41   * geni.maxgigapop.net  ====> Publications  ====> GEC15
     42        or direct
     43   * https://geni.maxgigapop.net/twiki/bin/view/GENI/Publications#GENI_Engineering_Conference_15_O
     44   * http://groups.geni.net/geni/wiki/GEC15Agenda/EveningDemoSession#Mid-AtlanticCrossroadsMAX
     45
     46MAX Aggregate Manager support for GENI v3 RSpecs:
     47   * https://geni.maxgigapop.net/twiki/bin/view/GENI/MaxRspec
     48
     49MAX Aggregate Manager federated with ProtoGENI and PlanetLab and available for use via user and slice credentials from these aggregates.
     50
     51==  II Description of work performed during last quarter ==
     52=== A. Activities and findings ===
     53
     54Based on the work we have completed with our prototype deployments of ION and LONI GENI Aggregate Managers, we believe we are ready for a more production level deployment.  We have started working with Internet2 NOC to deploy an instance of a GENI AM that they will maintain and support on a trial basis.
     55
     56We have a well defined stitching architecture which consists of the following components:[[BR]]
     57
     58i.      Stitching Extensions for RSpec Schemas[[BR]]
     59ii.     Stitching !WorkFlow Function (basic and w/negotiation)[[BR]]
     60iii.    GENI AM API Extensions for Stitching[[BR]]
     61iv.     Stitching Topology Service[[BR]]
     62v.      Stitching Computation Service[[BR]]
     63
     64Based on already completed design, implementation, testing, and demonstrations, the indications are that we will be able to implement a GENI multi-aggregate stitching capability which will satisfy the needs of the initial GENI Rack deployments as well as other sites which will have GENI Aggregate Managers.  Now that the GENI AM API v3 has been finalized, we will need to update the current design for item ii (stitching w/ negotiation).  These updates are primarily message type and format in nature, and do not change the planned architecture or design.
     65
     66This initial capability set will likely be based on items i and iii (with basic stitching workflow).  This capability will allow GENI experimenters to utilize the initially deployed infrastructure to instantiate slices which span multiple aggregates.  Parallel to this initial stitching deployment, work will continue on items ii (stitching w/negotiation), and iv-v to prepare for larger scale deployments.
     67
     68
     69=== B. Project participants ===
     70Tom Lehman (MAX)[[BR]]
     71Xi Yang (MAX)[[BR]]
     72
     73
     74=== C. Publications (individual and organizational) ===
     75No formal publications were funded by this projects during this time period.
     76
     77
     78=== D. Outreach activities ===
     79The current focus of our outreach activities is thru our collaborations with other Aggregates such as CRON, ProtoGENI, ExoGENI, and GENI Rack deployment sites.  We also plan to encourage more outreach to potential experimenters at University of Maryland and other universities in the MAX footprint.
     80
     81We are participating in conversations with the NSF CC-NIE community to discuss GENI.  We also have a NSF CC-NIE project at MAX and will be working on the integration of this with our GENI capabilities on UMD campus and MAX member institutions.
     82
     83
     84=== E. Collaborations ===
     85As part of the activities and milestones described here, we have had extensive collaborations with many in the GENI community.  This includes CRON, ProtoGENI, ExoGENI, 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.
     86
     87=== F. Other Contributions ===
     88none.