Skip to Content.
Sympa Menu

perfsonar-dev - Re: [pS-dev] question on LS registration (XML schema for registration)

Subject: perfsonar development work

List archive

Re: [pS-dev] question on LS registration (XML schema for registration)


Chronological Thread 
  • From: Guilherme Fernandes <>
  • To: ulisses <>
  • Cc: Jason Zurawski <>, ,
  • Subject: Re: [pS-dev] question on LS registration (XML schema for registration)
  • Date: Thu, 30 Nov 2006 09:59:15 -0200

ulisses wrote:

Hi Jason, all

I'm not sure who I should send this question since LS IMHO only stores opaque data in the eXistDB.

Hi,

I'm not the one that should be answering this, but I guess there's no harm. The registration message could have any nmwg schema compatible information, so if there's no field suitable in the current schemas you could add this field to the schema being used for the topology service and put it in the message.

The data element can be empty.

Regards,

Guilherme

Currently the message we want to use in the registration is:

<nmwg:message type="LSRegisterRequest"
id="msg1"
xmlns:perfsonar="http://ggf.org/ns/nmwg/tools/org/perfsonar/1.0/";
xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";

xmlns:psservice="http://ggf.org/ns/nmwg/tools/org/perfsonar/service/1.0/";
xmlns:nmwgt="http://ggf.org/ns/nmwg/topology/2.0/";

xmlns:netutil="http://ggf.org/ns/nmwg/characteristic/utilization/2.0/";>

<nmwg:metadata id="serviceLookupInfo">
<perfsonar:subject id="commonParameters"
xmlns:perfsonar="http://ggf.org/ns/nmwg/tools/org/perfsonar/1.0/";>
<psservice:service id="serviceParameters"
xmlns:psservice="http://ggf.org/ns/nmwg/tools/org/perfsonar/service/1.0/";>
<psservice:serviceName>Topology Service</psservice:serviceName>

<psservice:accessPoint>http://tux.rediris.es:8090/axis/services/TopologyService</psservice:accessPoint>
<psservice:serviceType>TOPS</psservice:serviceType>
<psservice:serviceDescription>Topology Service,
perfSONAR</psservice:serviceDescription>
</psservice:service>
</perfsonar:subject>
</nmwg:metadata>

<nmwg:data id="data0" metadataIdRef="serviceLookupInfo"/>

</nmwg:message>

I think this is ok, but it lacks something we need:

We are insterested in specifying the domain_name for which the Topology
Service is
serving topology data.

I have seen Service.java but there is no way of specifying domain_name or analogous, I also took a look at other .java files but found nothing.

Currently we are exporting the domain_name as the institution attribute of a
Node,
but I don't see a proper way for this case.

how I could add this information to the registration?

Also, can somebody confirm me that the data element can be empty?

Thanks so much

Ulisses

_______________________________ __ ___________________________________
/_/
Network Operation Center __ __ Email:

RedIRIS/Red.es /_/ RedIRIS /_/
Edificio Bronce __ Tel: + 34 912127625
Pza. Manuel Gómez Moreno, s/n /_/ Urgencias: + 34 629148201
E-28020 Madrid Fax: + 34 915568864

_________________ Spanish Academic & Research Network _______________________





Archive powered by MHonArc 2.6.16.

Top of Page