Changes between Initial Version and Version 1 of netKarma-1Q10-status

05/25/10 16:20:56 (9 years ago)



  • netKarma-1Q10-status

    v1 v1  
     3= NetKarma Project Status Report =
     5Period: 1Q10
     6== I. Major accomplishments ==
     8=== A. Milestones achieved ===
     9''__Demonstration of NetKarma:__'' Demonstrated a working version of !NetKarma ingesting
     10provenance information from GUSH. We visualized the provenance graph that is
     11generated when an experimenter uses Gush to manipulate their experiment. Delivered
     12at GEC-7
     14!NetKarma Poster used at the demo session can be found here:
     17=== B. Deliverables made ===
     20== II. Description of work performed during last quarter ==
     22=== A. Activities and findings ===
     23''__GUSH provenance capture code released:__'' We have released version 1.0 of the
     24“gush2netkarma” software. This code contains tools to parse log files generated by
     25Gush. While this software allows injestion of Gush logfiles into the Karma provenance
     26framework, it also provides a generalized rules framework that can be used to generate
     27provenance information in other GENI projects. We hope to use this framework in
     28capturing the status and workflow of GENI experiments. The framework developed
     29should allow us to capture artifacts and instrument additional GENI components easily.
     31The gush2netkarma-1.0 code is linked from the !NetKarma GENI WIKI page and
     32available at the following location:[[BR]]
     35''__Karma 3.0 Released:__'' The new release of the core Karma system contains
     36instrumentation using Axis2 handlers, more extensive test clients, and better
     37documentation. Karma v3.0 supports provenance activities published from services,
     38workflows and nested workflows. The provenance data is efficiently stored in a
     39relational database, and supports Open Provenance Model (OPM) v1.0 standard for
     40interfacing with the tool.
     41=== B. Project participants ===
     42During this time, key participants in the !NetKarma project included:
     43  * Beth Plale, PI
     44  * Chris Small, Co-PI
     45  * Girish Subramanian, PhD student
     46  * Yiming Sun, PhD student
     47  * Devarshi Goshal, PhD student
     48  * Sharanya Chinnusamy, MS student
     49  * David Ripley, technical staff
     50  * Robert Ping, Project and Information Management
     51=== C. Publications (individual and organizational) ===
     52!NetKarma Status Update during GEC7 Planetlab cluster meeting:
     56!NetKarma Poster used at the GEC7 demo session:
     60gush2netkarma-1.0 release:
     63=== D. Outreach activities ===
     65=== E. Collaborations ===
     66We have worked extensively with Jeannie Albrecht, lead of the Gush team, to ingest
     67provenance relevant information from log files produced by Gush into the Netkarma
     68system. Professor Albrecht has been extremely cooperative in providing assistance in
     69understanding the various data artifacts produced by Gush and in deploying a
     70demonstration instance for the development of the “gush2netkarma” software.
     72We continue to work with the Gush team on refining the provenance data collection
     73process. This includes adding hooks to the Gush code to facilitate the collection of
     74artifacts from the Gush processes.
     76We have had discussions with John Hartman and Scott Baker of the Raven project to
     77discuss the workings and workflow of the Raven provisioning service. We are studying
     78the logs and information presented through the Owl monitoring service for collection
     79into !NetKarma.
     81We have started initial discussion with the GMOC. We are studying the extent to which
     82operational data collected by the GMOC, especially control plane related data, could be
     83collected from the GMOC repository instead of the original source. The GMOC
     84repository would provide a unified, normalized schema to query against compared to
     85widely differing data and formats used by control plane and other data sources.
     86Collecting data already obtained from various sources and stored in the GMOC
     87database schema may speed and simplify the work need for data collection.
     89We had a preliminary discussion of how !penFlow state such as flow tables and
     90controller policy rules can be used. We focused on collection from the Indiana
     91University !OpenFlow campus trial infrastructure as an initial test but techniques should
     92be applicable to all !OpenFlow deployments.
     94=== F. Other Contributions ===
     96We will work to establish connections with relevant projects in the Control Plane and
     97Measurement Plane areas. We plan to make decisions of what Control plane
     98information we will integrate into the !Netkarma data collection during Q3.
     100We will continue to develop software to allow the integration of Raven metadata into
     101!Netkarma. This may include data such the locations, success of the distribution and
     102time of deployment of software package to all nodes in an experiment. References to
     103the software itself on the Raven repository would also be incorporated in to the
     104!Netkarma description of an experiment. The software reference could be very useful if
     105future creation of the ability to recreate an experiment from information captured in the
     106!Netkarma provenance trace.