perfsonar development work

[Guilherme Fernandes <>]

Maciej Glowiak wrote:

> Guilherme Fernandes wrote:
>
> > Hi all,
> >
> > I've just submitted a generic LSRegistrationComponent so that all 
> > services can use the same. I changed a few parameters to reflect 
> > generic setup:
> >
> > - The component now uses the file specified by the parameter 
> > 'service.ls.registration_file' (instead of 'service.ma.conf_file') in 
> > service.properties file (This is the xml that is sent as registration 
> > information to the LS).
> > - It now uses the following parameters in service.properties for 
> > configuration: component.ls-registrator.interval and 
> > component.ls-registrator.scheduler_component  (instead of 
> > component.ma-registrator.*)
> > - In component.properties file, the registrator variable should now 
> > point to 
> > org.perfsonar.service.commons.registration.LSRegistrationComponent .
> >
> > One thing that came up when doing this was what values to set to 
> > default and minimal interval. I talked to Jeff about it and he asked 
> > me to put it up for discussion here. For now I changed the default 
> > interval to 30 minutes and minimal interval to 5 minutes (10s and 
> > 100ms was crazy).
> >
> > Feel free to change the naming of the parameters or anything else 
> > (like the package of the class), I just tried to speed this up.
> >
> > Guilherme
>
>
> Hi Guilherme,

Hi Maciej

> Thanks for your work. I didn't finished the idea of generic 
> LSRegistrationComponent because of some reasons.
>
> I have one concern. In previous implementation the component was quite 
> generic, because it base on LSRegistrator anyway.
> The only registration code is in runAction(), the other part is just 
> settings.
>
> The previous implementation was for specific service and the name of 
> components was for instance ma-registrator. Now it's ls-registrator, 
> but what if we had more than one service? I can imagine the situation 
> when one MA may register to two different LSes with two different files.

I guess this could be done defining multiple LS in 'service.r.ls_url' 
(separated by commas for example) and the corresponding files in 
'service.ls.registration_file' (also separated by commas), building a 
set and making the component register for every entry in the set. What 
do you think?

> Anyway, I think your changes go in right direction.
>
> Best regards
>
> Maciej