Changes between Version 11 and Version 12 of MAX-GENI-Status-Report-GEC16
- Timestamp:
- 05/29/13 23:33:22 (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MAX-GENI-Status-Report-GEC16
v11 v12 32 32 The stitching topology service prototype implementation is still underway. We currently have a very basic topology service prototype 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. 33 33 34 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. We have not implemented a mechanism to pull the information from the GEMINI Topology service. The topology service final design will likely be either based on extending what we currently have embedded in the SCS or via utilizing the GEMINI Topology Service. During the next reporting period we will finalize the plan for the GENI Topology Service and continue with implementation.34 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. We have not implemented a mechanism to pull the information from the GEMINI Topology service. The topology service final design will likely be either based on extending what we currently have embedded in the SCS or via utilizing the GEMINI Topology Service. During the next reporting period we will finalize the plan for the GENI Topology Service and continue with implementation. 35 35 36 36