Skip to Content.
Sympa Menu

perfsonar-dev - Re: [pS-dev] what services should register into LS [was:Re: BWCTL,Hades and Lookup service]

Subject: perfsonar development work

List archive

Re: [pS-dev] what services should register into LS [was:Re: BWCTL,Hades and Lookup service]


Chronological Thread 
  • From: Verena Venus <>
  • To:
  • Cc: Nina Jeliazkova <>, "Jeff W. Boote" <>, Nicolas Simar <>, WiN-Labor <>, Prodromos Gerakios <>, "" <>
  • Subject: Re: [pS-dev] what services should register into LS [was:Re: BWCTL,Hades and Lookup service]
  • Date: Thu, 29 May 2008 10:23:07 +0200

Hello everybody,

Am Mittwoch, 28. Mai 2008 20:50:53 schrieb Jason Zurawski:
> All;
>
> >>> We are discussing what information services should register into LS,
> >>> besides service URL. Recently, Jason advised to recognize service
> >>> type by eventtypes, rather than by arbitrary strings like one found
> >>> in "servicetype" parameter.
> >>>
> >>> This seems to work fine with RRD MA services, but not all other
> >>> services submit information about eventtypes when registering to LS.
> >>> Is there a guidance what schema should be supported in this case?
> >>
> >> Could you be more specific? Which services are not registering
> >> eventTypes? This disrupts the dLS (and gLS) summarization model as
> >> well...
> >
> > So far I am aware of flowsa MA, developed at Surfnet , and BWCTL and
> > Hades by Win-Labor. Verena is going to add support for eventtypes,
> > but was asking of the syntax to be supported. Could you please advise
> > her?
>
> I am not sure I understand the request, services should be registering
> with the LS in a manner similar to the RRD MA etc. where they register a
> Service metadata description, and the metadata elements they are
> personally responsible for. These metadata elements *should* include
> eventType elements for the particular data they pertain to. The
> examples that can be examined are related to the RRD MA (this is the
> only one I personally know of, perhaps there are more).
>
Good to know. In the past, I undertook several attempts, to implement
something based on an example of another service. However, this did not work
in a lot of cases, as examples tend to be outdated sooner or later.

It would be a good idea, if anyone expects services to implement based on an
example, to state this clearly which example, and if this is going to be the
one which is specified (hopefully) sooner or later.

> >> I think we should concentrate effort to fix this on the service
> >> registration side, not by adding heuristics on the client side (which
> >> would then need to be copied to every other client).
> >
> > Yes, sure - we've already introduced some perfsonarUI code that relies
> > on eventtypes registered in LS and are trying to figure out how it
> > will work with services other than RRD MA.
>
> I can't really stress this enough: discovery will not work unless
> services are registering in the same manner.
^^^^^^^^^^^^^^^^^^^^^^^^^^

But that's exactly the point! All we want to know, is HOW this should look
like. We cannot implement it in the same manner, if we do not know this.

> If a service does not make
> available to the LS:
>
> a) Address information (ipv4 or perhaps ipv6)
> d) Domain information (fully qual hostname will do)
> c) any and all possible eventTypes
>
> Discovery will be meaningless. If service authors have questions or
> concerns about this, lets start talking about it very soon, and if you
> haven't done so *please* read the LS API document, this should explain
> everything:
>
> http://anonsvn.internet2.edu/svn/nmwg/trunk/nmwg/doc/dLS/gLS/phase_1_color.
>html
>
Good to know this one also. It is not obvious to me (and considering that
quite a lot of other services have not implemented this, it seems to be not
obvious to others, too) that the API for dLS is relevant for implementing the
API to LS! Sorry, but how do you expect me and others to find exactly this
document if noone points out that it is the one you need to implement when
properly registering to LS?

By the way, I had a look into it. Unfortunately it does not point to a schema
definition for the elements to be registered with a normal LS. So, still, I
do not know, how I should do this exactly.

It's not that I need a discussion what elements should be registered. I just
need to know which elements you need, and in what format I should register
them, that's all.

To summarize: I have absolutly no concerns with the content of a registration
message. All I want to know is the proper definition of this.

I'm not sure, where the RRDMA got the definition for the registration from,
but I would be more than happy is someone could point me to this information.

Considering existing schemata for LSRegistration, I found this one:
http://anonsvn.internet2.edu/svn/perfsonar/trunk/geant2_java-xml-ls/doc/schema/rnc/LSRegisterRequest.rnc

What is more or less exactly, what our service is registering at the moment.
I hope you understand now my problems.

Thanks,
Verena
--
Verena Venus, DFN-Labor
Friedrich-Alexander-Universität Erlangen-Nürnberg
Regionales RechenZentrum Erlangen (RRZE)
Martensstraße 1, 91058 Erlangen, Germany
Tel. +49 9131 85-28738, -28800, Fax +49 9131 302941


www.win-labor.dfn.de



Archive powered by MHonArc 2.6.16.

Top of Page