Version 1 (modified by, 11 years ago) (diff)


GMOC Project Status Report

Period: Annual Report


  • Operating within Budget
  • Completed all Year 1 Milestones
  • Worked collecting data from initial set of GENI projects
  • Functional prototype GMOC environment implemented and available
  • Published several GENI documents, including Concept of Operations, Emergency Stop, GMOC data exchange formats

The GMOC project had a successful first year, making good progress on the early definition of operations for GENI, and helping to build the initial systems and processes for federated operational data sharing. These are crucial early building blocks for a facility that must be federated and flexible enough to attract many types of infrastructures, but must also behave coherently and effectively as an integrated facility. These can be used as the bootstraps for the increased services, prototypes, and further definition we expect for Spiral 2.

Much of our work for Spiral 1 was spent working to build a framework for data sharing between GMOC and GENI infrastructure providers. This was handled initially by approaching the control framework projects heading each control framework cluster to try to build a system to share operational data about all the projects within each cluster. Initial discussion was focused on feedback for a draft Common Operational Dataset document describing the most important types of data projects should share with GMOC. A Common Operational Data Format document was also created to document how best to format the data we receive, although this provoked less feedback and interest from the projects.

The results from this effort were fruitful, but inconsistent. At this early stage, the capabilities of the control frameworks and the projects themselves are highly variable. Some projects were able to immediately provide us some data, while others had little or no way of sharing this data at this point. It also became clear that the control framework projects might not necessarily be the right aggregator of operational data for projects within each cluster. Rather, the right architecture might require direct data sharing with individual infrastructure provider projects.

By the end of Spiral 1, GMOC was collecting significant operational data about the PlanetLab infrastructure, though not the other projects within the PlanetLab cluster. We were also gathering some topological data from ProtoGENI, with an expectation of gathering more data in Spiral 2. For ORCA, they hoped to have some data in Spiral 2 as well.

In addition to the project of coordinating operational data sharing and formatting, GMOC developed a prototype GENI-wide view. This view, available from the GMOC website, serves as an early prototype into how to visualize GENI as a facility. There will continue to be significant work to develop this into a suite of maps and other tools to provide health information to all GENI stakeholders. This prototype will change significantly as we begin to receive additional types of data. We’ve found that even a small amount of data becomes difficult to visualize in a constructive way, and this will become exponentially more difficult as more projects begin to share more information.

Lastly, GMOC has produced 2 documents to help define operations for GENI overall. First, we’ve produced a document describing a strategy for Emergency Stop. This will be the document used to drive our Spiral 2 developments in supporting Emergency Stop functionality. This document is now in draft format and will be altered after soliciting feedback from other GENI project. Second, we’ve produced a draft GENI Concept of Operations document to help begin a strategy for Operations of GENI. This document will also likely be altered based on feedback, and will be used to set the direction of GENI operations as a whole.

I. Major accomplishments

A. Milestones achieved

B. Deliverables made

II. Description of work performed during last quarter

A. Activities and findings

B. Project participants

C. Publications (individual and organizational)

D. Outreach activities

E. Collaborations

F. Other Contributions