perfsonar development work

[Roman Lapacz <>]

Nina Jeliazkova wrote:
> Hi all,
>
> We are going to introduce support for the new events in PerfsonarUI shortly,
> but it seems there is another issue with filtering.
>
> The Interface specification (page 10) says :
>
> The metadata elements can be linked together using metadataIdRefs. If meta1
> and meta2 are two metadata elements for example, they can be linked together
> with the help of a metadataIdRef attribute which is present (a) either in the
> Subject element of meta2 or (b) the metadata element of meta2. Option (a) is
> called filtering and Option (b) is called chaining. Any number of metadata
> elements can be linked together in this fashion. However, the data element,
> which can be seen as the chain terminator in the request, should link to the
> LAST metadata element of such a chain. 
>
> The current experience is that 
>
> 1)if the data element links to the LAST metadata element of a chain, the
> SetupDataRequest does not return data (see attached
> SetupDataRequest-Filter_LastMeta.xml and
> SetupDataResponse-Filter_LastMeta.xml)
>
> 2)if the data element links to the FIRST metadata element of a chain, the
> SetupDataRequest does return some data.  (see attached
> SetupDataRequest-Filter_FirstMeta.xml and
> SetupDataResponse-Filter_FirstMeta.xml). However, this differs from both  the
> behaviour of previous releases and from the specification.
>
> Could you please help? 
>   


Data element should links to filtering metadata.

Roman


> Best regards,
> Nina
>
>
>
>
> Roman Lapacz 
> <>
>  wrote:
>
>   
> > EventType values supported by SQL MA and RRD MA being prepared for the 
> > release 2.0
> >
> > http://ggf.org/ns/nmwg/characteristic/utilization/2.0 (new)
> > http://ggf.org/ns/nmwg/topology/l2/3.0/link/status (new)
> > Path.Status (old)
> > http://schemas.perfsonar.net/tools/admin/echo/2.0 (new)
> > http://ggf.org/ns/nmwg/ops/select/2.0 (new)
> >
> >
> > Roman
> >
> >
> >
> > Nina Jeliazkova wrote:
> >     
> > > Hi All,
> > >
> > > The request Roman suggested is working, but PerfsonarUI does not support
> > >       
> the
>   
> > > new event types at this moment (especially the new select event, as
> > > utilization can be configured in MA.conf) and therefore can not send
> > > appropriate SetupDataRequest messages.
> > >
> > > The old event types apparently are not recognised by the new service.
> > >
> > > Best regards,
> > > Nina
> > >
> > > Szymon Trocha 
> > > <>
> > >  wrote:
> > >
> > >   
> > >       
> > > > Hi Loukik,
> > > >
> > > > Did you manage to fix the problem with the help you received?
> > > >
> > > > Regards,
> > > >     
> > > >         
> > >   
> > >       
>
>   
>   
> ------------------------------------------------------------------------
>
> <nmwg:message id="message1173954329" 
> 	type="SetupDataRequest" 
> 	xmlns:netutil="http://ggf.org/ns/nmwg/characteristic/utilization/2.0/"; 
> 	xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/"; 
> 	xmlns:nmwgt="http://ggf.org/ns/nmwg/topology/2.0/"; 
> 	xmlns:select="http://ggf.org/ns/nmwg/ops/select/2.0/";>
>         
>   <nmwg:metadata id="meta_in">
>     <netutil:subject id="subject_1">
>       <nmwgt:interface>
>         <nmwgt:hostName>test-hostName</nmwgt:hostName>
>         <nmwgt:ifName>test-0</nmwgt:ifName>
>         <nmwgt:ifAddress type="ipv4">10.1.2.3</nmwgt:ifAddress>
>         <nmwgt:direction>in</nmwgt:direction>
>       </nmwgt:interface>
>     </netutil:subject>
>     
> <nmwg:eventType>http://ggf.org/ns/nmwg/characteristic/utilization/2.0</nmwg:eventType>
>   </nmwg:metadata>
>     <nmwg:metadata id="meta2_in">
>     <select:subject id="subject1_2" metadataIdRef="meta_in"/>
>
>     <select:parameters id="param_3">
>       <nmwg:parameter name="startTime">1173349529</nmwg:parameter>
>       <nmwg:parameter name="endTime">1173954329</nmwg:parameter>
>       <nmwg:parameter name="consolidationFunction">AVERAGE</nmwg:parameter>
>       <nmwg:parameter name="resolution">300</nmwg:parameter>
>     </select:parameters>
>     <nmwg:eventType>http://ggf.org/ns/nmwg/ops/select/2.0</nmwg:eventType>
>     
>   </nmwg:metadata>
>   
>   <nmwg:data id="data_in" metadataIdRef="meta2_in"/>
>
>
> </nmwg:message>
>