Dear All
As you are no doubt aware LCG 2.6.0 was released later than anticipated
partly due to the inclusion of some critical components (without which
the release would have been pointless) and also due to the need to fix
many problems after extensive regional testing. Nevertheless, it appears
that another problem had to be fixed after the official release a few
days ago.
With this release there has been a change in policy regarding updates.
For this release each Regional Operations Centre is to set the upgrade
period locally. As there is likely to be a return to the 3 week period,
for the UKI region we want to maintain that aim for this release.
Therefore ALL sites are requested to upgrade to 2.6.0 by Wednesday 24th
August. It is understood that some sites require special ports of the
middleware and may not be able to meet this request. Please could you
let me (and your Tier-2 coordinator) know directly if your site is not
likely to upgrade in this time frame.
There are many good reasons to stay with a strict upgrade period:
1) Latest additions and fixes are required by our user communities - our
resources will be less used if we are slow to upgrade.
2) Rapid updates will be required for LCG operations when the LHC is
running - so it is better to develop good working practices now.
3) If there is no defined timeline it will be difficult to prioritise
locally
If you feel differently about this subject then please raise your
concerns during the deployment session at GridPP14 in Birmingham in
September (yes, we all know it is too close to the Durham meeting)
http://www.gridpp.ac.uk/meetings/
Kind regards,
Jeremy
-----Original Message-----
From: Markus Schulz [mailto:[log in to unmask]]
Sent: 02 August 2005 08:51
To: project-egee-roc-managers ((EGEE ROC managers and alternates));
project-eu-egee-cic-managers
Subject: Update to the LCG-2_6_0 release, please upgrade
Hi,
after releasing 2_6_0 a problem turned up. Information published by
default by some of the 2_6_0 info providers hit a bug in the
2_4_0 gfal libs.
Yesterday afternoon an upgrade to 2_6_0 was released that fixes the
problem.
Who has to react?
===============
Sites that have already upgraded to LCG-2_6_0
markus
p.s. Yes, we tested that the release is backward compatible
before releasing it.
p.p.s Min is adding a test to the GIIS monitor to check for the
problem.
Begin forwarded message:
> From: Maarten Litmaath <[log in to unmask]>
> Date: August 1, 2005 5:38:21 PM GMT+02:00
> To: [log in to unmask]
> Subject: [LCG-ROLLOUT] upgrade to LCG-2_6_0 OK now
> Reply-To: LHC Computer Grid - Rollout <LCG-
> [log in to unmask]>
>
>
> Dear colleagues,
> we came up with a fix. One rpm needs to be upgraded:
>
> lcg-info-templates-1.0.11
> --> lcg-info-templates-1.0.13
>
> The new rpm has been put in the APT repository, so any new
> site upgrading to LCG-2_6_0 will get it automatically.
>
> Sites that already have LCG-2_6_0 must run the following commands
> on all service nodes (not on WNs or UIs):
>
> apt-get update && apt-get upgrade
>
> export INSTALL_ROOT=your_install_root
>
> $INSTALL_ROOT/lcg/sbin/lcg-info-generic-config \
> $INSTALL_ROOT/lcg/var/gip/lcg-info-generic.conf
>
> Sorry about this mess.
>
|