perfsonar development work

[Sven Ubik <>]

Hi Loukik,

> I am interested in knowing if there are any new commands that CMP can do 
> which CL-MP does not currently do. If so, could these products be merged 
> somehow?

The difference is that CL-MP supports several monitoring tools, but the
request for each tools is specific for that tools (if I am wrong, correct 
me), such as for ping:

  <nmwg:eventType>ping</nmwg:eventType>
  <ping:parameters id="param1">
     <nmwg:parameter name="count">10</nmwg:parameter>
     <nmwg:parameter name="interval">1</nmwg:parameter>
     <nmwg:parameter name="packetSize">64</nmwg:parameter>
     <nmwg:parameter name="ttl">255</nmwg:parameter>
  </ping:parameters>

whereas CMP does not know anything about any specific tool, it uses the 
same request format for any tool, such as for ping:

 <nmwg:eventType>command</nmwg:eventType>
 <nmwg:parameters id="param1">
    <nmwg:parameter name="command">ping_rtt.sh</nmwg:parameter>
    <nmwg:parameter name="argument">www.cesnet.cz</nmwg:parameter>
    <nmwg:parameter name="argument">3</nmwg:parameter>
 </nmwg:parameters>

In this example, it uses a short script ping_rtt.sh to invoke ping. 
Similar scripts can be written for other current or future tools
without changing the measurement point.

CMP server can execute the requested command locally or on another 
computer over ssh, which can be requested by:

 <command:subject id="sub1">
   <nmwgt:interface>
      <nmwgt:hostName>hostname.domain</nmwgt:hostName>
      <nmwgt:ifName>username</nmwgt:ifName>
   </nmwgt:interface>
 </command:subject>

Regards,

Sven