| 4 | | This is the OMIS working group wiki. Heidi Picher Dempsey [mailto:hdempsey@geni.net] is the working group chair. Mike Patton [mailto:MAP@GENI.net] is the System Engineer for OMIS. To find out what the OMIS working group does, browse these pages and read the [http://www.geni.net/wg/omis-wg.html working group charter]. If you have comments or suggestions on the charter, please send them to the [http://lists.geni.net/mailman/listinfo/omis-wg omis-wg mailing list]. If you have comments or suggestions about these pages, feel free to log in and improve their content. To view past archives of the mailing list, see the [http://lists.geni.net/pipermail/omis-wg/ mailman archive] or the [http://www.nabble.com/GENI-OMIS-WG-f26304.html nabble archive]. |
| | 4 | '''OMIS WG Scope:''' What are the requirements for operating GENI and managing its services? What are GENI's security requirements, both from a researcher's viewpoint and from that of its operators? |
| | 5 | |
| | 6 | This is the OMIS working group wiki. Heidi Picher Dempsey [mailto:hdempsey@geni.net] is the working group chair. Mike Patton [mailto:MAP@GENI.net] is the System Engineer for OMIS. To find out what the OMIS working group does, browse these pages. If you have comments or suggestions on the charter, please send them to the [http://lists.geni.net/mailman/listinfo/omis-wg omis-wg mailing list]. If you have comments or suggestions about these pages, feel free to log in and improve their content. To view past archives of the mailing list, see the [http://lists.geni.net/pipermail/omis-wg/ mailman archive] or the [http://www.nabble.com/GENI-OMIS-WG-f26304.html nabble archive]. |
| | 37 | == OMIS Future Work == |
| | 38 | |
| | 39 | '''Technology Survey:''' A document that reports on available commercial and open-source tools and systems that are appropriate for operations in a large-scale research environment, explaining how such tools might be adapted for GENI requirements. The report will identify areas where GENI system requirements and new technology may drive new development. |
| | 40 | |
| | 41 | '''Security Policy Recommendations:''' A document that identifies GENI assets, data, and processes for which there are security requirements, provides a framework for comparing the degree of protection required for various GENI elements, and recommends suitable procedures, tools, and technologies for adequately protecting those elements. The document will pay special attention to security needs related to federation and the requirements for interconnections between GENI elements and those of other organizations. |
| | 42 | |
| | 43 | '''Long-Term Operations Framework:''' A document that describes the expected long-term operations functions for the GENI suite of infrastructures. This document will follow the initial Operations Framework document. It will address fully developed GENI system requirements that evolve from the GENI Research Plan. |
| | 44 | |
| | 45 | '''Concept of Operations Documents:''' Documents that describe the concept of operations, including worked-through examples, for operations, management, integration and security processes in GENI. The working group will assess the areas in which Concept of Operations documents are needed, based on the GENI system requirements derived from the Research Plan. The working group may release Concept of Operations documents in phases that coordinate with the spiral development process. The working group will produce separate Concept of Operations documents for at least the following areas: |
| | 46 | * experiment support, monitoring, and data storage |
| | 47 | * security monitoring and incident response (including incidents unrelated to security) |
| | 48 | * federation management and monitoring |
| | 49 | * hardware release, maintenance and integration |
| | 50 | * software release, maintenance and integration |
| | 51 | * operations metric collection and analysis |
| | 52 | |
| | 53 | '''Management Interface Requirements:''' Document requirements for desired interfaces between GENI operations, aggregate/component management and security functions. Initial versions will describe high-level interfaces (for example between a GENI node and the operations function that provides current status on that node). Later versions will define interfaces in more detail as appropriate (for example defining a GENI management API for a particular type of component interface). |
| | 54 | |
| | 55 | |
