perfsonar-dev - Re: [Gn2-sa3-cnis] [pS-dev] Re: [GN2-JRA1] Retrieval of service location information
Subject: perfsonar development work
List archive
Re: [Gn2-sa3-cnis] [pS-dev] Re: [GN2-JRA1] Retrieval of service location information
Chronological Thread
- From: Toby Rodwell <>
- To: "Jeff W. Boote" <>
- Cc: Andreas Hanemann <>, Szymon Trocha <>, "" <>, GN-JRA1-list <>, GEANT2 cNIS <>
- Subject: Re: [Gn2-sa3-cnis] [pS-dev] Re: [GN2-JRA1] Retrieval of service location information
- Date: Tue, 14 Nov 2006 18:37:45 +0000
Hi Jeff/all,
Just to reassure you, cNIS will indeed implement interfaces for each and
every GN2 application (which includes perfSONAR). As and when the cNIS
service replaces TopS it will still implement the same TopS interface,
or to put it another way cNIS will honour and respect whatever interface
perfSONAR requires of it (and will do the same for the other GN2 apps).
However, for completeness, I wouldn't say that "... cNIS needs *to be*
an implementation of the perfSONAR TopS service specification", rather I
would say 'cNIS will implement the perfSONAR TopS service specification'.
regards
Toby
Jeff W. Boote wrote:
> Andreas Hanemann wrote:
>> Yes, you are right. The cNIS service will replace the TopS and it will
>> cover requirements from (at least) JRA1, JRA3, JRA4, and SA3.
>
> I don't disagree, but I would like to clear one issue up. The TopS
> perfSONAR
> interface/protocol is not being replaced. I realize when you say replace,
> you
> probably mean replace the current TopS implementation.
>
> I only bring this up to make sure we distinguish between the TopS
> "interface/protocol" and the TopS implementation. I think these two things
> could
> be getting confused in this discussion. (If not, please ignore this
> message. ;) )
>
> From an implementation perspective in JRA-1, there is no problem with any
> of
> the discussions I have seen. But I bring this up because of
> interoperability
> concerns.
>
> I would say that cNIS needs to be an implementation of the perfSONAR TopS
> service specification. (cNIS can of course implement more interfaces.) But,
> to
> ensure interoperability with all the other networks in the world that are
> unlikely to deploy a full cNIS, we (perfSONAR) need to define very well the
> perfSONAR TopS interface and protocols.
>
> jeff
>
> _______________________________________________
> Gn2-sa3-cnis mailing list
>
> http://mail.dante.org.uk/mailman/listinfo/gn2-sa3-cnis
--
______________________________________________________________________
Toby Rodwell
Network Engineer
DANTE - www.dante.net
Tel: +44 (0)1223 371 300
Fax: +44 (0)1223 371 371
Email:
PGP Key ID: 0xB864694E
City House, 126-130 Hills Road
Cambridge CB2 1PQ
UK
_____________________________________________________________________
- Re: [GN2-JRA1] Retrieval of service location information, Roman Lapacz, 11/14/2006
- Re: [GN2-JRA1] Retrieval of service location information, Szymon Trocha, 11/14/2006
- Re: [GN2-JRA1] Retrieval of service location information, Andreas Hanemann, 11/14/2006
- Re: [pS-dev] Re: [GN2-JRA1] Retrieval of service location information, Jeff W. Boote, 11/14/2006
- Re: [pS-dev] Re: [GN2-JRA1] Retrieval of service location information, Andreas Hanemann, 11/14/2006
- Re: [Gn2-sa3-cnis] [pS-dev] Re: [GN2-JRA1] Retrieval of service location information, Toby Rodwell, 11/14/2006
- Re: [pS-dev] Re: [GN2-JRA1] Retrieval of service location information, Jeff W. Boote, 11/14/2006
- Re: [Gn2-sa3-cnis] [GN2-JRA1] Retrieval of service location information, Toby Rodwell, 11/14/2006
- Re: [GN2-JRA1] Retrieval of service location information, Andreas Hanemann, 11/14/2006
- Re: [GN2-JRA1] Retrieval of service location information, Szymon Trocha, 11/14/2006
Archive powered by MHonArc 2.6.16.