• End-user Opt-in

• Experiment Workflow and Services

• Faciliy Control Framework

• Operations, Management, Integration, & Security

• Substrate

GENI Operations, Management, Integration, and Security Working Group

<omis-wg>

---

Chair:

Heidi Picher Dempsey <hdempsey@geni.net>

SE:

Michael A. Patton <MAP@MAP-NE.com.net>

Discussion Mail List Information:

subscribe
mailman archive
nabble archive

Wiki: http://groups.geni.net/geni/wiki/GeniOmis

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?

Initial Deliverables:

• Operations Framework: A document (20pp) that describes the high-level functions required for running the near-term GENI facility 24x7x365 with appropriate security and management safeguards for a research infrastructure. This document will pay particular attention to the minimal set of operations, management, and security functions needed for the narrow waist.

Later Deliverables:

• 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.
• 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.
• Long-Term Operations Framework: A document that describes the expected operations functions of the GENI facility that will come into being during and after the MREFC construction phase. This document will follow the initial Operations Framework document. It will be based on the fully developed GENI system requirements that evolve from the GENI Research and Education Plan.
• 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 and Education 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:
  • experiment support, monitoring, and data storage
  • security monitoring and incident response (including incidents unrelated to security)
  • federation management and monitoring
  • hardware release, maintenance and integration
  • software release, maintenance and integration
  • operations metric collection and analysis
• Facility Management Interface Requirements: Document requirments for desired interfaces between the GENI operations, facility management, and security infrastructures and the rest of the GENI elements. Initial versions will describe functional interfaces (for example between a GENI node and the operations function that provides current status on that node). Later versions will define the interfaces in more detail, possibly to the level of a GENI API for a particular interface.