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


Ignore:
Timestamp:
09/10/11 12:34:21 (10 years ago)
Author:
Rudra Dutta
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • IMF-GEC11-QSR

    v2 v3  
    6161The 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 ...
     63Some of our thinking during this cycle served to clarify "pS-compatibility" and "OMF compatibility" in the context of the IMF project.  Currently our operating definitions are as follows, followed by more detailed discussion.
    6464
    65 The developer notes, and other documentation included in the code below, provide more details regarding specifics.
     65 * "pS-compatibility" means "any measurement resource which is IMF-readable (i.e. for which an IMF Measurement Handler module has been developed) can be queried by a standard pS query client, without having to go through the rest of IMF, or having to use IMF semantics."
     66 * "OMF compatibility" means "any controllable substrate which is IMF-controllable (i.e. for which an IMF Substrate Control Handler module has been developed) can be viewed as an OMF controllable resource by an OMF experimenter, and controlled using an OMF experiment, without having to go through the rest of IMF, or having to use IMF semantics."
     67
     68'''''pS''''':  As we have discussed previously, using pS compatible channels for sensing does not realistically allow enabling many cross-layer experiments.  We took our goal to be defined by the following: "pS-compatibility" means "any measurement resource which is IMF-readable - for which an IMF Measurement Handler module has been developed - can be queried by a standard pS query client, without having to go through the rest of IMF, or having to use IMF semantics."
     69
     70Since GEC10, our goal was that (i) the IMFpSRealTime service should be indistinguishable from a reasonable MA service for existing pS query clients, and (ii) well-packaged ready code would be available for anybody who wants it.  We have effectively achieved these goals, we are now working on a test deployment on LEARN.
     71
     72'''''OMF''''':  We spent a significant time thinking about what it meant "to use OMF semantics for the substrate control channel".  We settled on a similar definition as for pS:  "OMF compatibility" means "any controllable substrate which is IMF-controllable - for which an IMF Substrate Control Handler module has been developed - can be viewed as an OMF controllable resource by an OMF experimenter, and controlled using an OMF experiment, without having to go through the rest of IMF, or having to use IMF semantics."  We do not believe using OMF saves any effort in the IMF development; as before, we see the benefit as the accessibility to those used to OMF semantics.
     73
     74   There are multiple potential ways of interfacing the IMF semantics with OMF, and we have articulated them.  Basically the IMF Substrate Control Handler will behave as an OMF resource controller, and allow control through OMF.  This does not realistically support timescales suitable for cross-layer control.  The IMF system can provide access to the resource controller through a "long-standing" OMF experiment that basically acts as a slave, or repeater, for cross-layer control commands.  However, though we might investigate this option as a value-add, with the GPO's advice, we have settled on our primary goal as being simply to incorporate an OMF resource controller interface to the IMF substrate control handler.
     75
     76   Neither pS nor OMF allows timescales which are required for many cross-layer automated protocols.  But different experiments may utilize measurement readings of different freshness or timescales.  It would be meaningful to build in semantics for multiple measurement characteristics in IMF, and be able to provide experimenters with information about the timescales of available measurement and actuation sources.
     77
     78'''''Metadata''''':  For cross-layer adaptive and responsive protocols within the slice, such as IMF should enable, it is important for the experimenter to know a few things about the available measurements: at what frequency are fresh measurements available, what is the latency with which the system can deliver the fresh data to the consumption point, whether the sensing can be adjusted to some extent by the consumer - scheduled ahead of time, or frequency changed?  The same are also true of actuation capabilities.  Earlier in the project, we simplified measurement into "realtime" and "not realtime" categories, i.e. those suitable for cross-layer control use, and those not.  Actually there is a continuous spectrum between them, and different ones can be useful for dealing with different cross-layer control issues.
     79
     80   The measurement metadata, such as is being standardized in the I&M group now, should contain some "pointer" to RSPECs that connect it to the capabilities of the resource that produced the data, which would address the above issues.  The measurement consumer can refer to the RSPEC for that resource if they want to.  The MDOD should also contain some metadata that helps the cross-layer algorithm decide whether it is "usable" or not, or how usable.  A fine-grained timestamp, as envisaged in Section 4.1.2 of the GENI-SE-IM-ARCH-1.0 document, would certainly be useful there.  Other potentially useful metadata includes a reference to a "stream" of measurements of which this particular measurement is a part.  Incorporating these potential extensions into the MDOD and implementing the MDOD into IMF-sourced measurement data is part of the envisaged future of the IMF project.
    6681
    6782== Project Participants ==
     
    91106== Code Snapshot ==
    92107
    93 The GEC11 version of the IMF system can be built from source in the following tarballs:
     108The GEC11 version of the IMF system can be built the following.  Documentation is included in the code.
    94109
     110 * [attachment:something.something perfSONAR standalone command-line client for IMF measurements]  <-- NEED THIS !!!
     111 * [attachment: perfSONAR standalone GUI client for IMF measurements]
    95112 * [attachment:mh.tar.gz Measurement Handler]  <-- NEED THIS !!!
    96113 * [attachment:pubsub_for_perfsonar.tar.gz PubSub for perfSONAR] <-- NEED THIS !!!
    97114 * [attachment:perfsonar_imf_realtime.tar.gz perfSONAR IMF Realtime service]  <-- NEED THIS !!!
    98115
     116The pS clients are configured to try to access data from the IMF Measurement Handlers running on the BEN testbed, to retrieve port power and BER measurements made on Polatis and Infinera switches.  To successfully run this, you need VPN access to the management plane network of BEN.  Get in touch with the IMF team to obtain this access, if you need it.
     117
    99118== Documentation and Release Notes ==
    100119