| | 1 | = GENI MAX Stitching Project Status Report - Post GEC17 = |
| | 2 | Project Status Report[[BR]] |
| | 3 | Project 1658 (MAX)[[BR]] |
| | 4 | Status Report [[BR]] |
| | 5 | Post GEC 17 (July 21-23, 2013) Report[[BR]] |
| | 6 | |
| | 7 | == I. Major accomplishments == |
| | 8 | === A. Milestones status === |
| | 9 | [[BR]] This status report provides a status for the milestones worked on during the time period between GEC16 and just after GEC17. Status of other milestones are covered in the previous Status reports and the Final Report for this project.[[BR]] |
| | 10 | |
| | 11 | |
| | 12 | __''MAX: S4.e: Prototype GENI Topology and Path Computation Services''__[[BR]] |
| | 13 | * Initial Prototype: January 2013 |
| | 14 | * Production Ready Service: May 1, 2013 |
| | 15 | * Prototype GENI Topology and Path Computation Services (previous SOW is just for a design) |
| | 16 | |
| | 17 | |
| | 18 | ''Status:''[[BR]] |
| | 19 | We have completed a version of the Stitching Computation Service (SCS). This has been utilized for development of the workflow service and is available for general use. A description of the SCS is available here: |
| | 20 | * https://wiki.maxgigapop.net/twiki/bin/view/GENI/NetworkStitchingAPI |
| | 21 | |
| | 22 | The SCS software is available here: |
| | 23 | * https://wiki.maxgigapop.net/twiki/bin/view/GENI/NetworkStitchingSoftware |
| | 24 | |
| | 25 | The SCS service was tested as part of the GENI Network Stitching Plan as described here: |
| | 26 | * http://groups.geni.net/geni/wiki/GeniNetworkStitchingTestPlan |
| | 27 | |
| | 28 | The stitching topology service prototype implementation is implemented as part of the computation service. This provides the topology information that the SCS needs, but does not currently provide a generally available query mechanism or an automated update function via GENI AM API calls. |
| | 29 | |
| | 30 | We have also been working with the GEMINI project to utilize their topology services for stitching services. They have implemented the ability to dynamically and automatically obtain topology information from the GENI AM API as well as the existing PerfSonar Topology Service. Additional coordination with the GEMINI group is needed to determine if their topology service will be the basis for a more generally available service. Future topology service functionality will likely be either based on extending what we currently have embedded in the SCS or via utilizing the GEMINI Topology Service. |
| | 31 | |
| | 32 | |
| | 33 | |
| | 34 | [[BR]] |
| | 35 | __''MAX: S4.f: Prototype shared GENI Stitching Workflow Service, based on Omni libstitch library, and use it from Omni, and make it available to Flack''__[[BR]] |
| | 36 | * Initial Prototype: February 2013 |
| | 37 | * Production Ready Service: May 1, 2013 |
| | 38 | |
| | 39 | ''Status:''[[BR]] |
| | 40 | The Stitching Computation Service (SCS) includes functionality to generate workflow data as part of experimenter RSpec computation requests. OMNI developers are utilizing this workflow data as input for stitching library which is implemented as part of the OMNI package. This functionality was demonstrated as part of the GENI Network Stitching Test Plan activity noted above, and also demonstrated during GEC 17. The SCS service is available to Flack. We have worked with the Flack developer to get proper Flash security policies running on ION and MAX AM, and allow access to SCS by Flack. There is expected to be continued work in this area to make this part of the standard Flack experience and also associated with the upgrade to Flack to be HTML5 based. |
| | 41 | |
| | 42 | |
| | 43 | [[BR]] |
| | 44 | __''MAX: S4.g: Update MAX/ION AMs to AM API v3 and to work with above services''__[[BR]] |
| | 45 | * Initial Prototype: March 2013 |
| | 46 | * Production Ready Version: May 30, 2013 |
| | 47 | |
| | 48 | ''Status:''[[BR]] |
| | 49 | We have completed initial design work for the update of the MAX AM API v3. The support for GENI AM APIv3 by other GENI Aggregates (ProtoGENI and ExoGENI) was not available during this time period. As a result we focused on additional stitching activities and are planning to complete the MAX AM APIv3 implementation and upgrade in December 2013. |
| | 50 | |
| | 51 | [[BR]] |
| | 52 | __''MAX: S4.h: Demo an InstaGENI and an ExoGENI rack stitched dynamically together using above services across a backbone at GEC16 |
| | 53 | * Initial InstaGENI and ExoGENI stitching demonstration: March 2013 (GEC 16) |
| | 54 | * Experimenter ready InstaGENI and ExoGENI stitching capability: May 30, 2013 |
| | 55 | |
| | 56 | ''Status:''[[BR]] |
| | 57 | We demonstrated stitching between InstaGENI Racks at Utah, ProtoGENI main, and GPO ExoGENI Rack resources connected across ION during GEC17. This included a slice topology with three GENI AMs. The details for this demonstration are available here: |
| | 58 | |
| | 59 | * https://wiki.maxgigapop.net/twiki/bin/view/GENI/Publications#GENI_Engineering_Conference_17_J |
| | 60 | |
| | 61 | |
| | 62 | |
| | 63 | === B. Deliverables made === |
| | 64 | During this reporting period we completed the following deliverables: |
| | 65 | |
| | 66 | GEC17 Stitching Demonstration |
| | 67 | * geni.maxgigapop.net ====> Publications ====> GEC17 |
| | 68 | or direct |
| | 69 | * https://wiki.maxgigapop.net/twiki/bin/view/GENI/Publications#GENI_Engineering_Conference_17_J |
| | 70 | * http://groups.geni.net/geni/wiki/GEC17Agenda/EveningDemoSession |
| | 71 | |
| | 72 | Stitching Computation Service (SCS) Design |
| | 73 | * https://wiki.maxgigapop.net/twiki/bin/view/GENI/NetworkStitchingAPI |
| | 74 | |
| | 75 | The SCS software: |
| | 76 | * https://wiki.maxgigapop.net/twiki/bin/view/GENI/NetworkStitchingSoftware |
| | 77 | |
| | 78 | |
| | 79 | == II Description of work performed during last quarter == |
| | 80 | === A. Activities and findings === |
| | 81 | |
| | 82 | Based 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. |
| | 83 | |
| | 84 | We have a well defined stitching architecture which consists of the following components:[[BR]] |
| | 85 | |
| | 86 | i. Stitching Extensions for RSpec Schemas[[BR]] |
| | 87 | ii. Stitching !WorkFlow Function (basic and w/negotiation)[[BR]] |
| | 88 | iii. GENI AM API Extensions for Stitching[[BR]] |
| | 89 | iv. Stitching Topology Service[[BR]] |
| | 90 | v. Stitching Computation Service[[BR]] |
| | 91 | |
| | 92 | Based on completed design, implementation, testing, and demonstrations, we are now have a multi-aggregate stitching capability in place. |
| | 93 | |
| | 94 | === B. Project participants === |
| | 95 | Tom Lehman (MAX)[[BR]] |
| | 96 | Xi Yang (MAX)[[BR]] |
| | 97 | |
| | 98 | |
| | 99 | === C. Publications (individual and organizational) === |
| | 100 | No formal publications were funded by this projects during this time period. |
| | 101 | |
| | 102 | |
| | 103 | === D. Outreach activities === |
| | 104 | The current focus of our outreach activities is thru our collaborations with other Aggregates such as ProtoGENI, ExoGENI, and GENI Rack deployment sites. |
| | 105 | |
| | 106 | We have received the MAX InstaGENI rack. This has been placed in a equipment room on the UMD College Park campus. Installation and configuration will be completed in August and September 2013. Once this InstaGENI rack is available, we plan to reach out to potential experimenters at University of Maryland and other universities in the MAX footprint. |
| | 107 | |
| | 108 | === E. Collaborations === |
| | 109 | As 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. |
| | 110 | |
| | 111 | === F. Other Contributions === |
| | 112 | none. |
