Site | Status | Recent changes | Planned changes |
---|---|---|---|
CERN | CASTOR 2.1.11-9 (tapegateway active) + SRM-2.11 for all main instances ; c2xrootd: 2.1.11-1 FTS: all nodes in SLC5 3.7.0-3 EOSATLAS: 0.1.1-11/xrootd-3.1; EOSCMS: 0.1.0/xrootd-3.0.4 |
CASTOR 2.1.12-1 is being released. Deployment will start with test/validation instances and the general rolll-out is foreseen for the first part of March. Campaign of FileClasses changes (10 days for now). Preparatory work for 2.1.12 to organise user data on tape (Monday 20th) |
|
ASGC | CASTOR 2.1.11-6 SRM 2.11-0 DPM 1.8.2-3 |
None | None |
BNL | dCache 1.9.12.10 (Chimera, Postgres 9 w/ hot backup) http (aria2c) and xrootd/Scalla on each pool |
None | None |
CNAF | StoRM 1.8.0 (Atlas, CMS, LHCb) | None | None |
FNAL | dCache 1.9.5-23 (PNFS, postgres 8 with backup, distributed SRM) httpd=2.2.3 Scalla xrootd 2.9.7/3.1.0.osg Oracle Lustre 1.8.6 EOS 0.1.1-12/xrootd 3.1.0.osg with Bestman 2.0.10 |
||
IN2P3 | dCache 1.9.5-29 (Chimera) on core servers and pool nodes | ? | ? |
KIT | dCache atlassrm-fzk.gridka.de: 1.9.12-11 (Chimera) cmssrm-fzk.gridka.de: head nodes 1.9.5-26 (Chimera), pool nodes 1.9.5-6 through -25 gridka-dcache.fzk.de: head nodes 1.9.5-26 (PNFS), pool nodes 1.9.5-24,-25 xrootd (version 20100510-1509_dbg) |
? | ? |
NDGF | dCache 1.9.14 (Chimera) on core servers. Mix of 1.9.13 and 2.0.0 on pool nodes. | ? | ? |
NL-T1 | dCache 1.9.12-10 (Chimera) (SARA), DPM 1.7.3 (NIKHEF) | ? | ? |
PIC | dCache 1.9.12-14 (last upgrade to patch release on 14-Dec); PNFS on Postgres 9.0 | ? | ? |
RAL | CASTOR 2.1.10-1 2.1.10-0 (tape servers) SRM 2.11 |
Upgraded SRM to 2.11 |
Upgrade NS to 2.1.11 on 14 Feb Upgrade CASTOR to 2.1.11 between 20-29 Feb |
TRIUMF | dCache 1.9.5-28 with Chimera namespace | None | None |
Site | Version | OS, n-bit | Backend | Upgrade plans |
---|---|---|---|---|
ASGC | NA | NA | NA | NA |
BNL | 1.8.0-1 | SL5, 64-bit | Oracle | None |
CERN | 1.8.2-0 64-bit | SLC5 | Oracle | Upgrade to SLC5 64-bit only pending for lfcshared1/2 |
CNAF | 1.8.0-1 | SL5 64-bit | Oracle | None |
FNAL | N/A | Not deployed at Fermilab | ||
IN2P3 | 1.8.2-2 | SL5 64-bit | Oracle 11g | |
KIT | 1.7.4-7 | SL5 64-bit | Oracle | Oracle backend migration pending |
NDGF | 1.7.4.7-1 | Ubuntu 10.04 64-bit | MySQL | None |
NL-T1 | 1.7.4-7 | CentOS5 64-bit | Oracle | |
PIC | 1.7.4-7 | SL5 64-bit | Oracle | |
RAL | 1.7.4-7 | SL5 64-bit | Oracle | |
TRIUMF | 1.7.3-1 | SL5 64-bit | MySQL | None |
Site | Status, recent changes, incidents, ... | Planned interventions |
---|---|---|
BNL | None | Migration of the Conditions Database to 11g and a new hardware, Feb 22 2012. Oracle data guard (physical standby database) will be used during this intervention. |
CNAF | LHCb updated to 11g on 31Jan-01Feb | We still have this problem of huge amount of FTS old data to delete, which is mainly slowing down FtsMonitor, that is too big to be purged by the official scripts. This issue will be treated starting with a clean DB after the scheduled down for FTS HW consolidation and upgrade to SL5+EMI. We are coming closer to this, but there isn't a fixed date yet. |
KIT | Jan 24: ATLAS 3D DB migration to 11g, Feb 1: LHCb 3D/LFC DB upgrade to 11g and migration to new hardware. | |
IN2P3 | On 7 february, ASM gets stuck what had for consequence to abort the apply process.ASM had rised many access errors to some old raw devices which had been deleted at the OS level.The problem has been fixed by bouncing machines Oracle has provided a solution for the problem observed during last upgrade attempt. Unfortunately the solution stop working just before redoing upgrade of LHCB database (09.02) |
|
PIC | LHCb database upgraded to 11g (30.01) | Upgrade of FTS and migration of the ATLAS LFC is intended to do between 27th to 29th of february, but the exact day is not fixed yet. |
RAL | LHCb 3D upgraded to 11g (31.01) | January security patches to be applied, no date yet |
SARA | LHCb 3D upgraded to 11g (01.02) - took until 02.02 | |
TRIUMF | Oracle's JAN 2011 CPU Patch applied to our ATLAS 3D, FTS & TAG database servers. | Short outage to change the database_compatible parameter to 11.2.0.3 to be scheduled |