Hi Jeff,
I know it's hard, I never said the opposite. It's hard for me as well to
upgrade within 3 weeks 1000 nodes without planning and differently from
the release delivery/publishing/release I get negative points for not
doing it since it is considered a critical test.
cheers
alessandra
On Fri, 8 Jul 2005, Jeff Templon wrote:
> Hi Alessandra et al,
>
> I agree with most of what you say. But it reminds me of grid scheduling ...
> if you insist on up-to-date information, you basically kill the system with
> queries and communication, and by the time you have queried all the relevant
> pieces of the system, the information from the first party queried is already
> out of date.
>
> Working on the preproduction system now, I understand even better why
> planning is tough. There is quite a step between "managed to build RPM from
> developer's release" and "software installs and functions correctly in
> production environment".
>
> My 0,02 cents.
>
> J "back to blahpd" T
>
>
> Alessandra Forti // EOJ wrote:
>> Hi Markus,
>>
>> since LCG-2_5_0 was for sites participating to SC3 I didn't read the
>> release note in detail.
>>
>> As a general comment, although I perfectly understand the pressure you are
>> under, I think that vagueness and mixed information about releases doesn't
>> help. I'd rather have clear statements for each release even if they say
>> that the release is late and the reason why it is late. I think that clear
>> communication is important to maintain my end of the bargain updating
>> sites within 3 weeks from LCG release.
>>
>> In about 2 months I'll have to deal with 1000 nodes (not ~80) which
>> clearly need planning for the upgrades. I hope you understand my position.
>>
>> cheers
>> alessandra
>>
>> On Fri, 8 Jul 2005, Markus Schulz wrote:
>>
>>> Hi,
>>> in the release note of LCG-2_5_0 I have stated that 2_6 will come early
>>> July.
>>>
>>> This statement was deliberately vague because at that time the state of
>>> the some of the components meant to go into the release was less than
>>> clear.
>>>
>>> Our aim is to release at the 15th to the 3 ROCs that volunteered for
>>> deployment testing and then with their feedback release at the
>>> 20th. The ROCs will then plan for their region the schedule taking into
>>> account the regional users and sites.
>>>
>>> markus
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Jul 8, 2005, at 1:27 PM, Alessandra Forti // EOJ wrote:
>>>
>>>> Hi,
>>>>
>>>> can anyone from the deployment team at CERN update us on the situation
>>>> of LCG-2_6_0?
>>>>
>>>> I need to schedule manpower and agree with some of the experiments
>>>> when to do the upgrade. The release was due this week but there is no
>>>> sign of it and I haven't seen any email that explains why it has been
>>>> delayed and when it is foreseen for and what we should expect from it.
>>>> It would be very helpful to know. An EGEE broadcast would be
>>>> apreciated.
>>>>
>>>> thanks
>>>>
>>>> cheers
>>>> alessandra
>>>>
>>>> --
>>>> ********************************************
>>>> * Dr Alessandra Forti *
>>>> * Technical Coordinator - NorthGrid Tier2 *
>>>> * http://www.hep.man.ac.uk/u/aforti *
>>>> ********************************************
>>>>
>>>
>>
>
--
********************************************
* Dr Alessandra Forti *
* Technical Coordinator - NorthGrid Tier2 *
* http://www.hep.man.ac.uk/u/aforti *
********************************************
|
