Changes between Version 1 and Version 2 of IMF-GEC11-QSR


Ignore:
Timestamp:
09/10/11 10:57:44 (8 years ago)
Author:
Rudra Dutta
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • IMF-GEC11-QSR

    v1 v2  
    5959[[Image(GEC11_setup_on_arch.png, 90%)]] [[BR]]
    6060
    61 The Java subscriber to the XMPP pub-sub service is not packaged in this release; the previously supplied code can, without change, be used (as part of a SILO service or standalone, as before), to extract the measurement data stored in the XMPP server.  The difference in this version is in how the IMF Pub-Sub Module acquires that data - it can now use a perfSONAR query to access the Measurement Handler (the IMF PSM can continue to reach the MH using an XML-RPC query as before as another alternative).
     61The IMF Pub-Sub Module was also updated to work with the new version of the IMFRealTime service.  The XML-RPC interface is still not re-enabled, we propose to do that at a future version (see post-GEC10 status report for discussion).
    6262
    63 In the MH, the pS capability is introduced by including a new pS service that we have called the "IMFRealTime" pS service.  (''Note:'' this name may be somewhat misleading and may change in subsequent releases; see discussion below.)  The IMFRealTime service is different from a normal Perfsonar service (MA or MP) in the sense that it implements a bit of both. It uses the mh Perl module and expands Perfsonar's configuration file to provide the MP service. However, instead of sending the results to an MA, the collected data are saved locally.
    64 
    65 The main reason behind this solution is that we want to avoid the delay introduced by adding an extra layer of database between the users and the MP. Consequently, the IMFRealTime service also needs to provide a user interface for real-time user queries in the absence of a standard Perfsonar MA.  In essence, the IMFRealTime service acts as a pS MP service (that uses previously developed IMF Measurement Handler capability to gather measurement data), but also looks like a pS MA service to external users who issue queries to obtain measurement data from the Measurement Archive.  In fact, internally, it uses shared memory as inter-process communication to access the most fresh data in response to user queries.  The shared memory acts as the rendezvous instead of the usual MA database.
    66 
    67 '''About "!RealTime" Nomenclature: ''' This behavior is obviously not actually "real-time" in terms of the time when measurement is made.  In contrast, the original XML-RPC approach is "real-time" in that measurements are "triggered", or undertaken (by the MH) in response to incoming user queries.  Rather, the behavior is "real-time" in only the sense that the IMFRealTime service looks for the most recent available data in response to user queries.  To avoid this potential confusion, we are considering re-naming the IMFRealTime pS service to something else in future releases, and use the term "real-time" exclusively to refer to cases where actual fresh measurements are undertaken once user queries are received.  In the future, we hope to investigate the possibility of triggered real-time measurements using the pS pathway as well; at this time, it appears this may not be a suitable match, since the pS architecture relies on static configuration file for measurements, and thus clearly separates the data query from collection.
     63...
    6864
    6965The developer notes, and other documentation included in the code below, provide more details regarding specifics.
     
    7773== Publications ==
    7874
    79 Integrated quarterly report and code documentation (this wiki)
     75Integrated post-GEC report and code documentation (this wiki)
    8076
    8177== Outreach ==
    8278
    83 Participants of the IMF team attended GECs as well as meetings of the Instrumentation and Measurement Working Group as possible.  We have previously collaborated with the GENI LEARN project team, and progressing toward deploying IMF in LEARN.
     79Participants of the IMF team attended GECs as well as meetings of the Instrumentation and Measurement Working Group as possible.  We have previously collaborated with the GENI LEARN project team, and progressing toward deploying IMF in LEARN.  We have started communicating with the TuNIE team from Tsinguah U, with a view to possibly collaborating on adapting IMF to provide measurement capabilities to TuNIE.
    8480
    8581== Collaborations ==
    8682
    8783The IMF team continued to collaborate with Deniz Gurkan of the GENI project LEARN.
    88 
    89 The IMF team collaborated with Martin Swany of the perfSONAR team to define and discuss the requirements of IMF as a pS usecase, resulting in the articulation of an alternate type of pS client and functionality, one that more nearly matches the needs of real-time oriented systems such as IMF.
    9084
    9185== Other contributions ==
     
    9791== Code Snapshot ==
    9892
    99 The GEC10 version of the IMF system can be built from source in the following tarballs:
     93The GEC11 version of the IMF system can be built from source in the following tarballs:
    10094
    101  * [attachment:mh.tar.gz Measurement Handler]
    102  * [attachment:pubsub_for_perfsonar.tar.gz PubSub for perfSONAR]
    103  * [attachment:perfsonar_imf_realtime.tar.gz perfSONAR IMF Realtime service]
     95 * [attachment:mh.tar.gz Measurement Handler]  <-- NEED THIS !!!
     96 * [attachment:pubsub_for_perfsonar.tar.gz PubSub for perfSONAR] <-- NEED THIS !!!
     97 * [attachment:perfsonar_imf_realtime.tar.gz perfSONAR IMF Realtime service]  <-- NEED THIS !!!
    10498
    10599== Documentation and Release Notes ==
    106100
    107 The diagram above (in "Activities/Findings" section) shows where these tarballs fit in.  The pubsub_for_perfsonar.tar.gz file (!PubSub for perfSONAR) replaces the imf.tar.gz file of previous releases: the internal file heirarchy is the same, but the top-level name is different: "imf_pfsr" instead of "imf"; this is a kluge that will be fixed in the next release.  As a consequence, this version of the code can '''''only''''' use pS query to reach the MH, the previous XML-RPC option is not available in this cut (the MH is still capable of it).
    108 
    109 The following developer's notes on the IMFRealTime pS service provide more detail which should be helpful in using this code.  This file is also included as "doc/README.imf" in the perfsonar_imf_realtime.tar.gz tarball.  In addition, the following diagram of the code organization for the "!PubSub for perfSONAR" module (pubsub_for_perfsonar.tar.gz) may be helpful.
    110 
    111  * [attachment:release_notes.txt Developer Release Notes]
    112 
    113 [[Image(PubSub_PerfSONAR_Source_Code_Folder_Structure.png, 50%)]] [[BR]][[BR]][[BR]]
     101See post-GEC10 status report.  The only changes to that code are the tarballs above, and the new pS client (command line and GUI) code.