| 1 | [[PageOutline]] |
| 2 | |
| 3 | = GMOC Project Status Report = |
| 4 | |
| 5 | Period: Annual Report |
| 6 | |
| 7 | == Summary == |
| 8 | * Operating within Budget |
| 9 | * Completed all Year 1 Milestones |
| 10 | * Worked collecting data from initial set of GENI projects |
| 11 | * Functional prototype GMOC environment implemented and available |
| 12 | * Published several GENI documents, including Concept of Operations, Emergency Stop, GMOC data exchange formats |
| 13 | |
| 14 | The GMOC project had a successful first year, making good progress on the |
| 15 | early definition of operations for GENI, and helping to build the initial systems |
| 16 | and processes for federated operational data sharing. These are crucial early |
| 17 | building blocks for a facility that must be federated and flexible enough to |
| 18 | attract many types of infrastructures, but must also behave coherently and |
| 19 | effectively as an integrated facility. These can be used as the bootstraps for the |
| 20 | increased services, prototypes, and further definition we expect for Spiral 2. |
| 21 | |
| 22 | Much of our work for Spiral 1 was spent working to build a framework for data |
| 23 | sharing between GMOC and GENI infrastructure providers. This was handled |
| 24 | initially by approaching the control framework projects heading each control |
| 25 | framework cluster to try to build a system to share operational data about all the |
| 26 | projects within each cluster. Initial discussion was focused on feedback for a |
| 27 | draft Common Operational Dataset document describing the most important |
| 28 | types of data projects should share with GMOC. A Common Operational Data |
| 29 | Format document was also created to document how best to format the data |
| 30 | we receive, although this provoked less feedback and interest from the projects. |
| 31 | |
| 32 | The results from this effort were fruitful, but inconsistent. At this early stage, the |
| 33 | capabilities of the control frameworks and the projects themselves are highly |
| 34 | variable. Some projects were able to immediately provide us some data, while |
| 35 | others had little or no way of sharing this data at this point. It also became clear |
| 36 | that the control framework projects might not necessarily be the right |
| 37 | aggregator of operational data for projects within each cluster. Rather, the right |
| 38 | architecture might require direct data sharing with individual infrastructure |
| 39 | provider projects. |
| 40 | |
| 41 | By the end of Spiral 1, GMOC was collecting significant operational data about |
| 42 | the !PlanetLab infrastructure, though not the other projects within the !PlanetLab |
| 43 | cluster. We were also gathering some topological data from ProtoGENI, with an |
| 44 | expectation of gathering more data in Spiral 2. For ORCA, they hoped to have |
| 45 | some data in Spiral 2 as well. |
| 46 | |
| 47 | In addition to the project of coordinating operational data sharing and formatting, |
| 48 | GMOC developed a prototype GENI-wide view. This view, available from the |
| 49 | GMOC website, serves as an early prototype into how to visualize GENI as a |
| 50 | facility. There will continue to be significant work to develop this into a suite of |
| 51 | maps and other tools to provide health information to all GENI stakeholders. |
| 52 | This prototype will change significantly as we begin to receive additional types |
| 53 | of data. We’ve found that even a small amount of data becomes difficult to |
| 54 | visualize in a constructive way, and this will become exponentially more difficult |
| 55 | as more projects begin to share more information. |
| 56 | |
| 57 | Lastly, GMOC has produced 2 documents to help define operations for GENI |
| 58 | overall. First, we’ve produced a document describing a strategy for Emergency |
| 59 | Stop. This will be the document used to drive our Spiral 2 developments in |
| 60 | supporting Emergency Stop functionality. This document is now in draft format |
| 61 | and will be altered after soliciting feedback from other GENI project. Second, |
| 62 | we’ve produced a draft GENI Concept of Operations document to help begin a |
| 63 | strategy for Operations of GENI. This document will also likely be altered based |
| 64 | on feedback, and will be used to set the direction of GENI operations as a whole. |
| 65 | |
| 66 | == I. Major accomplishments == |
| 67 | |
| 68 | === A. Milestones achieved === |
| 69 | |
| 70 | |
| 71 | === B. Deliverables made === |
| 72 | |
| 73 | |
| 74 | == II. Description of work performed during last quarter == |
| 75 | |
| 76 | === A. Activities and findings === |
| 77 | |
| 78 | |
| 79 | === B. Project participants === |
| 80 | |
| 81 | |
| 82 | === C. Publications (individual and organizational) === |
| 83 | |
| 84 | |
| 85 | === D. Outreach activities === |
| 86 | |
| 87 | |
| 88 | === E. Collaborations === |
| 89 | |
| 90 | |
| 91 | === F. Other Contributions === |