Hi
Isn't this a GDB discussion?? If we have separate "WN requirements" for
all four experiments .... I think there needs to be some
application-driven process for expressing what they want sites to
install on WNs, and this needs to be discussed with sites.
the result is a list of what sites agree to install on WNs, so that the
applications know what missing pieces need to be in their own dists.
I don't want to have to read the "WN requirements doc" for fourteen
separate VOs ...
JT
Henry Nebrensky wrote:
> On Wed, 26 Oct 2005, Graeme Stewart wrote:
>
>>Rolf Rumler wrote:
>>
>>>Le 21 oct. 2005, � 19:35, Rod Walker a �crit :
>>>
>>>>Is there a central place where we can list the Atlas requirements on WN
>>>>software. A few sites choose to strip down the rpm list to what they
>
> ...
>
>>>As others suggested in this thread, it seems that the VO part of the
>>>operations portal (or CIC portal) is a good place. For the moment,
>>>nearly all the staff is on the 4th EGEE conference, so please be
>>>patient, we'll contact you directly on the "what and how" ASAP.
>>
>>This is doubtless the correct place to publish the information, but as a
>>practical measure for sites can we turn that information into a metarpm,
>>e.g., lcg-UI-atlas.
>>
>>If we put this into the apt repository then the YAIM setup scripts can
>>ensure that each WN has the right packages for supported VOs - and that
>>list can be changed with an updated rpm if necessary.
>
>
> Should Atlas be allowed to modify "LCG" RPMs?
>
> Anyway, the list of dependencies shouldn't be changing at all often. What
> about publishing the list from the CIC in a machine-readable form and
> having YAIM look at that - at least then there's only one such list...
>
> Once said packages have been installed, APT should be able to keep them
> updated...
>
> Henry
>
|