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: Loukik Kudarimoti <>
  • To: Martin Swany <>
  • Cc: "Matthias K. Hamm" <>, Roman Lapacz <>, maxim <>, , Jason Zurawski <>, Mark Yampolskiy <>, "Matthias K. Hamm" <>
  • Subject: Re: [pS-dev] RC3 of Java SQL MA ver. 1.0
  • Date: Tue, 06 Feb 2007 12:52:44 +0000

Hi All,

Martin Swany wrote:
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.
I agree. This field could be made optional i.e., the MPs and the MAs do not *have to* provide this info. But if they do, there may be other clients or even the deployers themselves (as in the case of Maxim) who might want to make use of it for some other purposes.

When the database schema for path status was designed and used as default within the SQL MA, the intention behind the 'comments' column was to allow any extra information related to the path status change to be documented. As Martin says, this section is for humans. It looks like Maxim wants to make use of this column and update it via the protocol. So, I think we could have an additional but optional field in the datum saying 'details' or 'comments'.

Loukik.

best regards,
martin





Archive powered by MHonArc 2.6.16.

Top of Page