Description

It is worthwhile and very important to have a client API for PerfSONAR which have following functions

• Provide a wrapper arround perfSONAR services
• Provide an interface for each services to fetch data for visualization and analysis.
• Hiding the XML parsing complexity behind request/response

Use Cases

• What are all the interfaces that a service publish its utilization to perfSONAR framework?
• What is the utilization for any specific interface supported by perfSONAR?

Implementation

Overview 

There are two ways to implement this

1. Query Lookup service
   • Query the lookup service for the metadata of a specific evenType
   • Lookup service will return all the metadata and its associated service url to query
   • Query the service url for the specific information directly from the service url
2. Static Mapping of Service URL
   • Get the MAs.conf static service url mapping file from perfSONARUI.
   • Query metadata for an eventType e.g. utilization for each service.
   • Query the interface utilization request directly to service

Considering the current deployement status of lookup service, not all the services are registers. There is an implementation of Multi-Lookup service, where each local domain look up service register itself with other domains lookup service to create hierarchy but there is not such heirarchy in place by this date. Hence we are starting implementation without query Lookup service for metadata i.e. Static  Mapping of  service  URL. In future, we will update the API to query Lookup service for metadata instead of Service directly.

 Details