perfsonar-dev - Re: [pS-dev] serviceType/serviceVersion values in LS registration
Subject: perfsonar development work
List archive
- From: Jason Zurawski <>
- To: Nina Jeliazkova <>
- Cc: Michael Bischoff <>, "Jeff W. Boote" <>,
- Subject: Re: [pS-dev] serviceType/serviceVersion values in LS registration
- Date: Sat, 24 May 2008 09:20:24 -0400
- Openpgp: id=B94D59A6; url=http://people.internet2.edu/~zurawski/key.txt
- Organization: Internet2
All;
(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.
The topology elements are tied to the various data schemata through eventTypes.
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?
It could be done that way, but the Topology service and Lookup service are both well known information services (and as such will probbaly be combined in the near future).
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?
All three things (eventTypes, addresses [currently IP v4 and v6] and domain information) can and will be used to categorize data throughout the framework. This is really the only effective way to locate and avoids pitfalls like relying on user defined service information like type, name, or description.
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?
Our current use case relies on IP because that is the data we deal with regularly. The same idea should be easily extended to other address/identification types.
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!
The 3 tuple of address/domain/eventType covers all major discovery issues in my opinion, if we are missing a major type I would appreciate feedback on the API.
-jason
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.
- serviceType/serviceVersion values in LS registration, Nina Jeliazkova, 05/23/2008
- Re: [pS-dev] serviceType/serviceVersion values in LS registration, Jeff W. Boote, 05/23/2008
- Re: [pS-dev] serviceType/serviceVersion values in LS registration, Michael Bischoff, 05/23/2008
- Re: [pS-dev] serviceType/serviceVersion values in LS registration, Jeff W. Boote, 05/23/2008
- Re: [pS-dev] serviceType/serviceVersion values in LS registration, Michael Bischoff, 05/23/2008
- Re: [pS-dev] serviceType/serviceVersion values in LS registration, Nina Jeliazkova, 05/24/2008
- Re: [pS-dev] serviceType/serviceVersion values in LS registration, Jason Zurawski, 05/24/2008
- Re: [pS-dev] serviceType/serviceVersion values in LS registration, Nina Jeliazkova, 05/24/2008
- Re: [pS-dev] serviceType/serviceVersion values in LS registration, Nina Jeliazkova, 05/24/2008
- Re: [pS-dev] serviceType/serviceVersion values in LS registration, Jason Zurawski, 05/24/2008
- Re: [pS-dev] serviceType/serviceVersion values in LS registration, Nina Jeliazkova, 05/26/2008
- Re: [pS-dev] serviceType/serviceVersion values in LS registration, Jason Zurawski, 05/27/2008
- Re: [pS-dev] serviceType/serviceVersion values in LS registration, Nina Jeliazkova, 05/27/2008
- Re: [pS-dev] serviceType/serviceVersion values in LS registration, Nina Jeliazkova, 05/26/2008
- Re: [pS-dev] serviceType/serviceVersion values in LS registration, Jason Zurawski, 05/24/2008
- Re: [pS-dev] serviceType/serviceVersion values in LS registration, Michael Bischoff, 05/23/2008
- Re: [pS-dev] serviceType/serviceVersion values in LS registration, Jeff W. Boote, 05/23/2008
- Re: [pS-dev] serviceType/serviceVersion values in LS registration, Michael Bischoff, 05/23/2008
- Re: [pS-dev] serviceType/serviceVersion values in LS registration, Jeff W. Boote, 05/23/2008
Archive powered by MHonArc 2.6.16.