Changes between Version 26 and Version 27 of netKarma/GEC13_report


Ignore:
Timestamp:
03/22/12 00:51:35 (7 years ago)
Author:
scjensen@umail.iu.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • netKarma/GEC13_report

    v26 v27  
    1818
    1919__S4b.1 Demonstration of the provenance system with WiMAX DDoS Experiments__
    20 [[BR]]
    2120Using the MiMAX DDoS experiments at Clemson which were identified as a case for evaluating the provenance captured and visualized using NetKarma we showed how the provenance of packets successfully transferred and the inferred provenance of packets dropped can be used to provide visualizations of individual experiment runs; providing network researchers with a new approach to analyzing their experiment results. At GEC13 we presented both a poster and a live demo of the provenance captured from the DDoS experiments we reran based on the research done by GENI researchers at Clemson University.  An additional outcome of this evaluation of NetKarma is a new NetKarma adaptor that can be used to capture provenance of experiments run on the NS2 simulator used in the Clemson experiments (and can be applied to any NS2 experiments).  An enhanced NetKarma plug-in for Cytoscape that contains new visualization algorithms for visualizing the provenance of NS2 experiments was also released (version 1.2.1).  Both the adaptor and visualization plug-in, along with updated software documentation, are available on the NetKarma wiki.
    2221[[BR]]
     
    3231== Work Preformed this Quarter ==
    3332
    34 __Sb.4 Work with the GENI I&M community to define a standardized GENI event records__  We began to examine some of the issues involved with creation of a standardized GENI event record. While NetKarma captures provenance information including "events" of the infrastructure used for a GENI experiment, NetKarma doesn't produce events but may capture events related to an experiment as part of the provenance capture.  These events can then be used to create a provenance graph (e.g., identifying the process that generated a specific output from an experiment). We have worked with ExoGeni, GMOC, I&M projects and the Mesoscale monitoring efforts as possible sources of event information about the creation, resource allocation and possible outages on the experimental infrastucture.
     33__Sb.4 Work with the GENI I&M community to define a standardized GENI event records__
     34
     35We began to examine some of the issues involved with creation of a standardized GENI event record. While NetKarma captures provenance information including "events" of the infrastructure used for a GENI experiment, NetKarma doesn't produce events but may capture events related to an experiment as part of the provenance capture.  These events can then be used to create a provenance graph (e.g., identifying the process that generated a specific output from an experiment). We have worked with ExoGeni, GMOC, I&M projects and the Mesoscale monitoring efforts as possible sources of event information about the creation, resource allocation and possible outages on the experimental infrastucture.
    3536
    3637In discussions prior to GEC13, we talked with  Harry Mussman and Jeanne Ohren of BBN and Giridhar Manepalli of CNRI regarding the features that are essential in the event record.  It is anticipated that a large number of events would be generated and that the event record needs to be lightweight, sharing some similarities to call records in the telecom industry.  The event records will capture events in the slice including resource assignment/release, failures, and network events such as resources being up/down.  We identified events from Nagios based on thresholds as an example.  For some of the events (e.g., assignment of resources) the RSpec contains the information but is too heavyweight.