perfsonar development work

[Roman Lapacz <>]

Jeff W. Boote wrote:
> [Adding perfsonar-dev to CC list. This is exactly the place this 
> conversation should happen. (Unless/until we create a 
> perfsonar-steering...)]
>
> I'm going to try and re-pull the list together based on the feedback 
> so far. And I'm adding my own personal favorite service. ;) :
>
> Services:
>   - utilization RRD MA (Other metrics? Who can work on it?)
>   - SQL MA (utilization/L2 path status) [Potential plug-in interface 
> if ready]

Jeff,

take a look at my email from July 5 (12:02)

[...]
"Currently, only the utilization and L2 path status are supported. If 
the eventType in the request has other metric name then the service 
returns error ("eventType, specified in the request message, is not 
supported"). Of course we can easily support more metrics which are 
similar to utilization (listed above) but there should be official 
agreement on this. "
[...]


Roman

>   - LS (single + [multidomain - only with serious work])
>   - ALCATEL NMS MP
>   - SNMP MP
>   - TELNET/SSH MP
>   - Command-Line MP (bwctl,owamp,ping [perhaps even ntpq, traceroute])
>
> Other:
>   - performance targets (we need to quantify, but it would be good to 
> set expectations)
>   - scheduled measurements (used by what services?)
>   - result codes
>   - jUnit tests
>   - push [only with more work]
>
> It was not my intention to leave anything out, or to include things 
> that others said could not happen. I was just trying to reduce it down 
> to a short readable list again... (I did keep a few things with 
> comments next to them that they would only make it if someone new is 
> assigned to work on them.) So, if I made mistakes, please correct. 
> But, lets try and get this down to a list that can be sent out to the 
> community at large a week or so after the release.
>
> jeff