perfsonar-dev - Re: [pS-dev] Definition of perfSONAR
Subject: perfsonar development work
List archive
- From: Maciej Glowiak <>
- To: Roman Lapacz <>
- Cc: "Eric L. Boyd" <>,
- Subject: Re: [pS-dev] Definition of perfSONAR
- Date: Tue, 10 Oct 2006 10:13:29 +0200
Roman Lapacz napisaĆ(a):
Eric L. Boyd wrote:
c) Conforming to the naming scheme for services
ACTION ITEM: Define naming scheme for services. Consider including developing institution, development language, service type, tool, e.g. DFN-PERL-MA-BWCTL service.
Including the name(s) of institution(s) doesn't look good for me. For example if there are 4 institutions involved: INTERNET2-DANTE-UoD-PSNC-MP-XXXXX
I agree. My proposal is to split the single name into several fields
(extended information in metadata) such as:
-serviceType (required, rely on hierarchy like error.codes):
ma.rrd
ma.sql
ls.xml
ls.uddi
mp.snmp
mp.cl
-serviceLocation (required, may be hierarchical too):
abilene
abilene.internet2.ann_arbor
geant
geant.pionier
-implementationLanguage (optional):
java
perl
python
-usedTools (optional)
bwctl,owamp
exist-db
rrdjtool
As far as I remember it was defined on the beginning of the project. Now we have only 4 elements in Lookup Info metadata which are not enough.
Maciej
- Definition of perfSONAR, Eric L. Boyd, 10/09/2006
- Re: [pS-dev] Definition of perfSONAR, Roman Lapacz, 10/10/2006
- Re: [pS-dev] Definition of perfSONAR, Maciej Glowiak, 10/10/2006
- Re: [pS-dev] Definition of perfSONAR, Roman Lapacz, 10/10/2006
Archive powered by MHonArc 2.6.16.