perfsonar development work

[Jason Zurawski <>]

Nina;

The mentioned bug did not address the known IP summarization problems. 
There is active work going on at UDel to address that particular problem 
but it has not been incorporated into new releases of the hLS or gLS.

It would be good to record the perfSONAR-UI specific use case (e.g. 
trying to find utilization data by IP address) as well as other 
potential use cases both for GUIs and APIs as a next step.  This will 
require input from users and developers across the perfSONAR spectrum.

We have started a partial list of "Information Service Use Cases" here 
as an example of what should be considered:

https://spaces.internet2.edu/display/ISWG/Use+Cases

Thanks;

-jason


> > > According to my records there was a bug found and fixed in March
> > > (http://code.google.com/p/perfsonar-ps/issues/detail?id=109) for both
> > > LS implementations.
> > >
> > > Since the Geant2 project was in transition at the time, there has
> > > been no additional communication regarding if this fixes the original
> > > problem 
> > I know. We also changed LS and LS API developers. That's why Krzysztof
> > would like to go back to this discussion.
> >
> > > with the GUI or APIs or what next steps may be.  There have not been
> > > any more discussion regarding requirements or expectations from the
> > > GUI (and Service) developers on how the information architecture may
> > > be improved to answer the appropriate questions, but hopefully this
> > > can be a priority down the road.
> > I think we would need some hints here from psUI developers. The goal
> > should be to make the information provided by LS cloud components
> > (including API) useful for user and tools including performance and
> > accuracy expectations.
> >
> > How would you suggest to proceed? May be should (re)run some tests?
> > What kind?
> I've rerun the test
> (org.perfsonar.perfsonarui.test.ls.TracerouteTest#testNewLookup() ) . It
> tries to retrieve MA services, containing utilization data for the
> following IP addresses.
>
>                 "150.254.185.146",//  (PIONIER)
>                 "192.5.40.187",
>                 "212.191.224.74",
>                 "194.141.0.10"//  (BREN)
>
> The result is ESnet MA is found  as a response to the request for
> 150.254.185.146 and  192.5.40.187 .  The full perfsonar.log with
> requests/response is attached.
>
> [ESnet SNMP MA] 150.254.185.146 N/A N/A
> ESnet SNMP
> MA,http://ps3.es.net:8080/perfSONAR_PS/services/snmpMA,http://schemas.perfsonar.net/2.0,,http://ggf.org/ns/nmwg/characteristic/utilization/2.0
> [ESnet SNMP MA] 192.5.40.187 N/A N/A
> ESnet SNMP
> MA,http://ps3.es.net:8080/perfSONAR_PS/services/snmpMA,http://schemas.perfsonar.net/2.0,,http://ggf.org/ns/nmwg/characteristic/utilization/2.0
> [] 212.191.224.74
> [] 194.141.0.10
>
> Best regards,
> Nina
>
> > Regards,