Skip to Content.
Sympa Menu

perfsonar-dev - Re: [pS-dev] RC3 of Java SQL MA ver. 1.0

Subject: perfsonar development work

List archive

Re: [pS-dev] RC3 of Java SQL MA ver. 1.0


Chronological Thread 
  • From: Martin Swany <>
  • To: "Matthias K. Hamm" <>
  • Cc: Loukik Kudarimoti <>, Roman Lapacz <>, maxim <>, , Jason Zurawski <>, Mark Yampolskiy <>, "Matthias K. Hamm" <>
  • Subject: Re: [pS-dev] RC3 of Java SQL MA ver. 1.0
  • Date: Tue, 6 Feb 2007 07:43:16 -0500

Hi Matthias, All,

- what is the purpose of this field? What goes into it ?
- who is supposed to provide the information and how will the field be populated ? From our experience, most NRENs still have problems to maintain the AdministrativeState field at all.

I completely agree that these are important things
to consider.

If the details are not related to the status (operational or administrative), then
we should have a new eventType. If what you're asking for is a text field to
describe why the state is administratively down (for instance) then details
would be appropriate.
The AdministrativeState field already aims at providing additional details (there are several states which can be used).

This is true, but I can also imagine that there is additional
info that might be useful. We had the same debate regarding
result codes and roughly agreed that "states" are for systems
and "descriptions" are for humans.

Before adding a new field to E2Emon, it should be cleared how this can improve the work of E2ECU and the operation of E2E links.

Another point is that perhaps the suggestion wasn't to
modify E2Emon, but rather the MAs that produce L2
status information. There maybe other clients that
talk to them.

best regards,
martin




Archive powered by MHonArc 2.6.16.

Top of Page