285 | | What persistent operational services must be supported: [[BR]] |
286 | | a) Descriptor registry required? use UNIS? DOR? iRODS? IF-MAP? [[BR]] |
287 | | b) Object registry required? use DOR? [[BR]] |
288 | | c) XML Messaging service [[BR]] |
289 | | d) Measurement Information (MI)service [[BR]] |
290 | | e) GENI User services [[BR]] |
291 | | f) Digital Object Archive (DOA) service [[BR]] |
292 | | Can all services can be shared by GIMI and GEMINI tools? [[BR]] |
293 | | How do these relate to other GENI services/functions, including clearinghouse? |
294 | | |
| 284 | Continue INSTOOLS portal-to-GUIs service, to allow user to locate GUIs within their slice, for use with INSTOOLS and GEMINI tools [[BR]] |
| 285 | |
| 286 | Summary |
| 287 | Current configuration [ slides] [[BR]] |
| 288 | Proposed configuration [ slides] [[BR]] |
| 289 | Operations plan [ slides] [[BR]] |
| 290 | |
| 291 | Discussion |
| 292 | How are partitions for different users managed? [[BR]] |
| 293 | How is authorization for a user done? [[BR]] |
| 294 | What additional features are under consideration? |
| 295 | Will the GIMI project want to use the INSTOOLS portal-to-GUIs service? [[BR]] |
| 296 | Will other parts of GENI want to use the INSTOOLS portal-to-GUIs service? [[BR]] |
| 297 | Do we need a breakout session for further discussion? when? [[BR]] |
305 | | The MI service will be built by the GEMINI project using UNIS technology; see the Spiral 4 SOW of the GEMINI project for the detailed steps, which include: [[BR]] |
306 | | 1) Refactor UNIS (combined Lookup and Topology Services) to support hierarchical operation with local and global instances: [[BR]] |
307 | | 2) Update topology model to Rspec version 3 and AM API (February 2012) [[BR]] |
308 | | 3) Modifications to allow local UNIS to register with global UNIS (March 2012) [[BR]] |
309 | | 4) Initial deployment of persistent GENI Global I&M Registry (GGR) service, based on UNIS. (May 2012) [[BR]] |
310 | | 5) Complete noSQL (MongoDB) backend (September 2012) [[BR]] |
311 | | 6) Unify Perl and Python implementations (September 2012) [[BR]] |
312 | | Define, prototype, demonstrate and operate a MI service, starting in May, 2012. [[BR]] |
313 | | Support use in GENI by many tools, including GEMINI and GIMI I&M tools [[BR]] |
314 | | Define operations plan for MI service. [[BR]] |
315 | | |
316 | | [wiki:InstMeasTopic_4.7LookupService Work in Progress] [[BR]] |
317 | | |
318 | | Summary of current status: (Ahmed El-Hassany) [[BR]] |
319 | | [http://groups.geni.net/geni/attachment/wiki/GEC13Agenda/InstrumentationAndMeasurement/T7%29%20%20GEC13.pdf slides] [[BR]] |
| 305 | Continue Unified Network Information Service (UNIS), to provide combined Lookup and Topology Services, initially for use with GEMINI tool set. |
| 306 | |
| 307 | Summary |
| 308 | [wiki:InstMeasTopic_4.7LookupService Work in Progress] [[BR]] |
| 309 | Current configuration [ slides] [[BR]] |
| 310 | Proposed configuration [ slides] [[BR]] |
| 311 | Operations plan [ slides] [[BR]] |
| 312 | |
| 313 | Discussion |
| 314 | Will you refactor UNIS (combined Lookup and Topology Services) to support hierarchical operation with local and global instances? [[BR]] |
| 315 | What additional features are under consideration? |
| 316 | Will the GIMI project want to use the UNIS service? [[BR]] |
| 317 | Will other parts of GENI want to use the UNIS service? [[BR]] |
| 318 | Do we need a breakout session for further discussion? when? [[BR]] |
| 319 | |