Skip to Content.
Sympa Menu

perfsonar-dev - Re: [pS-dev] Lookup service playground tab

Subject: perfsonar development work

List archive

Re: [pS-dev] Lookup service playground tab


Chronological Thread 
  • From: Szymon Trocha <>
  • To: "" <>
  • Subject: Re: [pS-dev] Lookup service playground tab
  • Date: Mon, 10 Aug 2009 14:33:08 +0200
  • Organization: PCSS

Jason,

Jason Zurawski pisze:
I have explained this on numerous occasions before, and nothing has really changed: we are aware that the IP summarization is not as tight as some would like them to be. There is ongoing work with a student at the University of Delaware to improve the algorithm and he has a report on his results so far available here:

I think this work seems to be crucial if we want to have gLS infrastructure usable.

http://code.google.com/p/perfsonar-ps/wiki/IPSummarization

and

https://damsl.cis.udel.edu/svn/perl-iptrie/README.html

I have not had a chance to incorporate his work into the gLS releases yet, so this is still untested in a production environment. We will be working towards releasing this before the end of the year. Until then our suggestion of how to work around this still stands: multiple queries to the result hLSs will be be required to determined if these instances do or do not hold what you are looking for.

As for your results below I took a look at the hLS installed on p-mdm.ps-lhcopn.fnal.gov, I would encourage all to see the internal view here:

http://dc211.internet2.edu/cgi-bin/pA/view.cgi?hls=http://p-mdm.ps-lhcopn.fnal.gov:8080/geant2-java-xml-ls/services/LookupService

This is an MDM hLS, so I am not aware of the specifics of how it works on the inside. According to the view of the hLS summary set (represented as "Collection: http://ogf.org/ns/nmwg/tools/org/perfsonar/service/lookup/discovery/xquery/2.0"; and "Store Type: LSStore-summary" - scroll all the way to the bottom) there is nothing there. This may mean:

1) I am not querying this set correctly, I will let the MDM hLS maintainer answer if I am doing this correctly. If there is a problem with my query, that would indicate a bug in my CGIs which I will gladly fix. I am sending this query:

<nmwg:message type="LSQueryRequest"
id="LSQueryRequest"
xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";

xmlns:xquery="http://ggf.org/ns/nmwg/tools/org/perfsonar/service/lookup/xquery/1.0/";>
<nmwg:metadata id="meta1">
<xquery:subject id="sub1">
declare namespace nmwg="http://ggf.org/ns/nmwg/base/2.0/";;

/nmwg:store[@type="LSStore-summary"]/nmwg:metadata
</xquery:subject>

<nmwg:eventType>http://ogf.org/ns/nmwg/tools/org/perfsonar/service/lookup/discovery/xquery/2.0</nmwg:eventType>
</nmwg:metadata>
<nmwg:data metadataIdRef="meta1" id="d1"/>
</nmwg:message>

I do get a response (but it is vaugue):

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";><soapenv:Body><nmwg:message xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/"; id="LSQueryRequest_resp" messageIdRef="LSQueryRequest" type="LSQueryResponse"><nmwg:metadata id="LSQueryResponseMetadata"><nmwg:eventType>success.ls.query</nmwg:eventType></nmwg:metadata><nmwg:data id="LSQueryResponseData" metadataIdRef="LSQueryResponseMetadata"><psservice:datum xmlns:psservice="http://ggf.org/ns/nmwg/tools/org/perfsonar/service/1.0/"/></nmwg:data></nmwg:message></soapenv:Body></soapenv:Envelope>



2) The set is empty and the service is not summarizing, would indicate a bug in the service

3) The service just came up and did not have a chance to summarize yet (unlikely, this appears to have been registered for a while but I can't prove this from where I sit)

I can ask Service Desk to help in verification of 1 and 3

regards,
--
Szymon Trocha

Poznan Supercomputing & Netw. Center ::: NETWORK OPERATION CENTER
Tel. +48 618582022 ::: http://noc.man.poznan.pl



Archive powered by MHonArc 2.6.16.

Top of Page