Yes, JRA1 are committd to producing deployment modules for all THEIR
components, but gLite isn't a full middleware stack. Well perhaps with
the new renaming it is but I doubt that JRA1 are committed to supporting
the new enlarged gLite.
> -----Original Message-----
> From: Testbed Support for GridPP member institutes
> [mailto:[log in to unmask]] On Behalf Of Burke, S (Stephen)
> Sent: 05 November 2005 11:26
> To: [log in to unmask]
> Subject: Re: installation tools situation
>
> Testbed Support for GridPP member institutes
> > [mailto:[log in to unmask]] On Behalf Of Gordon, JC (John)
> said:
> > What were the actions? Did anyone commit to integrating all the
> > non-glite components into this framework? This is presumably an
> > ongoing task as other tools develop in parallel.
>
> I think that's part of the point: jra1 are committed to
> producing deployment modules for all the components, whereas
> Oliver doesn't have time to re-code the python scripts in
> bash. However, in principle that could presumably be done
> elsewhere in the community.
>
> In the end it seems to me that the sysadmins are the
> clients here and the system adopted should be one that they
> are happy with. However, it should be an informed choice; so
> far the admins on the testbed and PPS haven't raised any
> fundamental objections to the new system, just some issues
> about things like how the xml files are managed which have
> been addressed to some extent. Also there are some potential
> benefits from xml which we don't actually have so far, e.g.
> editing with a GUI tool.
>
> Stephen
>
|