Changes between Initial Version and Version 1 of GENIMetaOps-Q3-status


Ignore:
Timestamp:
06/07/10 11:25:04 (14 years ago)
Author:
jtaylor@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GENIMetaOps-Q3-status

    v1 v1  
     1[[PageOutline]]
     2
     3= GMOC Project Status Report =
     4
     5Period: Q3
     6== Summary ==
     7  * Operating within Budget
     8  * Development underway for GMOC operations portal prototype
     9  * Continued work collecting data from !PlanetLab
     10  * Initial Data Exchange with ProtoGENI
     11  * Roadmap discussion for data collection with ORCA
     12
     13== I. Major accomplishments ==
     14
     15=== A. Milestones achieved ===
     16''__Initial GMOC Data Translator Implementation:__'' While we do not expect in Spiral 1
     17to have a single unified implementation to translate operational data into our
     18internal format, we have worked with !PlanetLab to collect operational data in
     19their existing format (mainly from their Comon application) and translated it into
     20our defined internal data format. In addition, we have started collecting a small
     21set of data from the ProtoGENI project
     22
     23''__Initial GMOC Data Exchanger Implementation:__'' As with the Data Translator, we
     24do not expect in Spiral 1 to have a unified exchange system used by all projects.
     25However, we’ve worked with !PlanetLab and ProtoGENI to collect data, using a
     26translation to convert it from the form the projects keep it in, into the Exchange
     27format defined in our Operational Data Exchange Format document, and then
     28using that to collect the data. In the future, the translator can be developed to translate additional data from these and other projects, or projects can send data
     29directly in our defined Data exchange format.
     30
     31=== B. Deliverables made ===
     32''__GMOC Data Exchanger:__'' The code developed for Data Exchange is stored in an
     33internal GMOC version control system. This code is available on request, and
     34we are working on a self-service system for access to this code.
     35
     36''__GMOC Data Translator:__'' The code developed for Data Translation is stored in an
     37internal GMOC version control system. This code is available on request, and
     38we are working on a self-service system for access to this code.
     39
     40''__GMOC Data Repository:__'' The GMOC Data Repository system is kept on an
     41internal GMOC server. This data can be made available to GENI as required.
     42
     43== II. Description of work performed during last quarter ==
     44
     45=== A. Activities and findings ===
     46Our activities during Q3 were spent chiefly in 3 areas:
     47
     48__Increased Collection from !PlanetLab:__ <is this true? > Parially, we started
     49collection of operational data after GEC4.>
     50Collection of operational data from !PlanetLab began on May 18, 2009. This data
     51includes data from all the !PlanetLab (proper) nodes and slices. Only a subset of
     52the required data as specified by the data requirements is being collected at the
     53moment.
     54
     55__Development/Discussion with ProtoGENI:__
     56Initial work of integration with ProtoGENI stated. We created a ProtoGENI Rspec
     57to GMOC data exchange translator. This allowed GMOC to store ProtoGENI’s
     58static topology. Initial work on sharing of operational data has been done but the
     59type and detail of this data is still pending.
     60
     61__Development effort on Prototype GENI operational portal view:__
     62
     63In anticipation of GEC5 demo, we developed an initial prototype of a GENI
     64Operational View system. We see 4 main sets of users for this system:
     65  1. Those interested in viewing GENI data as a whole, such as interested outside parties, GPO, etc.
     66  2. Those interested in viewing GENI data about a particular cluster
     67  3. Those interested in viewing GENI data about a particular aggregate or component
     68  4. The Research user who will be interested in viewing GENI data about their particular slice.
     69
     70This early prototype focuses primarily on visualizing and graphing GENI clusters,
     71and graphing GENI slices. Because the bulk of our data comes from !PlanetLab,
     72this is the data we’ve focused on showing. As this prototype evolves, we will
     73focus on more data from other projects, topology, and especially on providing
     74the views into slices, including better visualization, for the researcher users of
     75GENI.
     76=== B. Project participants ===
     77During this time, key participants in GMOC included:
     78
     79Jon-Paul Herron, PI[[BR]]
     80Luke Fowler, Co-PI[[BR]]
     81Chris Small, Senior GMOC Engineer[[BR]]
     82Camilo Viecco[[BR]]
     83
     84=== C. Publications (individual and organizational) ===
     85Herron, JP. (2009, June 10). The GENI Meta-Operations Center. Presented at
     86Terena Networking Conference 2009, University of Malaga, Malaga, Spain.
     87
     88This presentation focused on challenges of operations in a federated/distributed
     89world, and how operations for GENI relate to the future of operations for
     90production networks. Specifically, this related to projects like Federica in
     91Europe.
     92
     93Small, C. (2009, June 26) Experiences with Measurement Data Collection in R&E
     94Networks Presented at GENI Measurement Workshop, University of Wisconsin,
     95Madison WI
     96
     97Presentation on experience learned in collecting measurement data and
     98deploying experiments on Research and Educational networks. Discussed what
     99data is collected currently by the GlobalNOC and concepts that may be used to
     100facilitate collecting measurement data for GENI
     101
     102__GENI Documents:__
     103
     104Viecco, Camilo H. Proposal (2009 June 15) : Use of URN's as GENI Identifiers,
     105Published at http://gmoc.grnoc.iu.edu/gmoc/file-bin/urn-proposal3.pdf and
     106presented to the Cluster C for integration.
     107
     108The GENI project current uses GGID for identifiers of GENI resources. This is
     109problematic for several reasons such as the bundling of identification and
     110authentication information and the inability to sub-allocate the UUID id space.
     111This problems are documented and a proposal to solve this problems by using
     112URNs and a grammar for these GENI URN’s is presented. This proposed format
     113is currently being adopted by the ProtoGENI cluster.
     114
     115=== D. Outreach activities ===
     116__Undergraduate Development Assistance:__ Dan Doyle, an undergraduate for the
     117IU Computer Science department continued to assist with research activities
     118into GENI projects and existing data sharing options. A second undergraduate
     119position is available but has not yet been filled.
     120
     121GMOC attended the IU Informatics Career Fair on Feb 17 to advertise available
     122positions for undergraduate students and discuss the GENI/GMOC projects with
     123IU undergraduates as part of our outreach efforts
     124
     125=== E. Collaborations ===
     126Worked with SPP and ProtoGENI groups to deploy hardware to be co-located in
     127the Internet2 network.
     128
     129Discussed collaboration with Franz Fidler of the Embedded Real-Time
     130measurement project on optical level measurement, including how substrate
     131measurements can be integrated into the GMOC Operational datasets. Showed
     132optical measurements tools developed and data collected by the GlobalNOC.
     133
     134Discussed topology format options and identifier format with other GENI
     135aggregates. Discussed collaboration with Ilia Baldine for future data sharing with
     136ORCA.
     137
     138Similar to Q1 & Q2 GMOC worked on gathering input and developing
     139discussions with many GENI stakeholders during this quarter.
     140
     141__PlanetLab:__ GMOC continued to work with !PlanetLab to gather operational data
     142about the !Planetlab project itself, working to fix some minor bugs in the
     143!PlanetLab software, and working out a reasonable interval for operational data
     144polling
     145
     146__ProtoGENI:__
     147GMOC worked with ProtoGENI to collect Topology data from Emulab-Utah.
     148GMOC also worked to ProtoGENI for the use of a common URN based
     149identifiers for GENI resources. Started discussions for determining what
     150operational data can be shared and the periodicity for polling data.
     151
     152__RSPEC Meeting:__
     153Discussed with the Rspec Meeting attendees on how topology data is
     154represented (NDL, NDL variations and GMOC exchange format) and continues
     155discussion on identifiers for GENI resources.
     156
     157__Measurement Meeting:__ Discussed with Measurement Workshop attendees how
     158measurement plane data, when available, may be integrated into the GMOC
     159data sets.
     160=== F. Other Contributions ===
     161None
     162
     163=== Planned Activities for Q4 ===
     164__Further Development of GENI Operational View:__ We will take the GENI
     165Operational View system demonstrated at GEC5 and make it robust and
     166accessible to the GENI community via the GENI and GMOC websites. This
     167system is expected to change continually in this early phase, so the GENI
     168community can track the progress and provide feedback on an ongoing basis.
     169
     170__Draft Emergency Stop Strategy Proposal:__ GMOC will produce a draft document
     171on how the important function of Emergency Stop might be accomplished,
     172especially in the near term. More detail will be given to an initial implementation,
     173with more general ideas for future implementations.
     174
     175__Draft Proposal for GENI Concept of Operations:__ in Year 1 Q4, GMOC will
     176produce a proposed strategy for ongoing GENI operations. This is expected to
     177cover the general guiding principles of how operations might work for a GENI
     178facility, and what we see as the most important examples of operational
     179functions, as well as a strategy for how such an operational model might be
     180phased.
     181
     182__Strategy for Integration of GENI Security and GENI Meta-Operations:__ Early in Q4,
     183we expect to publish a document laying out the strategy we’ve worked with the GENI Security project to develop. This document will cover the GMOC’s approach to security and privacy issues, especially in the early phase of operational data sharing
     184
     185__Continued Ramp-up of Operational Data Sharing from GENI projects:__ We
     186anticipate further efforts from both the ORCA and ProtoGENI control
     187frameworks to provide operational data to us in Q4. Additionally, we will be
     188opening dialogues with several non-control-framework projects to attempt to
     189gather more direct information. We will be targeting projects that exemplify
     190types of infrastructure, so that we can make sure we fulfill the needs of different
     191types of projects, such as sensor projects, network infrastructure projects,
     192programmable node projects, etc.
     193
     194
     195[[BR]]
     196Converted submitted file by Julia Taylor (jtaylor@bbn.com). Original file can be found [http://groups.geni.net/geni/attachment/wiki/GENIMetaOps/GMOC%20QR%20-Q3.pdf?format=raw here]