| 67 | | a) Work with I&M teams and the GPO to define and document a defined range of GENI environments, into which I&M tools can be successfully deployed, including: a selected set of aggregates, accessed by specified interfaces/protocols/APIs, using a selected set of experiment management and measurement orchestration tools. (March 2012) |
| 68 | | |
| 69 | | b) Define and document v1.0 GEMINI architecture, service components, interfaces and measurement data schemas, in cooperation with I&M teams and the GPO. (March 2012) |
| 70 | | |
| 71 | | c) Refactor UNIS (combined Lookup and Topology Services) to support hierarchical operation with local and global instances: [[BR]] |
| 72 | | |
| 73 | | 1. Update topology model to Rspec version 3 and AM API (February 2012) [[BR]] |
| 74 | | |
| 75 | | 2. Modifications to allow local UNIS to register with global UNIS (March 2012) [[BR]] |
| 76 | | |
| 77 | | 3. Initial deployment of persistent GENI Global I&M Registry (GGR) service, based on UNIS. (May 2012) [[BR]] |
| 78 | | |
| 79 | | 4. Complete noSQL (MongoDB) backend (September 2012) [[BR]] |
| 80 | | |
| 81 | | 5. Unify Perl and Python implementations (September 2012) [[BR]] |
| 82 | | |
| 83 | | |
| 84 | | d) Refactor LAMP/perfSONAR/Periscope/BLiPP services: [[BR]] |
| 85 | | |
| 86 | | 1. To support deployment into a defined range of GENI environments. (March 2012) [[BR]] |
| 87 | | |
| 88 | | 2. To support the flexible deployment of I&M services onto selected nodes, and the flexible configuration of I&M measurement points, including those for basic active network measurements, at each measurement node. (March, 2012) [[BR]] |
| 89 | | |
| 90 | | 3. To support dynamic deployment of I&M services, after an application has been deployed on a node. (July 2012) [[BR]] |
| 91 | | |
| 92 | | |
| 93 | | e) Refactor and extend LAMP/perfSONAR/Periscope/BLiPP services: [[BR]] |
| 94 | | |
| 95 | | 1. To collect measurement data provided by an experimenter’s application (July 2012) [[BR]] |
| 96 | | |
| 97 | | 2. To efficiently collect measurement data from MIBs in the local node (July 2012) [[BR]] |
| 98 | | |
| 99 | | f) Refactor perfSONAR Measurement Archive (MA) to Measurement Store (MS) and extend to: [[BR]] |
| 100 | | |
| 101 | | 1. Support authorization of transfers between slices (April 2012) [[BR]] |
| 102 | | |
| 103 | | 2. Support for multiple storage arrangements, including a continuum of durations (August 2012) [[BR]] |
| 104 | | |
| 105 | | 3. Support movement of measurement data objects from an MS to an iRODS-based Measurement Data Archive service, including the associated MDOD (September 2012) [[BR]] |
| 106 | | |
| 107 | | g) Refactor INSTOOLS portal service to support GEMINI and GIMI tools, to become the GENI Experimenter Portal Service [[BR]] |
| 108 | | |
| 109 | | 1. Identify use cases / concept of operations, in cooperation with the GIMI project (February 2012) [[BR]] |
| 110 | | |
| 111 | | 2. Provide first prototype (March 2012) [[BR]] |
| 112 | | |
| 113 | | 3. Initial deployment of persistent GENI Experimenter Portal Service (July 2012) [[BR]] |
| 114 | | |
| 115 | | 4. Include ability to view Periscope services (July 2012) [[BR]] |
| 116 | | |
| 117 | | 5. Include ability to orchestrate operation of measurement services (Sept 2012) [[BR]] |
| 118 | | |
| 119 | | 6. Include ability to create and edit Measurement Data Object Descriptors (MDODs) (Sept 2012) [[BR]] |
| 120 | | |
| 121 | | 7. Include ability to manage archiving of measurement data objects (Sept 2012) [[BR]] |
| 122 | | |
| 123 | | 8. Include content management features into Periscope service (December 2012) [[BR]] |
| 124 | | |
| 125 | | |
| 126 | | h) GENI Event Messaging Service (GEMS) [[BR]] |
| 127 | | |
| 128 | | 1. Identify use cases and concept of operations, in cooperation with the IMF and GIMI projects (February 2012) [[BR]] |
| 129 | | |
| 130 | | 2. Compare available technologies and prototypes, in cooperation with the IMF and GIMI projects (March 2012) [[BR]] |
| 131 | | |
| 132 | | 3. Complete initial GEMS prototype (June 2012) [[BR]] |
| 133 | | |
| 134 | | 4. Integrate initial GEMS for GEMINI 1.0 (July 2012) [[BR]] |
| 135 | | |
| 136 | | 5. Initial deployment of GENI Event Messaging Service (GEMS) (July 2012) [[BR]] |
| 137 | | |
| 138 | | |
| 139 | | i) Deliver release of GEMINI v1.0 I&M services software (July 2012) [[BR]] |
| 140 | | |
| 141 | | 1. Fully integrated, and tested for functionality and robustness [[BR]] |
| 142 | | |
| 143 | | 2. Documented [[BR]] |
| 144 | | |
| 145 | | 3. For operation in defined range of GENI environments [[BR]] |
| 146 | | |
| 147 | | 4. Deployment configurable for use by experimenters and for infrastructure measurement [[BR]] |
| 148 | | |
| 149 | | 5. With capabilities and features as noted [[BR]] |
| 150 | | |
| 151 | | |
| 152 | | j) Demonstrate, document and support the use of GEMINI I&M services to collect, analyze and present measurement data satisfying the defined use cases for instrumenting an experimenter’s slice, including: [[BR]] |
| 153 | | |
| 154 | | 1. Active IP network performance measurements, made between nodes within the slice (i.e., ping and iperf) (February 2012) [[BR]] |
| 155 | | |
| 156 | | 2. Measurement data provided by the experimenter’s application (July 2012) [[BR]] |
| 157 | | |
| 158 | | 3. Demonstrate at GEC14 (July 2012) [[BR]] |
| 159 | | |
| 160 | | 4. Tutorial for experimenters at GEC14 (July 2012) [[BR]] |
| 161 | | |
| 162 | | 5. Continuing support and bug fixes to experimenters using GEMINI I&M services (thru Sept 2012) [[BR]] |
| 163 | | |
| 164 | | |
| 165 | | k) Demonstrate, document and support the use of GEMINI I&M services to collect, analyze and present measurement data satisfying the defined infrastructure monitoring use cases, including: [[BR]] |
| 166 | | |
| 167 | | 1. A persistent infrastructure measurement slice, that provides active and/or passive measurements of the infrastructure included within the slice (February 2012) [[BR]] |
| 168 | | |
| 169 | | 2. Authentication, and basic Authorization support, for collection and presentation in another slice (June 2012) [[BR]] |
| 170 | | |
| | 68 | * [[MilestoneDate(GEMINI: S4.a Define and document a defined range of GENI environments)]] |
| | 69 | * [[MilestoneDate(GEMINI: S4.b Define and document)]] |
| | 70 | * [[MilestoneDate(GEMINI: S4.c Refactor UNIS)]] |
| | 71 | * [[MilestoneDate(GEMINI: S4.c.1 Update topology model)]] |
| | 72 | * [[MilestoneDate(GEMINI: S4.c.2 Modifications)]] |
| | 73 | * [[MilestoneDate(GEMINI: S4.c.3 Deployment)]] |
| | 74 | * [[MilestoneDate(GEMINI: S4.c.4 Complete noSQL (MongoDB) backend)]] |
| | 75 | * [[MilestoneDate(GEMINI: S4.c.5 Unify Perl and Python implementations)]] |
| | 76 | * [[MilestoneDate(GEMINI: S4.d Refactor LAMP/perfSONAR/Periscope/BLiPP services)]] |
| | 77 | * [[MilestoneDate(GEMINI: S4.d.1 Refactor LAMP/perfSONAR/Periscope/BLiPP services)]] |
| | 78 | * [[MilestoneDate(GEMINI: S4.d.2 Refactor LAMP/perfSONAR/Periscope/BLiPP services)]] |
| | 79 | * [[MilestoneDate(GEMINI: S4.d.3 Refactor LAMP/perfSONAR/Periscope/BLiPP services)]] |
| | 80 | * [[MilestoneDate(GEMINI: S4.e Refactor and extend LAMP/perfSONAR/Periscope/BLiPP services)]] |
| | 81 | * [[MilestoneDate(GEMINI: S4.e.1 Refactor and extend LAMP/perfSONAR/Periscope/BLiPP services)]] |
| | 82 | * [[MilestoneDate(GEMINI: S4.e.2 Refactor and extend LAMP/perfSONAR/Periscope/BLiPP services)]] |
| | 83 | * [[MilestoneDate(GEMINI: S4.f Refactor perfSONAR Measurement Archive (MA) to Measurement Store (MS) and extend)]] |
| | 84 | * [[MilestoneDate(GEMINI: S4.f.1 Refactor perfSONAR Measurement Archive (MA) to Measurement Store (MS) and extend)]] |
| | 85 | * [[MilestoneDate(GEMINI: S4.f.2 Refactor perfSONAR Measurement Archive (MA) to Measurement Store (MS) and extend)]] |
| | 86 | * [[MilestoneDate(GEMINI: S4.f.3 Refactor perfSONAR Measurement Archive (MA) to Measurement Store (MS) and extend)]] |
| | 87 | * [[MilestoneDate(GEMINI: S4.g "Refactor INSTOOLS portal service to support GEMINI and GIMI tools, to become the GENI Experimenter Portal Service")]] |
| | 88 | * [[MilestoneDate(GEMINI: S4.g.1 "Refactor INSTOOLS portal service to support GEMINI and GIMI tools, to become the GENI Experimenter Portal Service")]] |
| | 89 | * [[MilestoneDate(GEMINI: S4.g.2 "Refactor INSTOOLS portal service to support GEMINI and GIMI tools, to become the GENI Experimenter Portal Service")]] |
| | 90 | * [[MilestoneDate(GEMINI: S4.g.3 "Refactor INSTOOLS portal service to support GEMINI and GIMI tools, to become the GENI Experimenter Portal Service")]] |
| | 91 | * [[MilestoneDate(GEMINI: S4.g.4 "Refactor INSTOOLS portal service to support GEMINI and GIMI tools, to become the GENI Experimenter Portal Service")]] |
| | 92 | * [[MilestoneDate(GEMINI: S4.g.5 "Refactor INSTOOLS portal service to support GEMINI and GIMI tools, to become the GENI Experimenter Portal Service")]] |
| | 93 | * [[MilestoneDate(GEMINI: S4.g.6 "Refactor INSTOOLS portal service to support GEMINI and GIMI tools, to become the GENI Experimenter Portal Service")]] |
| | 94 | * [[MilestoneDate(GEMINI: S4.g.7 "Refactor INSTOOLS portal service to support GEMINI and GIMI tools, to become the GENI Experimenter Portal Service")]] |
| | 95 | * [[MilestoneDate(GEMINI: S4.g.8 "Refactor INSTOOLS portal service to support GEMINI and GIMI tools, to become the GENI Experimenter Portal Service")]] |
| | 96 | * [[MilestoneDate(GEMINI: S4.h GENI Event Messaging Service (GEMS))]] |
| | 97 | * [[MilestoneDate(GEMINI: S4.h.1 GENI Event Messaging Service (GEMS))]] |
| | 98 | * [[MilestoneDate(GEMINI: S4.h.2 GENI Event Messaging Service (GEMS))]] |
| | 99 | * [[MilestoneDate(GEMINI: S4.h.3 GENI Event Messaging Service (GEMS))]] |
| | 100 | * [[MilestoneDate(GEMINI: S4.h.4 GENI Event Messaging Service (GEMS))]] |
| | 101 | * [[MilestoneDate(GEMINI: S4.h.5 GENI Event Messaging Service (GEMS))]] |
| | 102 | * [[MilestoneDate(GEMINI: S4.i Deliver release of GEMINI v1.0 I&M services software)]] |
| | 103 | * [[MilestoneDate(GEMINI: S4.j "Demonstrate, document and support the use of GEMINI I&M services")]] |
| | 104 | * [[MilestoneDate(GEMINI: S4.j.1 "Demonstrate, document and support the use of GEMINI I&M services")]] |
| | 105 | * [[MilestoneDate(GEMINI: S4.j.2 "Demonstrate, document and support the use of GEMINI I&M services")]] |
| | 106 | * [[MilestoneDate(GEMINI: S4.j.3 "Demonstrate, document and support the use of GEMINI I&M services")]] |
| | 107 | * [[MilestoneDate(GEMINI: S4.j.4 "Demonstrate, document and support the use of GEMINI I&M services")]] |
| | 108 | * [[MilestoneDate(GEMINI: S4.j.5 "Demonstrate, document and support the use of GEMINI I&M services")]] |
| | 109 | * [[MilestoneDate(GEMINI: S4.k "Demonstrate, document and support the use of GEMINI I&M services")]] |
| | 110 | * [[MilestoneDate(GEMINI: S4.k.1 "Demonstrate, document and support the use of GEMINI I&M services")]] |
| | 111 | * [[MilestoneDate(GEMINI: S4.k.2 "Demonstrate, document and support the use of GEMINI I&M services")]] |
| | 112 | * [[MilestoneDate(GEMINI: S4.k.3 "Demonstrate, document and support the use of GEMINI I&M services")]] |
| | 113 | * [[MilestoneDate(GEMINI: S4.k.4 "Demonstrate, document and support the use of GEMINI I&M services")]] |
| | 114 | * [[MilestoneDate(GEMINI: S4.k.5 "Demonstrate, document and support the use of GEMINI I&M services")]] |
| | 115 | * [[MilestoneDate(GEMINI: S4.k.6 "Demonstrate, document and support the use of GEMINI I&M services")]] |
