John
I think (and hope) that this was a special case (though a recent review
suggests it is not an isolated case). The initial delay was due to the
2.3.0 upgrade and then the SL3 move. It is a pity that the security
incident took RHUL out, especially for so long, as their resources were
being well used. There was another issue with manpower. All of this
shows up in the London Tier-2 quarterly report so we can discuss it at
the next Tier-2 board.
Generally speaking, increased emphasis on availability of resources
should mean that sites are not down for so long (and we will certainly
be under pressure to encourage them not to be!). There is now more of a
commitment from the LCG deployment team to meet release dates.
On a related matter, at a recent weekly operations meeting the topic of
site downtime being unreasonable was discussed but no conclusion made on
how to deal with the problem.
Jeremy
-----Original Message-----
From: Testbed Support for GridPP member institutes
[mailto:[log in to unmask]] On Behalf Of Simon George
Sent: 27 April 2005 09:03
To: [log in to unmask]
Subject: Re: Good progress on 2.4.0 upgrade
Hi John,
thanks for your comments. I am learning that. I was taken in by the
promise of fixed release dates! But I did consult Owen and Jeremy and
they agreed with my plan to wait at the time. We did a fresh
installation, not an upgrade, as part of the procedure to recover from
the security incident, so in this case the practicalities of jumping 1,2
or N releases were not an issue. One of the highest considerations was
how much time we could spend working on it. I made the decision that we
did not have time to do and install and an upgrade in the space of
approx one month. In other words, if we installed 2.3.0, we would have
been late with 2.4.0. As it is I think we have just made it on time for
2.4.0.
Cheers,
Simon
Gordon, JC (John) wrote:
> Simon, I think you should try to avoid the temptation to put off
> upgrading to 'wait for the next release'. There are two reasons for
> this. Firstly we can't always rely on the next release arriving on
time.
> This leaves you out of date for longer than you thought. The other
> reason is that empirically jumping 2 releases doesn't always work.
>
> Regards,
>
> John
>
>
>>-----Original Message-----
>>From: Testbed Support for GridPP member institutes
>>[mailto:[log in to unmask]] On Behalf Of Simon George
>>Sent: 25 April 2005 16:00
>>To: [log in to unmask]
>>Subject: Re: Good progress on 2.4.0 upgrade
>>
>
>
>>It was prolonged because, due to limited manpower, we decided in March
>
> to
>
>>wait for 2.4.0 rather than install 2.3.0, with the prospect of
>
> upgrading
>
>>in a few weeks' time.
|