perfsonar development work

["Matthias K. Hamm" <>]

Hi Nicolas,

thanks to your hint. I opened a bugzilla bug (#184, 
https://bugzilla.perfsonar.net/show_bug.cgi?id=184) to start the schema 
change.

Cheers,

M&M

Nicolas Simar schrieb:
> Hi Matthias
>
> Matthias K. Hamm wrote:
> > Hi Nicolas, all
> >
> > we had a chance to discuss with Loukik how to proceed with this issue 
> > (see below) and define next steps (although we have to clarify 
> > remaining technical details).
> >
> > However, this raises the question how to proceed with the needed 
> > change of the NMWG schema:
> >
> > Currently, the E2Emon visualization tool uses the NMWG 
> > request/response schema as agreed with Internet2.
> >
> > Are there procedures for requesting and coodinatimg schema changes in 
> > the perfSONAR community ?
>
> perfSONAR wiki > Developers Information > FAQ > How do I extented or 
> modify the schema.
> http://anonsvn.internet2.edu/svn/nmwg/trunk/nmwg/schema/README.txt
>
> Does it covers your questions?
>
> Nicolas
>
> > Cheers,
> >
> > M&M
> >
> > Loukik Kudarimoti schrieb:
> >
> > > Roman Lapacz wrote:
> > >
> > > > Jeff W. Boote wrote:
> > > >
> > > > >  wrote:
> > > > >
> > > > > > If there is no data in the database the response will have only 
> > > > > > one datum element with 'UNKNOWN' values.
> > > > > >
> > > > > > example:
> > > > > >
> > > > > >
> > > > > >     <nmwg:data id="7f89" metadataIdRef="md-link-PSNC-2-DFN-MUE-004">
> > > > > >         <ifevt:datum 
> > > > > > xmlns:ifevt="http://ggf.org/ns/nmwg/event/status/base/2.0/";>
> > > > > >             <ifevt:stateAdmin>UNKNOWN</ifevt:stateAdmin>
> > > > > >             <ifevt:stateOper>UNKNOWN</ifevt:stateOper>
> > > > > >         </ifevt:datum>
> > > > > >     </nmwg:data>
> > > > >
> > > > >
> > > > > Roman - anyone else that was part of the decision to add this...
> > > > >
> > > > > Why is this better than no datum at all?
> > > > >
> > > > > My concern with adding this, is that it is different from the 
> > > > > behavior of other services now. The RRD-MA for example, returns no 
> > > > > datum if you ask for data outside of the time-range of data it holds.
> > > > >
> > > > > We want a generic visualization client to have only a very small 
> > > > > amount of work to add in each new data type. Therefore, we should 
> > > > > have as similar access semantics as possible for all MA's.
> > > > >
> > > > > If there is a good reason for it in this service, then it begs the 
> > > > > question: Should other services be creating the equivalent of a 
> > > > > 'missing-values' datum in the case of an empty result?
> > > >
> > > >
> > > > Hi Jeff,
> > > >
> > > > I had similar concerns :) but I was asked by Loukik to do it 
> > > > (before the change there was no datum in the response). If I 
> > > > understood correctly, the visualization application made by JRA4 
> > > > guys requires this approach. I'm sure Loukik can say more.
> > >
> > >
> > > As I mentioned to Roman, I certainly don't have a strong opinion on 
> > > this topic. I don't see how one is better than the other. It is true 
> > > that in the current scenario the JRA4 visualization tool fails to 
> > > show that there is no data. Instead it 'crashes' for a particular 
> > > domain by showing long and 'not-so-easy-to-read' error messages.
> > >
> > > One could argue that the change should be made on the JRA4 side and 
> > > I would also agree to that as well. I think defining a generic datum 
> > > element (and not really a result code) for such situations would be 
> > > useful. It will be better than a result code because the result code 
> > > structure currently does not pass back any metadata (related to the 
> > > link/network element for example). So, with a datum element which 
> > > means 'no data' you could say, this particular link (metadata) does 
> > > not have any data.
> > >
> > >
> > >
> > >
> > >
> > >
> > > > Roman


--

Matthias Hamm

------------------------------------------------
Leibniz-Rechenzentrum / Leibniz Computing Centre
Raum I.2.107
Boltzmannstrasse 1, 85748 Garching, Germany
Telefon: +49 89 35831-8832
Fax:     +49 89 35831-9700
E-Mail:  

-------------------------------------------------