32 | | This effort has both technical development and operational requirements. Technically, the GENI Meta Operations Center (GMOC) would require a well-defined protocol to help generalize the operational details of GENI prototypes and for the providers of prototypes to send those details to an operational data repository. These requirements suggest a modular approach, with a generalized protocol rather than a restricted set of hardware and software that GENI prototype participants would be required to run. In other words, it would be largely up to the GENI Spiral 1 project investigators to decide what data to share and how to collect this data from their prototype infrastructure. The GMOC would provide the standardized format for this data and the systems required to share, monitor, display, and act on this data. In addition, the GMOC could be used to help provide a repository for data collections passing into and out of GENI prototypes for the purpose of discovering and isolating prototypes that have caused problems. This might require additional instrumentation at the connection points and substrate elements between prototypes. |
| 32 | This effort has both technical development and operational requirements. Technically, the GENI Meta Operations Center (GMOC) would require a well-defined protocol to help generalize the operational details of GENI prototypes and for the providers of prototypes to send those details to an operational data repository. These requirements suggest a modular approach, with a generalized protocol rather than a restricted set of hardware and software that GENI prototype participants would be required to run. In other words, it would be largely up to the GENI Spiral project investigators to decide what data to share and how to collect this data from their prototype infrastructure. The GMOC would provide the standardized format for this data and the systems required to share, monitor, display, and act on this data. In addition, the GMOC could be used to help provide a repository for data collections passing into and out of GENI prototypes for the purpose of discovering and isolating prototypes that have caused problems. This might require additional instrumentation at the connection points and substrate elements between prototypes. |
39 | | [[MilestoneDate(GMOC:Define Common Operational Dataset)]][[BR]] |
40 | | [[MilestoneDate(GMOC:Define Specialized Operational Dataset)]] only one day late[[BR]] |
41 | | [[MilestoneDate(GMOC:Define GMOC Native Operational Data Format)]] only one day late[[BR]] |
42 | | [[MilestoneDate(GMOC:Integrate Security services in GMOC framework)]][[BR]] |
43 | | [[MilestoneDate(GMOC:Complete initial GMOC Operational Dataset Translater Implementation)]][[BR]] |
44 | | [[MilestoneDate(GMOC:Complete initial GMOC Data Exchanger Implementation)]][[BR]] |
45 | | [[MilestoneDate(GMOC:Complete initial implementation of Emergency Stop and notifications)]][[BR]] |
46 | | [[MilestoneDate(GMOC:Complete initial implementation of prototype GMOC)]][[BR]] |
47 | | [[MilestoneDate(GMOC:Demonstrate initial GMOC Framework Implementation at a GEC)]][[BR]] |
48 | | [[MilestoneDate(GMOC:Draft GENI Concept of Operations)]][[BR]] |
| 39 | [[MilestoneDate(GMOC: S2.a Spiral 2 prototyping plans)]][[BR]] |
| 40 | [[MilestoneDate(GMOC: S2.b Prototype manual emergency shutdown)]][[BR]] |
| 41 | [[MilestoneDate(GMOC: S2.c Prototype slice view of operational data sharing)]][[BR]] |
| 42 | [[MilestoneDate(GMOC: S2.d Revised Concept of Operations document)]][[BR]] |
| 43 | [[MilestoneDate(GMOC: S2.e Prototype S2 data sharing system)]][[BR]] |
| 44 | [[MilestoneDate(GMOC: S2.f Prototype multi-cluster GENI-wide visualization)]][[BR]] |