Sorry about the late reply; random burblings follow:
On Tue, 26 May 2009, Douglas McNab wrote:
> * NGS would prefer to publish tags with ngs-uee-<softwarename>-<version> this is slightly different from the EGEE
> convention of vo-<softwarename>-<version> . Does this matter?
No and yes: No, it's all just a plain string anyway.
Yes: (to me) the vo-<VO>-... convention implies a tag managed
by the VO through lcg-Manage-VOtag, so if, as a user, I
found some problem I would raise a ticket against the VO, not
the site. *Which way* it matters would thus depend on how the
publishing is to be managed at a higher level.
> * What is the best way to create these entries on GridPP sites? Since the NGS GIP plugin is not compatible with EGEE.
No idea, but it probably needs sw installation to be settled first.
> * NGS envisages a large number of small VOs - per site, per interest group which will probably not have Grid IT experts.
> Will sites be willing to manage software installs?
Obviously it will depend on the site admin resources :). SW that's shipped
with the OS (e.g. R, octave) is easy and might even be installed already;
as it's available system-wide, it should probably be tagged directly as
<softwarename>-<version> rather than either prefix above.
The EGEE remote SW install can boil down to asking VOMS for the privilege
and then submitting a script that unpacks a tarball in the right place -
Grid expertise for the install is possibly less important than general SW
expertise for structuring it so that it can easily be used once in place.
If sites with finite resources are to manage software installs, they will
concentrate on particular VOs - i.e. you would probably have each
site supporting only a subset of VOs. That's not something I see as a
problem, but it is counter to the current tendency to support everything
everywhere.
> * There was mention that Brunel already had an application in a biomed VO that was of interest to NGS and indeed installed
> by locals at some sites. Could this application suite be shared across VOs - biomed and some NGS VO on a GridPP site ?
I've not checked the specific file permissions, but I can imagine an
experienced NGS VO user being able to run the software. However, even
wearing a sysadmin hat I don't know what the software does (i.e. stock or
custom), licensing issues, or when it will be updated or even removed -
it's installed and managed by the biomed VO. Having the site install it
would be one route to sharing it (we don't have the time :( ), but I don't
know of any technical reasons why two VOs couldn't co-operate to share
the use of a software package (only one can install/remove it) - i.e. this
could be agreed directly between biomed and said NGS VO.
That implies another solution to the question above: centrally the NGS
could use its generic VO to remotely install common software used by its
user VOs. Users would need some boilerplate in their jobs to pick that up,
but I think they'll have something similar there anyway.
Thanks
Henry
--
Dr. Henry Nebrensky [log in to unmask]
http://people.brunel.ac.uk/~eesrjjn
"The opossum is a very sophisticated animal.
It doesn't even get up until 5 or 6 p.m."
|