perfsonar development work

["Jeff W. Boote" <>]

Roman Lapacz wrote:
> 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. " [...]

Right - that is why I said utilization/L2 for sure, and others if 'plug-in
interface' is ready. I'm confused, are you saying the utilization/L2 path 
stuff
is not available? Or are you saying the part I put in []'s - that will be
available if ready won't be available?

I'm confused, do you want or not want this in the list of planned services?

(I called it a plugin interface based on your email July 3rd:

> Quite soon I'm going to implement plugin-like metric support. Supported
> metrics will be listed in the config file and the service will load certain
> classes (each one will represent a metric) during startup.

)

jeff