Skip to Content.
Sympa Menu

perfsonar-dev - Naming scheme for services

Subject: perfsonar development work

List archive

Naming scheme for services


Chronological Thread 
  • From: Szymon Trocha <>
  • To:
  • Subject: Naming scheme for services
  • Date: Mon, 20 Nov 2006 15:49:01 +0100

Maciej Glowiak wrote:
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

Approaching the next release we can go back to this discussion about naming schema which Maciej initiated. Any other opinions or proposals?

Regards,
--
Szymon Trocha

Poznan Supercomputing & Ntw. Center ::: NETWORK OPERATION CENTER
Tel. (+48 61) 8582022
http://noc.man.poznan.pl ::: http://noc.pionier.gov.pl




Archive powered by MHonArc 2.6.16.

Top of Page