perfsonar development work

[Guilherme Fernandes <>]

Jason Zurawski wrote:
> Michael;
Hi,
> > Verena and me where discussing the one here:
> > http://wiki.perfsonar.net/jra1-wiki/index.php/Talk:Service_Self-testing
> >
> > I actually mentioned that it can return more then one result in the 
> > form of causes, although
> > that wasn't clear from the examples. (I added more examples now.)
> >
> > So both (new) proposals can return more then one return value.
>
>
> Your example from the talk page is skirting the key issue we addressed 
> last week that was the entire reason for the alternate proposal: 
> multiple datum elements confuse the semantics of the result.  Your 
> example:
>
>
>  <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/failure/1.0</nmwg:eventType> 
>
>    </nmwg:metadata>
>    <nmwg:data id="causes" metadataIdRef="meta">
>      <nmwg:datum value="warning">Could not read configuration falling 
> back to defaults</nmwg:datum>
>      <nmwg:datum value="error">bwctld executable not found!</nmwg:datum>
>      <nmwg:datum value="error">bwctld not running!</nmwg:datum>
>    </nmwg:data>
>  </nmwg:message>
>
>
> 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.

Guilherme
>  <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 value="warning">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 value="error">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 value="error">bwctld not running!</nmwgr:datum>
>    </nmwg:data>
>  </nmwg:message>
>
>
> -jason