Alessandra Forti wrote:
> Michel complained as well about these updates. So I gather that QWG has
> had its fair share of problems.
Yes we suffer from shortcomings in the release process too and will
happily add our voices to the chorus demanding an improved process. The
point is that we expect these shortcomings, the extra layer of filtering
is there by default and all QWG users benefit automatically from it,
rather than each site independently encountering and resolving the same
set of problems.
I'm not a zealot -- I know that the UK sites are managed very efficiently.
I just wanted to share our experience with Quattor which has improved
exponentially in the last couple of years (mainly due to Michel's hard
work). In the past I wouldn't have recommended it for a single site: now I
would, and all the more so for a distributed T2.
Stephen
> On Mon, 21 May 2007, Stephen Childs wrote:
>
>> In the quattor world, we evaluate the contents of each update and don't
>> include disruptive changes by default -- they must be explicitly requested by
>> the admin in their configuration. In this way, necessary changes like VOMS
>> cert get included by default but you don't break your DPM unless you really
>> want to. The QWG distribution also allows easy selection of which update level
>> you want to go to by just setting a variable.
>>
>> All sites using the QWG distribution benefit from this filtering while
>> retaining full autonomy if required. It's perhaps unfortunate that this level
>> of filtering is required for core middleware updates, but that's the reality
>> and at least this way we ensure that the silly problems are caught at a
>> central point.
>>
>> See https://trac.lal.in2p3.fr/LCGQWG/wiki/ReleaseNotes/gLite-3.0 for more
>> info.
>>
>> Just thought I'd slip a bit of Quattor promotion into the discussion! We feel
>> that it really is the best way to save duplication of effort at sites with
>> similar configurations (it has proved particularly effective for managing
>> distributed Tier 2s).
>>
>> Stephen
>> --
>> Dr. Stephen Childs,
>> Research Fellow, EGEE Project, phone: +353-1-8961797
>> Computer Architecture Group, email: Stephen.Childs @ cs.tcd.ie
>> Trinity College Dublin, Ireland web: http://www.cs.tcd.ie/Stephen.Childs
>>
>
> Alessandra Forti
> NorthGrid Technical Coordinator
> University of Manchester
--
Dr. Stephen Childs,
Research Fellow, EGEE Project, phone: +353-1-8961797
Computer Architecture Group, email: Stephen.Childs @ cs.tcd.ie
Trinity College Dublin, Ireland web: http://www.cs.tcd.ie/Stephen.Childs
|