Skip to Content.
Sympa Menu

perfsonar-dev - Re: [pS-dev] Re: Self-test triggering/response messages pointer

Subject: perfsonar development work

List archive

Re: [pS-dev] Re: Self-test triggering/response messages pointer


Chronological Thread 
  • From: Jason Zurawski <>
  • To: Guilherme Fernandes <>
  • Cc: Michael Bischoff <>, Verena Venus <>, "Luchesar V. ILIEV" <>, Aaron Brown <>, Roman Lapacz <>, Szymon Trocha <>, Maciej Glowiak <>, Stijn Melis <>, Cándido Rodríguez Montes <>, Nicolas Simar <>, Domenico Vicinanza <>, perfSONAR developers <>, , "Jeff W. Boote" <>
  • Subject: Re: [pS-dev] Re: Self-test triggering/response messages pointer
  • Date: Tue, 24 Jun 2008 11:39:38 +0200
  • Openpgp: id=B94D59A6; url=http://people.internet2.edu/~zurawski/key.txt
  • Organization: Internet2

All;


sends back conflicting messages as to the results of the test (why are there 2 errors and a warning, it appears that again we have run 3 separate tests here...). It also is imposing additional result semantics to the datum items, if this was an 'error' or a 'waring' the eventType should say so. If this proposal is being offered to extend syslog information mining it is being done in the wrong manner, there would need to be 3 sub-results (note the altered eventTypes and single datum elements) as per the original example where the selftest itself was code for several tests:

I'm also noticing that the datum element can't be used that way:

<nmwgr:datum *value="warning"*>*Could not read configuration falling back to defaults*</nmwgr:datum>

the value attribute is being set two times with different meanings. The schema allows any attribute on datum (i.e. change value to type), but as Jason is pointing, the type of information should be defined by the eventType.

Thanks for catching that, you are absolutely right (I should have proofread my example better):

<nmwg:message id="message1213971959" type="EchoResponse" xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/"; xmlns:result="http://ggf.org/ns/nmwg/result/2.0/";>
<nmwg:metadata id="meta">
<nmwg:eventType>
http://schemas.perfsonar.net/tools/admin/selftest/MP/BWCTL/well_configured/WARNING/1.0
</nmwg:eventType>
</nmwg:metadata>
<nmwg:data id="causes" metadataIdRef="meta">
<nmwgr:datum>Could not read configuration falling back to defaults</nmwgr:datum>
</nmwg:data>
</nmwg:message>

<nmwg:message id="message1213971959" type="EchoResponse" xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/"; xmlns:result="http://ggf.org/ns/nmwg/result/2.0/";>
<nmwg:metadata id="meta">
<nmwg:eventType>
http://schemas.perfsonar.net/tools/admin/selftest/MP/BWCTL/well_configured/ERROR/1.0
</nmwg:eventType>
</nmwg:metadata>
<nmwg:data id="causes" metadataIdRef="meta">
<nmwgr:datum>bwctld executable not found!</nmwgr:datum>
</nmwg:data>
</nmwg:message>

<nmwg:message id="message1213971959" type="EchoResponse" xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/"; xmlns:result="http://ggf.org/ns/nmwg/result/2.0/";>
<nmwg:metadata id="meta">
<nmwg:eventType>
http://schemas.perfsonar.net/tools/admin/selftest/MP/BWCTL/well_configured/ERROR/1.0
</nmwg:eventType>
</nmwg:metadata>
<nmwg:data id="causes" metadataIdRef="meta">
<nmwgr:datum>bwctld not running!</nmwgr:datum>
</nmwg:data>
</nmwg:message>

-jason



Archive powered by MHonArc 2.6.16.

Top of Page