Hi Jeremy,
I'm not against using rpms produced by DAG, it seems like a sensible
solution to save effort and ensure more timely updates, but I have a
couple of concerns that I think could be pretty easily addressed:
1) this should not mean that these rpms are outside gLite update
validation + testing procedures
2) will the recipe ("a recipe will be provided for preventing updates to
the OS being taken from the repository") be for a specific installation
+ update mechanism? So for example will I be on my own if I use the tar
ball or redhat's up2date rather than yum?
I think the simplest solution to both these is to keep a "contrib"
repository, into which the necessary/recommended subset of RPMs from DAG
and their updates are replicated. This gives the opportunity to make
them available when they have been validated with gLite. It would give a
chance to spot non-backward compatible updates before everyone installs
them without realising.
Cheers,
Simon
Coles, J (Jeremy) wrote:
> Dear All
>
>
>
> Please can you let us (UKI ROC) know your thoughts on use of the DAG
> repository as suggested in the EGEE mail below?
>
>
>
> Many thanks,
>
> Jeremy
>
>
>
>
>
>
>
> -----Original Message-----
> *From:* Nicholas Thackray [mailto:[log in to unmask]]
> *Sent:* 08 August 2007 14:56
> *To:* project-egee-roc-managers (EGEE ROC managers and alternates)
> *Cc:* Oliver Keeble
> *Subject:* Action 51 from Grid Ops Meeting: "using the externally
> maintained 'DAG' repository for external dependencies of the middleware"
>
>
>
> Dear ROCs
>
>
>
>
>
> As discussed at the grid operations meeting on Monday, please can you
> contact your sites to find out if they foresee any problems with using
> the DAG, third-party repository for some of the external dependencies of
> the gLite distribution. The benefit of this is that we will use a
> repository which is fully maintained and therefore fully up to date with
> all security patches, etc. At the moment, the repository in which these
> external packages are kept is maintained on a best efforts basis and
> there have been several instances in the past where sites have companied
> of the repository being out of date.
>
>
>
> If it is agreed that the DAG repository will be used, then a recipe will
> be provided for preventing updates to the OS being taken from the
> repository.
>
>
>
> Please note that, as agreed at the grid operations meeting, all ROCs
> have until the 20^th August to raise any issues against this proposal.
> If issues are not raised by that date, then it will be assumed that the
> ROC (and thus it’s sites) agrees with the proposal to use the DAG
> repository.
>
>
>
>
>
> Many thanks and best regards,
>
> Nick
>
>
>
>
>
> /CERN office:/ 28 R-002
>
> /Tel. / SMS:/ +41.76.487.5528 (or 165528 from CERN)
>
>
>
>
>
|