perfsonar development work

[Roman Lapacz <>]

On Tue, 17 Apr 2007, Murilo Vetter wrote:

> Hi,

Hi

> The messages were changed to fit this need. It is better now.
>
> You can call the service now this way:
>
> *****************
>
> <nmwg:message type="TopologyRequest"
>       id="msg1"
>       xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";
>       xmlns:nmwgtopo3="http://ggf.org/ns/nmwg/topology/base/3.0/";>
>
> <nmwg:metadata id="11">
>
>       <nmwgtopo3:subject id="YYY">
>       </nmwgtopo3:subject>

Is empty subject is really needed? I think eventType is enough in this 
request.

>       
> <nmwg:eventType>http://ggf.org/ns/nmwg/topology/actions/list</nmwg:eventType>
>
>       <nmwgtopo3:parameters id="YYY">
>               <nmwg:parameter name="include">node,link</nmwg:parameter>

It would be good too have more flexible parameter element to define a list 
or maps, for example

<nmwg:parameter name="include">
  <nmwg:item>node</nmwg:item>
  <nmwg:item>link</nmwg:item>
</nmwg:parameter>

I would be useful not only in this request.

Roman


>               <nmwg:parameter name="level">detail</nmwg:parameter>
>       </nmwgtopo3:parameters>
>
> </nmwg:metadata>
>
> <nmwg:data id="data0" metadataIdRef="11"/>
>
> </nmwg:message>
>
> *****************
>
> In the parameter "include" you can put node, link or network.
> for example it can be:
>
> node
> link
> network
> node,link
> node,network
> link,network
>
> The level parameter should be defined when selecting the option: node
> in the include.
>
> I hope it fits to your need.
>
> Thanks, Murilo
>
>
> Yee-Ting Li escreveu:
>
> > Hi,
> >
> > we're trying to get some information from the topology service.
> >
> > what we are trying to do is to plot some information from the  topology 
> > service onto something like googlemaps. we have an example  at 
> > http://134.79.24.133:8080/cgi-bin/gmaps.pl
> >
> > the current version uses dns LOC records to determine the long lat 
> > location. if that fails it defaults to the use of geoiptools. of  course, 
> > the link information shown is false (blindly uses the array  of routers if 
> > the geographical location can be found), rather than  information from bgp, 
> > cdp etc.
> >
> > for optimal efficiency, we would like to be able to query for both  the 
> > link information and the detailed node information on the same  xml. for 
> > example:
> >
> > === example ===
> > <nmwg:message type="TopologyRequest"
> >         id="#tops"
> >         xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";
> >         xmlns:nmwgtopo3="http://ggf.org/ns/nmwg/topology/base/3.0/";>
> >
> >   <nmwg:metadata id="#meta1">
> >     <nmwgtopo3:subject id="#sub1"></nmwgtopo3:subject>
> >     <nmwg:eventType>http://ggf.org/ns/nmwg/topology/actions/node/ 
> > list/detail</nmwg:eventType>
> >     <nmwgtopo3:parameters id="#params1"></nmwgtopo3:parameters>
> >   </nmwg:metadata>
> >
> >   <nmwg:data id="#data1" metadataIdRef="#meta1"/>
> >
> >   <nmwg:metadata id="#meta2">
> >     <nmwgtopo3:subject id="#sub2"></nmwgtopo3:subject>
> >     <nmwg:eventType>http://ggf.org/ns/nmwg/topology/actions/link/ 
> > list</nmwg:eventType>
> >     <nmwgtopo3:parameters id="#params2"></nmwgtopo3:parameters>
> >   </nmwg:metadata>
> >
> >   <nmwg:data id="#data2" metadataIdRef="#meta2"/>
> >
> > </nmwg:message>
> > ======
> >
> > however, the returned xml response only contains information  regarding the 
> > link information and NOT the node information.  (regardless of the order in 
> > which the <nmwg:data/> elements are placed.
> >
> > is it possible to do a single request for such information? (ie both  node 
> > and link info)
> >
> > also, does any one else have any topology services from which we can 
> > query?
> >
> > thanks,
> >
> > Yee.