Changes between Version 1 and Version 2 of GENIMetaOps-annualreport-status

06/07/10 12:06:07 (9 years ago)



  • GENIMetaOps-annualreport-status

    v1 v2  
    6868=== A. Milestones achieved ===
     70''__Progress toward Dataset & Format Definition:__'' The first set of GMOC milestones
     71is on track for on-time completion at the 6-month mark of Spiral 1. This set of
     72milestones includes a complete initial GENI Operational Dataset and a complete
     73initial Operational Data Format. Our work to define the basic GENI operational
     74dataset is in progress, with three main elements. It includes discussion of a
     75strawman list of types of data to collect, a discussion of some basic questions about the data collecting and sharing capabilities of various GENI projects, and
     76research by GMOC into the existing data already included in various projects’
     77data collections.
     80''__Initial GMOC Data Translator Implementation:__'' While we do not expect in Spiral 1
     81to have a single unified implementation to translate operational data into our
     82internal format, we have worked with !PlanetLab to collect operational data in
     83their existing format (mainly from their Comon application) and translated it into
     84our defined internal data format. In addition, we have started collecting a small
     85set of data from the ProtoGENI project
     87''__Initial GMOC Data Exchanger Implementation:__'' As with the Data Translator, we
     88do not expect in Spiral 1 to have a unified exchange system used by all projects.
     89However, we’ve worked with !PlanetLab and ProtoGENI to collect data, using a
     90translation to convert it from the form the projects keep it in, into the Exchange
     91format defined in our Operational Data Exchange Format document, and then
     92using that to collect the data. In the future, the translator can be developed to
     93translate additional data from these and other projects, or projects can send data
     94directly in our defined Data exchange format.
     97''__Actively sharing operational data with PlanetLab:__'' Based on our conversation
     98with the !PlanetLab cluster participants, there was consensus that we should
     99begin by gathering existing data from !PlanetLab Central. GMOC visited
     100Princeton to discuss this in detail, using our operational dataset document as a
     101guide. The result is that we are now actively gathering data from !PlanetLab,
     102storing it in the format described by our Internal Operational Data Format
     103document. This data is still incomplete, in that we are unable to gather some
     104topological data, and in that it is only data covering the !PlanetLab project itself,
     105not data about other projects within the !PlanetLab cluster. But, it represents
     106both a good initial model for quickly beginning to collect data, and a good start
     107for gathering data from the !PlanetLab cluster as other projects in the cluster
     108begin to integrate more with the !PlanetLab control framework.
     109GMOC Operational Dataset Document: The Operational Dataset document has
     110been shared with all GENI control frameworks, and we’ve updated this
     111document based on input. This document is now mature enough that we’ve
     112begun to use it to work with projects to begin gathering operational data.
     114''__GMOC Operational Data Format Document:__'' Initial versions of two documents
     115have been created and shared with the GENI community, related to this. First,
     116we’ve created a document that describes the internal data format schema we’ve
     117developed for storing operational data we collect. Second, we’ve created a
     118document that describes the data exchange methodology we hope to employ as
     119GENI evolves to gather data from GENI projects, and to share data about GENI
     120with other federated networks such as internationals. These documents are
     121open to input from the community, but we believe these will require less
     122collaboration at this point than our operational dataset document. This is
     123because initially the formats used to exchange data with most projects will be
     124highly customized for each project.
     127''__Draft GENI Concept of Operations__'' The GENI Concept of Operations Document
     128proposes an operational model for GENI infrastructure for problem reception,
     129triage, handling, resolution, and reporting.
     131''__Demonstrated initial GMOC Framework implementation at GEC5:__'' GMOC
     132participated in the demo session at GENI GEC5, demoing a prototype version of
     133GMOC functionality with !PlanetLab and ProtoGENI data.
     135''__Initial implementation of Emergency Stop and notifications:__'' The GMOC
     136Emergency Stop document proposes a set of conditions and procedures for
     137early Emergency Stop activity in GENI.
     139''__Complete initial implementation of prototype GMOC:__'' The GMOC portal demoed
     140at GEC5 serves this initial prototype GMOC function. Continued enhancement
     141and refinement of this software will occur throughout the next year.
    71143=== B. Deliverables made ===
     145''__High-level, Strawman dataset:__'' GMOC has developed an initial high-level list of
     146types of data to begin collecting from other GENI projects. This list is by no
     147means finalized or complete; in fact, our intent with this list is to generate and
     148focus our discussion with the other GENI projects. As this high-level list is
     149improved through discussion, it will also begin to include a greater level of detail.
     150This list was presented during our GMOC presentation at GEC3.
     152''__Operational Dataset Question List:__'' Additionally, GMOC has formulated an initial
     153set of questions to discuss with other GENI projects, in order to form a fair
     154amount of consensus on what operational data is most sensible to collect.
     157''__Updated Operational Dataset Document:__'' Several new versions of the evolving
     158GMOC Operational Dataset Document were created, incorporating the input
     159from other GENI projects and clusters.
     161''__GMOC Internal Operational Data Format Description Document:__'' A new
     162document describing the format GMOC will use to store operational data was
     165''__GMOC Operational Data Exchange Draft Document:__'' A document describing our
     166approach to data exchange with other projects has been created.
     169''__GMOC Data Exchanger:__'' The code developed for Data Exchange is stored in an
     170internal GMOC version control system. This code is available on request, and
     171we are working on a self-service system for access to this code.
     173''__GMOC Data Translator:__'' The code developed for Data Translation is stored in an
     174internal GMOC version control system. This code is available on request, and
     175we are working on a self-service system for access to this code.
     177''__GMOC Data Repository:__'' The GMOC Data Repository system is kept on an
     178internal GMOC server. This data can be made available to GENI as required.
     181''__Continued improvement of GMOC software:__'' GMOC has worked through Q4 to
     182revise and enhance the GMOC software to increase speed and add to the
     183feature set. The portal used for the GMOC demo at GEC5 has also been moved
     184to production infrastructure.
     186''__GENI Emergency Stop Document:__'' The GMOC Emergency Stop document
     187proposes a set of conditions and procedures for early Emergency Stop activity
     188in GENI.
     190''__GENI Concept of Operations Document:__'' The GENI Concept of Operations
     191Document proposes an operational model for GENI infrastructure for problem
     192reception, triage, handling, resolution, and reporting.
    74194== II. Description of work performed during last quarter ==
    76196=== A. Activities and findings ===
     198''__Hiring:__'' The GENI Meta-Operations Center posted, advertised, interviewed, and
     199hired Camilo Viecco into the position of GMOC primary developer. Camilo
     200starts on January 8th, and will be tasked with continuing the research into
     201existing models for GMOC data formatting and protocols for sharing, as well as
     202technical discussions about the operational dataset with other GENI projects.
     203Camilo comes to GMOC from the Advanced Network Management Lab at
     204Indiana University, and has extensive expertise in both development and
     207GMOC also hired one of the two hourly undergraduate assistants to help with
     208the project. The second position is available, but has not yet been filled.
     209Equipment: The budgeted equipment need to test and develop GMOC software
     210has been specified and is in the procurement process.
     213Our activities during Q2 were spent working in depth with control framework
     214clusters and other stakeholders to do two things: gather input on our strawman
     215operational dataset document, and to understand in technical detail what each
     216cluster could provide and how.
     218This resulted in conversations with staff from every cluster, along with several
     219projects within clusters, and with Steve Schwab to discuss how security and
     220operational data sharing might begin to interface and interact.
     222Further details about findings and activities can be found in
     223Milestone/Deliverables description, and in the Collaborations sections of this
     227Our activities during Q3 were spent chiefly in 3 areas:
     229__Increased Collection from PlanetLab:__
     230Collection of operational data from !PlanetLab began on May 18, 2009. This data
     231includes data from all the !PlanetLab (proper) nodes and slices. Only a subset of the required data as specified by the data requirements is being collected at the
     234__Development/Discussion with ProtoGENI:__
     235Initial work of integration with ProtoGENI stated. We created a ProtoGENI Rspec
     236to GMOC data exchange translator. This allowed GMOC to store ProtoGENI’s
     237static topology. Initial work on sharing of operational data has been done but the
     238type and detail of this data is still pending.
     240__Development effort on Prototype GENI operational portal view:__
     242In anticipation of GEC5 demo, we developed an initial prototype of a GENI
     243Operational View system. We see 4 main sets of users for this system:
     245  1. Those interested in viewing GENI data as a whole, such as interested outside parties, GPO, etc.
     246  2. Those interested in viewing GENI data about a particular cluster
     247  3. Those interested in viewing GENI data about a particular aggregate or component
     248  4. The Research user who will be interested in viewing GENI data about their particular slice.
     250This early prototype focuses primarily on visualizing and graphing GENI clusters,
     251and graphing GENI slices. Because the bulk of our data comes from !PlanetLab,
     252this is the data we’ve focused on showing. As this prototype evolves, we will
     253focus on more data from other projects, topology, and especially on providing
     254the views into slices, including better visualization, for the researcher users of
     258During this quarter, we made several improvements to the GMOC prototype.
     259These improvements included:
     260  * Work to increase performance of the prototype application
     261  * Work to increase stability
     262  * Made modifications to allow compatibility with Internet Explorer 8 and Opera browsers
     263  * General code clean-up / standardization
     264During the quarter, we also made contacts with GpENI to host a GpENI node at
     265GMOC, attempted further data exchange with ProtoGENI, and assisted with
     266GENI installs in the Internet2 Network. These activities are detailed in later
     267sections of this document.
    79269=== B. Project participants ===
     270During this time, key participants in GMOC included:
     272Jon-Paul Herron, PI[[BR]]
     273Luke Fowler, Co-PI[[BR]]
     274Chris Small, Senior GMOC Engineer[[BR]]
     275Camilo Viecco, Senior GMOC Programmer[[BR]]
     276Dan Doyle, GMOC Undergraduate[[BR]]
     277Nick Baker, GMOC Undergraduate[[BR]]
     278Jeff Catania, GMOC Undergraduate[[BR]]
    82280=== C. Publications (individual and organizational) ===
     282Herron, JP. (2008, October 20-22). Developing the GENI Meta-Operations
     283Center. Presented at Chinese American Networking Symposium, Indiana
     284University, Indianapolis, IN.
     286This presentation focused on challenges of operations in a federated/distributed
     287world, and how operations for GENI relate to the future of operations for
     288production networks.
     290Herron, JP., Fowler, L., Small, C. (2008, October 28-30). Introduction to the
     291GENI Meta-Operations Center. Presented at GENI Engineering Conference 3,
     292Palo Alto, CA.
     294This presentation was a required introduction to the GMOC project
     295concentrating on the deliverables, approach, and expectations this will have on
     296other GENI projects.
     298Herron, JP., Fowler L. (2008, December 8-12). The GENI Meta-Operations
     299Center. Poster presented at IEEE eScience 2008 conference, Indianapolis, IN.
     301This was a presentation of a poster on GMOC. During this session, we fielded
     302questions from reporters and others interested in GMOC and in GENI.
     304__GMOC Website:__ A website for the GENI Meta-Operations Center was launched
     305at This is also available via the main GRNOC page at
     306 This site initially contains information about the
     307GMOC project’s goals, and approach, including the proposal, presentations,
     308and other introductory information. As the project accelerates, this will also
     309house information about which GENI projects are sharing data with GMOC, and what kinds of data each is sharing. It will also be the site containing the GENIwide operational system view data as it’s developed.
     312Herron, JP. (2009, March 24-25). The GENI Meta-Operations Center.
     313Presented at National Lambda Rail All-Hands Meeting, CalIT2, San Diego, CA.
     315This presentation focused on challenges of operations in a federated/distributed
     316world, and how operations for GENI relate to the future of operations for
     317production networks.
     319__GENI Documents:__
     321Herron, JP. The GMOC Operational Dataset.
     323This is a document produced to understand the initial set of data GMOC hopes
     324to gather from GENI projects.
     326Viecco, C. The GMOC Internal Data Format.
     328This document lays out the schema and format GMOC will use to store all
     329operational data format.
     331Viecco, C. GMOC Data Exchange.
     333This document describes a methodology moving forward to describe how
     334projects and GMOC might share data (other than utilization)
     337Herron, JP. (2009, June 10). The GENI Meta-Operations Center. Presented at
     338Terena Networking Conference 2009, University of Malaga, Malaga, Spain.
     340This presentation focused on challenges of operations in a federated/distributed
     341world, and how operations for GENI relate to the future of operations for
     342production networks. Specifically, this related to projects like Federica in
     345__GENI Documents:__
     347Viecco, Camilo H. Proposal (2009 June 15) : Use of URN's as GENI Identifiers,
     348Published at and
     349presented to the Cluster C for integration.
     351The GENI project current uses GGID for identifiers of GENI resources. This is
     352problematic for several reasons such as the bundling of identification and
     353authentication information and the inability to sub-allocate the UUID id space.
     354This problems are documented and a proposal to solve this problems by using
     355URNs and a grammar for these GENI URN’s is presented. This proposed format
     356is currently being adopted by the ProtoGENI cluster.
     359__GENI Documents:__
     361Herron, JP. Fowler, L. Viecco, C. Small, C. Emergency Shutdown, published at
     365The GMOC Emergency Stop document proposes a set of conditions and
     366procedures for early Emergency Stop activity in GENI.
     368Herron, JP. Fowler, L. Viecco, C. Small, C. GMOC: GENI Concept of Operations,
     369published at
     373The GENI Concept of Operations Document proposes an operational model for
     374GENI infrastructure for problem reception, triage, handling, resolution, and
    85377=== D. Outreach activities ===
     378__Undergraduate Development Assistance:__ Dan Doyle, an undergraduate for the
     379IU Computer Science department continued to assist with research activities
     380into GENI projects and existing data sharing options. A second undergraduate
     381position is available but has not yet been filled.
     383GMOC attended the IU Informatics Career Fair on Feb 17 to advertise available
     384positions for undergraduate students and discuss the GENI/GMOC projects with
     385IU undergraduates as part of our outreach efforts
    88387=== E. Collaborations ===
     389GMOC has began the process of collaboratively working to define the GENI
     390Common Operational Dataset with the other GENI projects that will be sharing
     391data with GMOC. Initial discussions are with the main control framework cluster
     392projects, as well as infrastructure projects that have existing relationships with
     393GRNOC, such as Internet2, NLR, and MAX GigaPoP. These initial discussions
     394should open the door to further dialogue on technical details and sharing of
     395existing data information with GMOC.
     397GMOC has formulated the initial questions to discuss with these projects, and
     398requested time to discuss with PIs or their assigned delegates on these topics.
     400''__ProtoGENI:__'' GMOC has had a discussion with ProtoGENI, and gathered a good
     401deal of information and data produced by ProtoGENI that will be relevant to
     402GMOC efforts. Capabilities are already in place in !EmuLab for Emergency Stop
     403and many of the topology and status data GMOC will need. More detailed
     404discussions and GMOC research into the data ProtoGENI provided us will reveal
     405how best to interact. But initially, it appears that we will be able to bring up
     406operational data sharing with ProtoGENI quickly.
     408''__Mid-Atlantic Crossroads/DRAGON:__'' GMOC has had discussions with MAX
     409GigaPoP, and formulated a plan for further collaboration. This collaboration will
     410involve a combination of direct polling of MAX components by GMOC and
     411gathering of data already collected from this equipment by the DRAGON project.
     412Further discussions will continue, with actually data gathering beginning
     413sometime in January.
     415''__NLR:__'' GMOC has also had discussions with NLR, and has come up with an initial
     416plan for data sharing on NLR components. Since these components are already
     417monitored and measured by the Global Research NOC at IU, NLR has agreed to
     418allow GMOC to make use of any data that is already publicly available for GENI
     419use. This should allow extensive data sharing on NLR components, but if
     420netflow (or similar user) data is needed, further discussion would be necessary.
     421Using the direct data collections should allow these components to be
     422monitored much more easily and quickly.
     425Similar to Q1, GMOC worked on gathering input and developing discussions
     426with many GENI stakeholders during this quarter.
     428__PlanetLab:__ After discussion about GMOC with !PlanetLab cluster participants,
     429GMOC staff visited Princeton to discuss overall operational data sharing
     430strategy and detailed capabilities for collaboration. This resulted in further
     431collaboration between GMOC and !PlanetLab staff to enable active data sharing.
     433__ProtoGENI:__ GMOC discussed the strawman GMOC Operational Dataset
     434document with the ProtoGENI cluster participants. There were some comments
     435from this discussion on the document, and further discussions between GMOC
     436and ProtoGENI developers on potential capabilities are underway. A visit with
     437ProtoGENI may be useful, as the !PlanetLab visit was.
     439__ORCA:__ GMOC spoke directly with Jeff Chase to cover the strawman GMOC
     440Operational Dataset document, and discuss future collaboration. We made
     441plans for immediate sharing from the ORCA monitoring software and topology
     442of some projects. Additionally, we talked about some future collaboration on
     443the issue of topology description, and exchange.
     445__ORBIT:__ ORBIT has provided GMOC some preliminary data output. Further
     446discussions will be needed to gather improved data.
     448__Mid-Atlantic Crossroads/DRAGON:__ GMOC is working with MAX to understand
     449how to gather operational data from projects. We are working with MAX to
     450understand what data we can/should gather via MAX’s integration with the
     451!PlanetLab control framework, and what data we can/should gather directly from
     454__NLR:__ GMOC has discussed operational dataset sharing with NLR, and now has
     455full capability to gather full initial operational dataset from the NLR GENI
     456elements, once it is in use.
     458__Internet2:__ GMOC has discussed operational dataset sharing with I2, using the
     459GRNOC’s existing access to Internet2 data. This data is all accessible for GENI
     460use, so we are prepared to gather full initial operational data from Internet2’s
     461GENI elements, once this is in use.
     463__PerfSONAR:__ GMOC has opened an ongoing dialogue with the PerfSONAR
     464project, which has already made significant progress in the areas of sharing data
     465among production networks. Specifically, PerfSONAR would provide a
     466potentially useful default method for projects to share operational data with GMOC, or for GMOC to share its data with other federated networks. It contains a topology description
     469Worked with SPP and ProtoGENI groups to deploy hardware to be co-located in
     470the Internet2 network.
     472Discussed collaboration with Franz Fidler of the Embedded Real-Time
     473measurement project on optical level measurement, including how substrate
     474measurements can be integrated into the GMOC Operational datasets. Showed
     475optical measurements tools developed and data collected by the GlobalNOC.
     477Discussed topology format options and identifier format with other GENI
     478aggregates. Discussed collaboration with Ilia Baldine for future data sharing with
     481Similar to Q1 & Q2 GMOC worked on gathering input and developing
     482discussions with many GENI stakeholders during this quarter.
     484__PlanetLab:__ GMOC continued to work with !PlanetLab to gather operational data
     485about the !Planetlab project itself, working to fix some minor bugs in the
     486!PlanetLab software, and working out a reasonable interval for operational data
     489__ProtoGENI:__ GMOC worked with ProtoGENI to collect Topology data from Emulab-Utah.
     490GMOC also worked to ProtoGENI for the use of a common URN based
     491identifiers for GENI resources. Started discussions for determining what
     492operational data can be shared and the periodicity for polling data.
     494__RSPEC Meeting:__ Discussed with the Rspec Meeting attendees on how topology data is
     495represented (NDL, NDL variations and GMOC exchange format) and continues
     496discussion on identifiers for GENI resources.
     498__Measurement Meeting:__ Discussed with Measurement Workshop attendees how
     499measurement plane data, when available, may be integrated into the GMOC
     500data sets.
     503__Continued discussion with projects about data sharing:__ GMOC continued
     504discussing data sharing activities with various GENI projects. More data sharing
     505activities are expected to occur based on milestones for GMOC and other GENI
     506projects during Y2.
     508__GpENI:__ Collaboration with GpENI to host GpENI node at GMOC for
     509investigation of integration of GpENI data into GMOC data sets. Hardware
     510expected to be deployed during Q1 of Y2.
     512__GENI infrastructure installs:__ GMOC assisted in the planning and installation of
     513the GENI infrastructure installations in the Internet2 network. GMOC is
     514investigating possible data sets that can be gleaned from this infrastructure for
     515inclusion in the GMOC data sets.
    91517=== F. Other Contributions ===
     520=== Planned Activities for Y2 ===
     521We plan to complete the following activities during Year 2. This list of activities
     522is copied from our Year 2 Statement of Work.
     523  1. Complete Spiral 2 Prototyping Plans. Document plans for gathering and sharing operational data with Spiral 2 control framework projects, and with several exemplar projects that cover different types of aggregate data. Initial plans will include at least 1) going over the Common Operational Dataset document, and developing a plan to gather as much of this data as each project can produce, in the format of their choosing; 2) going over the Operational Data Format and developing a plan to collect any data projects can produce in that format. In addition to the control framework projects, the exemplar projects will cover these technologies (candidate projects listed in parentheses. If candidate projects are unable to complete these tasks, alternate projects will be identified):
     524  * backbone and regional networks (I2, NLR, MAX) (December 30, 2009)
     525  * compute resources (CMU)
     526  * sensors (Kansei)
     527  * wireless networks (TBD after Sol2 funding finalized)
     528  * cloud computing (TBD after Sol2 funding finalized)
     529  * end-user opt-in (Million-node GENI) (December 31)
     530  2. Prototype manual emergency shutdown. Implement initial emergency shutdown process with control framework and exemplar projects. This process will be based on the emergency stop documentation from the GMOC’s spiral 1 work. Tasks for this milestone include:
     531  * Develop database of contact information for emergency shutdown with each project
     532  * Discuss expectations with each project for emergency shutdown process (response times, feedback loop, etc)
     533  * Conduct an initial drill to test the process (March 30)
     534  3. Prototype slice view of operational data sharing. Develop a per-slice operational view capability. View should include topology of a specified slice, including information about components being used, active operational status of slivers and components, and utilization data for slice traffic. This prototype will be enhanced to use data from real exemplar projects if appropriate data is available. (March 30)
     535  4. Complete revised Concept of Operations document. Revise the Concept of Operations document drafted in Spiral 1 based on lessons learned from exemplar interactions, emergency shutdown, and visualization prototypes. May also include any new drafts for Common Operational Data set document and Operational data format documents. Document will be reviewed and discussed at GEC8. (May 31)
     536  5. Complete Spiral 2 prototype data sharing system. Complete implementation and testing and put prototype data sharing in place for all projects identified in milestone 1 Prototyping Plan. Data collected will include either the full set of required data in the Common Operational Dataset document or a subset of critical data, depending on each project's capabilities, and the discussions in milestone 1. (September 30)
     537  6. Prototype multi-cluster GENI-wide visualization. Generate a prototype GENI map that visualizes multiple clusters at a time, in order to show integration within and between clusters, and the activity of slices across clusters. (September 30)
     541Converted submitted file by Julia Taylor ( Original file can be found [ here]