perfsonar development work

["Jeff W. Boote" <>]

Roman Lapacz wrote:
> HI Nina and Vedrin,
>
> Vary good points!
>
> What do you think to take this simple solution: just putting parameters 
> of rrdcreate in the keys in the rrd metadata configuration file.
>
> example:
>
> <nmwg:data id="data1" metadataIdRef="meta1">
> <nmwg:key>
> <nmwg:parameters>
> <nmwg:parameter 
> name="file">/opt/perfsonar-20060724/data/rrd/test/test.rrd</nmwg:parameter>
> <nmwg:parameter name="dataSource">bytes</nmwg:parameter>
> <nmwg:parameter name="valueUnits">Bps</nmwg:parameter>
> <nmwg:parameter name="step">60</nmwg:parameter>
> <nmwg:parameter name="rra">RRA:AVERAGE:0.5:1:1147680 
> RRA:MAX:0.5:1:1147680 RRA:MIN:0.5:1:1147680</nmwg:parameter>
> <nmwg:parameter name="dataSourceType">COUNTER</nmwg:parameter>
> </nmwg:parameters>
> </nmwg:key>
> </nmwg:data>
>
>
> MetadataKeyResponse message would contain all this information and it 
> would be up to the client app how to use it.
>
> What do you think?

And what happens if I store my utilization data in an SQL archive. This would 
force every client to understand my internal SQL table representation to 
determine the resolution and periodic nature of my data. (More specifically, it 
would force the clients to have to understand a different way to get this 
information from every single service that exports utilization data from a 
different type of archive.) The point of the schema should be to come up with a 
standard way to represent this information. Then the rrd fields could be used to 
populate the 'standard' ones.

This sounds like a really good first example of a protocol that should be 
standardized as we have discussed this week.

Along these lines, there used to be examples of chaining that represented the 
statistics that were available using a filter-chained metadata. Unfortunately I 
have not been able to find them, and I don't want to concentrate too hard on it 
now during the meeting. I think they were removed because the current services 
could not understand them and they were not kept up to date with the namespace 
changes. But, I still think that was the more appropriate way to represent this 
information.

Anyone have copies of the example XML files that used statistics in filter 
chaining somewhere? If I remember correctly we were working on it in Poznan last 
year... I will keep looking - but I will probably have to dig into the old CVS 
to find it.

jeff