perfsonar development work

[Loukik Kudarimoti <>]

> Nina,
>
> I think there is a mis-understanding here. I just spent some time 
> testing out the SQL MA by making use of the documentation provided for 
> the RRD MA.
> In short, your requests are working as expected. Just try the second 
> request (SetupDataRequest_LastMeta.xml) with the start time: 
> 1143034700 and the end time 1143035770
>
> SQL MA RC6 is available here: 
> http://mu.dante.org.uk:8092/perfSONAR-SQL-MA-1.0-RC6/services/MeasurementArchiveService 
>
>
> RC5 is no more!
>
> Here are my findings:
>
> In your first request (SetupDataRequest_FirstMeta.xml), the first 
> metadata contains metadata paramters such as interface etc, which is 
> used to find which data to retrieve. The second metadata contains 
> filter paramters. By linking the data element to the first metadata 
> element, you are not providing any select parameters (i.e. start and 
> end time) because the second metadata is not in the chain. The service 
> hence tries to retrieve data using default start and end times. The 
> important point is that the default start and end times for SQL MA 
> (utilisation data) is the last know utilisation value.
>
> Hence, as a response for this request, you get the last known value.
>
> In your second request(SetupDataRequest_LastMeta.xml), the select 
> metadata is part of the chain so the service tries to find data for 
> the given time interval. It so happens that for test purposes, during 
> installation, there is just one data value entered into the sql 
> database for one metadata. The time value for this data entry falls 
> out of the range of the request that you are sending. Hence, as a 
> response for this request, you do not get any values because there are 
> no values in that time range.
>
>
> Let me know if this sorts out the problem.

Hi Nina, Vedrin,

Does this fix things? Is perfSONAR UI ready for SQL MA coming out in 2.0?


Andreas & David,

What about you guys?

Loukik.