Changes between Initial Version and Version 1 of Raven2Q10QSR


Ignore:
Timestamp:
07/13/10 09:36:48 (14 years ago)
Author:
Vic Thomas
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Raven2Q10QSR

    v1 v1  
     1= Raven Quarterly Status Report for Q2 2010 =
     2
     3Reporting period: Apr 1 - Jun 30 2010
     4
     5PI: John H. Hartman (University of Arizona)
     6
     7== Major accomplishments ==
     8
     9  * Publish/Subscribe system
     10  * Elimination of PyXML dependencies
     11  * Rewrite Keyconvert tool from C to Python
     12  * !ServiceMonitor tool
     13  * Seattle support for Owl monitoring service
     14  * Continuing support for SFA credentials
     15  * Major Owl refactoring and enhancements
     16  * Enhanced Owl Mapviewer support
     17  * VINI support
     18
     19== Description of work performed during last quarter ==
     20
     21=== Publish/Subscribe system ===
     22
     23We created a publish/subscribe system that notifies slivers quickly and efficiently of events. The publish/subscribe system is used in Tempest to notify slivers of configuration changes that may require installing, updating, or removing packages.
     24
     25=== Elimination of PyXML dependencies ===
     26
     27We eliminated the use of PyXML by Raven, switching to an XML parser that is built into the Python distribution. This enhances Raven portability, opening up non-PlanetLab platforms where PyXML may not have been available.
     28
     29=== Rewrite Keyconvert tool from C to Python ===
     30
     31We developed our own ASN.1 parsing routines in native python and
     32ported a C-based tool for converting SSH keys to Python. This
     33eliminates dependencies on precompiled binaries, allowing Stork to run on more platforms and more diverse hardware.
     34
     35=== !ServiceMonitor tool ===
     36
     37We created a tool for monitoring services that run in a sliver and automatically restarting them. This tool is typically used by long-running experiments where fault tolerance of failed processes over a long period of time must be guaranteed. The !ServiceMonitor tool replaces several one-off special-purpose tools for monitoring different critical services.
     38
     39=== Owl refactoring and enhancements ===
     40
     41We refactored Owl not only to improve the code base but also to extend its capabilities. The Owl client now uses a library to communicate with the Owl server. This library can be used by services that want to use Owl directly without going through the client. The server now supports integer data, statistics such as the mean, column hiding, a legend containing field descriptions, increaing and decreasing sort on all columns, and a per-row view that displays only the data for a row (typically a sliver).
     42
     43=== Seattle support for Owl ===
     44
     45We ported the Owl client to the Seattle platform and performed a feasibility study of supporting other Raven tools on that platform. Owl allows Seattle experiments to report results back to a centralized database where they can be analyzed.
     46
     47=== Continuing support for SFA credentials ===
     48
     49We continued to update Raven tools to use new versions of SFA
     50credentials. More work needs to be done as the Credential continues to evolve toward merged support of !PlanetLab and ProtGENI.
     51
     52=== Enhanced Owl Mapviewer support ===
     53
     54Added new features to the Owl map
     55viewer application, including
     56a control panel for selecting display options and the ability
     57to view links between nodes. Links allow services that implement virtualized network topologies, such as VINI, to be monitored by Owl.
     58
     59=== Support for VINI ===
     60
     61We added support for the Raven tools to automatically detect when they are installed on VINI nodes, and to install custom packages for the VINI platform. We created a monitoring application for Owl that allows latencies on VINI links to be monitored and reported to the Owl database. More work needs to be done with respect to VINI key distribution and initscript support to make it easier to provision VINI experiments with Raven.
     62
     63
     64== Project participants ==
     65
     66  * John H. Hartman (University of Arizona)
     67  * Scott Baker (SB Software)
     68  * Jude Nelson (University of Arizona)
     69
     70== Publications (individual and organizational) ==
     71
     72  *  None.
     73
     74== Outreach activities ==
     75
     76  * None.
     77
     78== Collaborations ==
     79
     80We worked closely with the following Cluster B members:
     81  * !PlanetLab
     82  * GUSH
     83  * GpENI
     84
     85We are also working with the ProtoGENI, Seattle, and VINI projects to port Raven to their platforms.
     86 
     87== Other Contributions ==
     88
     89  * None.