perfsonar development work

[Jason Zurawski <>]

Michael & All;

> Hello all,
>
> I have not taken notice of earlier parts of the conversation so forgive me if 
> I'm off base.
>
> "why is the MA.conf file still necessary?"
>
> MA.conf was retained for couple of reasons. (it has been discussed before 
> either internally
> or on the dev list I can't recall. Some conclusions where made I'll list them 
> for as well as
> I remember)
>
> Stripping MA.conf method from psui in one go would be to abrupt on our users. 
> While psui is
> gLS capable, we would want to allow some period where the functionally can be 
> matured as well
> as deployments increase.


I think this is a great goal, but to support getting there we should not 
be encouraging the addition of new MAs to the 'distributed' MA.conf.

If Nina is seeing performance or usability issues, then we need to 
improve group communication to get these fixed.  I have also not 
received any reports (via the bug tracker or through email - personal or 
list) that has indicated this solution is incapable, but if there are 
problems I will address them.

-jason


> MA.conf still serves use, albeit in a somewhat evolved way, it would be 
> useful to allow
> users/(small)usergroups to have access to their personal list of 
> favourite/frequently used
> services. This could even evolve in to a locally hosted cached list of gls 
> entries.
>
> Dynamically obtained service addresses should for the most part replace more 
> 'statically'
> MA.conf. The adoption rate here should be a direct indication as to the 
> quality of the
> provided functionality. Additional stimulation above the added ease of use 
> that dynamically
> obtaining service addresses brings, would only and frustrate the user. 
> Increasing awareness
> is more the direction I would opt for. So don't say 'use this', but rather 
> 'did you know..'
> and gather feedback - improve the functionally - which should improve 
> adoption rate.
>
> As I said I'm unaware of earlier messages - so I'll just ask: was there a 
> particular reason
> gls didn't fit the requirements?
>
> - Michael
>
>
> > Nina;
> >
> >
> > [Moving to pS-Dev]
> >
> >
> > > Vicky,
> > >
> > >
> > > You could edit your own local configuration and load it in perfsonarUI.
> > > You could install your own copy of perfsonarUI web start  (all the
> > > configs/data is under jnlp directory in SVN)
> > >
> > > To edit the global configuration of perfsonarUI, I need to have the
> > > approval of current GEANT / MDM community, who is using the current setup.
> > >
> > > Does everybody agree it is OK to add Vicky' MA service to the
> > > perfsonarUI config ?
> >
> > If perfSONAR-UI is gLS capable, why is the MA.conf file still necessary?
> > I would much rather we start encouraging dynamic operations of all tools
> > instead of relying on the wiki and the static configurations.
> >
> > We really know nothing about where Vicky is coming from, or how long
> > this service intends to be active.  For these reasons I believe we must start 
> > practicing some
> > of what we preach with regards to dynamic service location.
> >
> > -jason
> >
> >
> >
> > > Best regards,
> > > Nina
> > >
> > >
> > > hsuan напи�а:
> > > > Dear Jason :
> > > >
> > > >
> > > > As roman as said , how can I add my geant2-java-rrdma to psUI ?
> > > >
> > > >
> > > > Thank you for your help !
> > > >
> > > >
> > > >
> > > >
> > > > Best regards,
> > > >
> > > >
> > > > Vicky