Hi Markus,
> I thank all the ROCs and sites that tried and succeeded to upgrade in this
> time window, but the overall result was that the average time
> to upgrade was the same as it always had been (~2.3 sites/day).
we have had only 1 time experience on this and it might take few
iterations to gain the real benefit of having scheduled releases.
> p.s. great to hear that your site will scale up by more than a factor of 10.
> What fabric management tools are you planning to use for the WNs?
> Quattor? Kickstart +X? ..?
I'll kickstart the machines + YAIM and local corrections in a /etc/init.d
script that gets deleted at the end of execution. We will also evaluate
cfengine for reconfiguration because of local expertise with that tool.
Thank you for the update.
cheers
alessandra
On Fri, 8 Jul 2005, Markus Schulz wrote:
> Hi Alessandra,
> I understand that it is difficult for you to plan without knowing when the
> release will hit you.
>
> The problem this time was that we couldn't plan because it was not clear
> wether the main new component could be released at all.
> It was not the common waiting for small fixes that then need other fixes
> which each delay the release by 24h.
>
> I have never had a problem announcing that a release will be late and did
> whenever I realized it.
>
> Concerning the 3 weeks to update.
> -----------------------------------------------
>
>
> The 2_6_0 release will come without hard limits in time and allow more
> individual planning.
> The ROCs can, of course, set targets for the RCs in their region for the
> upgrade.
> It is clearly desirable to have the improvements that come with a new release
> available on most of the sites as quickly as possible.
>
> The VOs can handle a mixed version grid via the Freedom of Choice of
> Resources tool and the jdl.
> Since 2.4.0 we have a mechanism to provide recent client libs. in user
> space. These are then available to VOs that are interested
> in using them and we can use this distribution mechanism when needed.
>
> markus
>
>
>
>
> On Jul 8, 2005, at 2:31 PM, 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 *
>> ********************************************
>>
>
--
********************************************
* Dr Alessandra Forti *
* Technical Coordinator - NorthGrid Tier2 *
* http://www.hep.man.ac.uk/u/aforti *
********************************************
|