Skip to Content.
Sympa Menu

perfsonar-dev - Re: [pS-dev] serviceType/serviceVersion values in LS registration

Subject: perfsonar development work

List archive

Re: [pS-dev] serviceType/serviceVersion values in LS registration


Chronological Thread 
  • From: Nina Jeliazkova <>
  • To: Michael Bischoff <>
  • Cc: "Jeff W. Boote" <>,
  • Subject: Re: [pS-dev] serviceType/serviceVersion values in LS registration
  • Date: Sat, 24 May 2008 07:43:06 +0300

Michael Bischoff wrote:
(I'm not up completely to speed with LS affairs so forgive me if I make
stupid remarks ;)

That makes sense, be can we facilitate the whole process currently? Don't we
also need to ask
(a) service(s) to identify the network topology elements? If not the current
structure of the
topology itself.

Through google I stumpled upon this:
http://www.ogf.org/OGF21/materials/895/topoSchema-OGF21.pdf (how much of the
doc is still
accurate btw)

Use Case:
A client would use a topology service to look
up the identifier for a network element and
then would query a lookup service using the
identifier to find the measurements
associated with that element.

Obtaining a topology service must also be retrieved from a LS? right?

Also level 1 ls client api seems to include eventType? is that the same as we
are talking about?
http://anonsvn.internet2.edu/svn/nmwg/trunk/nmwg/doc/dLS/gLS/phase_1_color.html#level1_api
Are topology elements identified by Ip adress/dns name? and is thus the (IP
Address | Domain)
part corresponding to a topology element?
Identifying topology elements by IP (v4, or v6?) makes the whole schema a bit restrictive. What if we need to monitor a layer 2 switch?
I vaguely remember similar discussion in Seville meeting last autumn and a statement the correspondence between e.g. interfaces in MA and topology elements will be defined in a different schema, that is under development.

The whole idea to identify a topology element with IP and domain name emerged as a _temporary_ solution!

Best regards,
Nina
Best regards,
Michael Bischoff

The query we were expecting was:


What services (no matter the type) have data related to the following
network topology elements?

jeff

On May 23, 2008, at 3:07 PM, Michael Bischoff wrote:


I'm not sure if its a valid use-case to figure out what kind of
services a LS contains unless the LS is also bound to a Location/area. (so
something along
the lines of which (h)Ls-es are there along the path -> what tools(->read
services) do I
have avail to test this route?

But to be honest for the near future I expect users to look for
services by organisation (like what perfSONAR services are there available at
Belnet)
(perhaps summarization in the
gLS/dLS context should look at sending info on that too)


That 'can' be? Or that currently exist in any given LS?



Since new services can be created by anyone at any time, all possible
values can never be given.

jeff

On May 23, 2008, at 11:59 AM, Nina Jeliazkova wrote:



All,



Is it possible to list all possible serviceType values, that can be
registered in a Lookup service? e.g. for RRD-MA, SQL-MA, Hades, BWCTL, Telnet
SSH, etc.?



I am looking for a way to establish a correspondence between the
information currently stored in MA.conf and one retrieved from a Lookup
service.


Best regards,
Nina








Archive powered by MHonArc 2.6.16.

Top of Page