Dear SiteManagers,
we would like to bring to your attention what we plan for two releases
in the near future.
The first one (LCG-2.3.1) is driven by security concerns that have
been fixed in the last few days. These affect all nodes that keep up to
date certificate revocation lists, that map users and that are Resource
Brokers.
We highly recommend to upgrade to this release as soon as it is out.
This release will contain some additional bug-fixes, especially for the
configuration tool (YAIM). We will push LCG-2.3.1 out as soon as we
have finished the packaging. This will be before the end of the week.
The second release for which we would like to give you an advanced
warning is LCG-2.4.0. The planned date for this is April 1st (Fools
day, what better time could one imagine for a release). This is the
first release in a sequence of major releases that we will provide
every 3 month. Several components received bug fixes and are not
explicitly listed here.
The main (planned) changes are (in no specific order):
* Updates to the WorkLoadManagement:
RB including the DLI interface to catalogues.
* Components to allow selection of release version and middleware flavor
via the jdl.
* lcg_utils with much improved error messages.
* edg-rm based on lcg_utils.
* LCG-BDII with a configuration interface and features that allow, if
requested, to integrate the sites status derived from testing into the
configuration. In addition the BDII will be more stable and the
problems that have been inherent to the design will be fixed.
New services: ===========
* VOMS for CE and Classic SE, with fallback on grid-mapfiles.
* Disk pool managers:
The diskpool managers will be part of the release, but can be deployed
whenever your site feels the need to switch from the (in)famous
Classic
SE to managed storage. We hope that this will be rather soon. New
sites
should start with managed storage from day 1.
- dCache for medium to large sites
- DPM for small to medium sites
the deployment team
************************************************************************
*******
Markus Schulz
CERN IT
|