perfsonar development work

[Roman Lapacz <>]

Eric L. Boyd wrote:
> The strategy is to pick "a" or "b" as appropriate for the target.
>
> Most of the work is interoperability testing anyway, and that's 
> implied by both.

I agree. Having bundle script might be very useful for end users but I 
would also allow defining abstract sets of services which address 
specific needs of end users (e.g. "pS setup for LHC", "pS setup for 
videoconferencing", etc.). End users would have guides what (with exact 
version numbers) and how to install. Even experienced end users could 
create their own sets/guides and share with others (the idea is we 
provide services/components, they build the final system/setup).


Roman


> --Eric
>
> Loukik Kudarimoti wrote:
> > Jeff W. Boote wrote:
> > > Hi Loukik,
> > >
> > > Loukik Kudarimoti wrote:
> > > > Hi Eric,
> > > >
> > > > I would like to clearly understand your definition of a bundle.
> > > >
> > > > (a) a simple page which groups together a list of Web service 
> > > > products to be used and gives the location of where these products 
> > > > are available?
> > > > (b) Bunch of products packaged together using a purpose built 
> > > > software package or installer?
> > > >
> > > > Currently, perfSONAR-bundle-2.0 is of type (b).
> > >
> > > Couldn't it be both?
> > >
> > > Can you explain why it matters?
> >
> > I was asking because I wanted myself (and the rest of us) to be on 
> > the same page with regards to use of this word.
> > The effort required to produce bundles of type (b) is clearly greater 
> > than the effort required for (a). So, its important to know what the 
> > strategy is.
> >
> > Loukik.
> >
> > > jeff