perfsonar development work

[Roman Lapacz <>]

Jason Zurawski wrote:
> Roman;
>
> > could you send example messages (or their addresses) of those 3 
> > proposals.
>
> The branch can be found here:
>
> http://anonsvn.internet2.edu/svn/nmwg/branches/snmp/
>
> The files that need to be examined are located in that directory:
>
> TODO_SNMP.txt
> example_instances/(snmp|utilization|errors|discards)/*xml
> rnc/(snmp|utilization|errors|discards).rnc
>
> The immediate commentary will be required on the discards/errors 
> examples.  The SNMP namespace may be implemented in time when we are 
> not as rushed for a deadline, but these two characteristics can stand 
> on their own.

Generally examples are very similar to the utilization ones and that's 
good. I have few comments:

1) 
http://anonsvn.internet2.edu/svn/nmwg/branches/snmp/example_instances/errors/store.xml

I think the namespace 'errors' for parameters element in metadata is 
not needed because eventType says what parameters are expected. I 
suggest to use 'nmwg' namespace there:

   <nmwg:parameters id="p1">
     <nmwg:parameter name="valueUnits">Eps</nmwg:parameter>
   </nmwg:parameters>

 besides valueUnits parameter is already located in the key (but I 
assume we may have some parameters for errors)


2) 
http://anonsvn.internet2.edu/svn/nmwg/branches/snmp/example_instances/errors/store.xml

supportedEventType parameter is not needed in the key. Data element with 
a key refers to metadata where supportedEventType is present.


3) 
http://anonsvn.internet2.edu/svn/nmwg/branches/snmp/example_instances/errors/store.xml

This file is store file so metadata should contain this:

       <nmwg:parameters>
           <nmwg:parameter 
name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/errors/2.0</nmwg:parameter>
       </nmwg:parameters>

instead of this:

       
<nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/errors/2.0</nmwg:eventType> 



4) For now I suggest not to use more than one supportedEventType 
parameters in metadata in a store file. Let's start with one such 
parameter. Later we will add support for multiple.

5) 
http://anonsvn.internet2.edu/svn/nmwg/branches/snmp/example_instances/errors/MDKRequest1.xml

 I suggest using unix time as default time format in select parameters 
(startTime, endTime). Additionally, we could use ISO format but this way 
(RRD MA and SQL MA support it for utilization):

     <nmwg:parameter name="startTime">
         <nmtm:time type="ISO" value="2005-07-16T00:00:00Z"/>
     </nmwg:parameter>


6) 
http://anonsvn.internet2.edu/svn/nmwg/branches/snmp/example_instances/errors/MDKRequest2.xml

Parameters in the key in metadata m3 represent more than one namespace 
so it should look like this:

   <nmwg:key id="1">
     <nmwg:parameters id="1">
       <nmwg:parameter 
name="supportedEventType">http://ggf.org/ns/nmwg/characteristic/errors/2.0</nmwg:parameter>
       <nmwg:parameter name="type">rrd</nmwg:parameter>
       <nmwg:parameter name="valueUnits">Eps</nmwg:parameter>     
       <nmwg:parameter 
name="file">/home/jason/perfSONAR-PS/MP/SNMP/mead.rrd</nmwg:parameter>
       <nmwg:parameter name="dataSource">eth0-ifInErrors</nmwg:parameter>
     <nmwg:parameters id="2">
     <select:parameters id="2">
       <nmwg:parameter name="startTime" value="N-50" />
       <nmwg:parameter name="endTime" value="N" />
       <nmwg:parameter name="resolution" value="1" />
       <nmwg:parameter name="consolidationFunction" value="AVERAGE" />      
     </select:parameters>
   </nmwg:key> 


This approach should be used in requests and responses.



Roman






> -jason