perfsonar development work

[Guilherme Fernandes <>]

Jason Zurawski wrote:
> Guilherme;
>
> > Hi Guys,
> >
> > So what was the decision on this for 3.1? CL-MP needs to register 
> > possibly 6 eventTypes that it serves. Currently I'm defining one 
> > metadata for each eventType, but this is not a clean solution and I'm 
> > not sure the hLS/gLS will understand this right?
>
>
> The hLS should be the only thing that summarizes what a service will 
> register (gLS's just sumamrize what an hLS sends along).  The 
> perfSONAR-PS instances currently recognize multiple eventTypes, 
> multiple 'supportedEventType' parameters, or several metadata blocks 
> as you are sending.  If you would like a test instance please let me 
> know.
Just tested it and it works fine. If anyone needs something similar, 
this is what CL-MP has on the LS registration file:

<nmwg:store xmlns:nmwg="http://ggf.org/ns/nmwg/base/2.0/";>
 <nmwg:metadata id="metadataping">
   <nmwg:eventType>http://ggf.org/ns/nmwg/tools/ping/2.0</nmwg:eventType>
 </nmwg:metadata>
 <nmwg:metadata id="metadataowamp">
   <nmwg:eventType>http://ggf.org/ns/nmwg/tools/owamp/2.0</nmwg:eventType>
 </nmwg:metadata>
 <nmwg:metadata id="metadataowampsum">
   
<nmwg:eventType>http://ggf.org/ns/nmwg/tools/owamp/summary/2.0</nmwg:eventType>
 </nmwg:metadata>
 <nmwg:metadata id="metadatabwctl">
   <nmwg:eventType>http://ggf.org/ns/nmwg/tools/bwctl/2.0</nmwg:eventType>
 </nmwg:metadata>
 <nmwg:metadata id="metadatatraceroute">
   
<nmwg:eventType>http://ggf.org/ns/nmwg/tools/traceroute/2.0</nmwg:eventType>
 </nmwg:metadata>
</nmwg:store>

Guilherme
> -jason
>
>
>
> > Regards,
> > Guilherme
> >
> > Roman Lapacz wrote:
> > > Guilherme Fernandes wrote:
> > > > Michael Bischoff wrote:
> > > > > Hello all,
> > > > >
> > > > >   
> > > > Hi,
> > > > > We have issues with registering to the LS.
> > > > >
> > > > > We use a InformationContextServiceContent and
> > > > > InformationContextServiceContent#getServiceContent returns an 
> > > > > array with one element: a
> > > > > String containing
> > > > >
> > > > > <nmwg:metadata ...>
> > > > >  <..:subject>
> > > > >   ...
> > > > >  </..:subject>
> > > > >  <eventType> .. </eventType>
> > > > >  <eventType> .. </eventType>
> > > > >  <eventType> .. </eventType>
> > > > > </nmwg:metadata>
> > > > >
> > > > > I checked it in the debugger that it returns the right string.
> > > > >
> > > > > the arrays gets passed around and is called by
> > > > > LSRegisterRequestGenerator#generateRequestMessage() where it is 
> > > > > pushed into nmwg classes in
> > > > > some awkward way and the information is lost. Looking at the 
> > > > > metadata nmwg class it seems it
> > > > > can only hold one eventType. (but not one shows up unless I put it 
> > > > > in a speparate metadata
> > > > > block.)
> > > > >
> > > > > Or format is similar(minus parameters) to example one here:
> > > > > http://wiki.perfsonar.net/jra1-wiki/index.php/LS_Registration_messages 
> > > > >
> > > > > (Which is the current spec right now, right?)
> > > > >
> > > > > Since I hardly think we are the only with a service that supports 
> > > > > more then one eventype and
> > > > > I wonder how other services got this to work, anyone who can 
> > > > > elaborate on this?
> > > > >
> > > > >   
> > > > Multiple eventTypes are not supported in the current base.AFAIK, 
> > > > MA's, which I think that right now are the only one's registering 
> > > > multiple eventTypes, use the supportedEventType parameter to 
> > > > register multiple eventType.
> > >
> > > Hi
> > >
> > > Unfortunately, the nmwg java implementation does not support 
> > > multiple eventType. So Java RRD MA and SQL MA can have only on 
> > > eventType in a metadata block. In future (after 3.1) we should 
> > > change it.
> > >
> > > (supportedEventType parameter is an obsolete solution; in fact it 
> > > didn't fix this problem)
> > >
> > > Roman
> > >
> > > > regards,
> > > > Guilherme
> > > > > regards,
> > > > >
> > > > > Michael