Table of Contents
dCache Tier I meeting July 28, 2009
[part of a series of meetings]
Present
dCache.org(Patrick,Timur,Gerd,Paul), IN2P3(), Sara(), Triumf(Reda), BNL(Pedro), NDGF(Gerd), PIC(Gerard), GridKa(Doris,Silke), Fermi(Timur), CERN()
Apologies
Fermi (Jon), Lionel (IN2P3)
Site reports
BNL
Nothing to report.
PIC
Everything is OK.
The upgrade to SRM worked fine after the upgrade.
They also reported being very happy with the new SRM Watch. It is now plotting much more information, which is useful.
NDGF
NDGF reported that they are planning to upgrade to dCache v1.9.4-2 tomorrow.
No new problems.
Triumf
Everything is stable.
FZK
FZK have updated both production instances to dCache v1.9.2-9. Things are going smoothly.
Fermi
Fermi reported that they have updated to dCache v1.9.2-9 on public systems. This went smoothly.
IN2P3
(via email) We had no issues here at CC-IN2P3.
For the upgrade, we are basically in the same situation as Triumf. We think of moving all core nodes to 1.9.1-10 and leave pool nodes in 1.9.0. Pool nodes which host doors will be upgraded to 1.9.1-9 too. We expect we can do at the end of the week.
Solaris clients
Pedro asked whether there was any progress in providing Solaris (dcap) clients. This is currently ongoing work.
Patrick will investigate the current status of this work and send Pedro an email with the updated status.
SRM vulnerability
There was a couple of questions about the SRM vulnerability.
Mixing door and SRM head-node versions
Reda asked about how best to upgrade their site. Triumf is running dCache v1.9.0-8 currently. Reda would like to upgrade to v1.9.1-10, but only for the SRM node. Their pool nodes are also door nodes so, although 1.9.0-n series pools are compatible with v1.9.1-m head nodes, dCache doesn't guarantee compatibility between 1.9.0 doors and 1.9.1 head nodes.
Is it possible to only upgrade the SRM only, leaving the others (combined pool and door) nodes at v1.9.0-10 ?
This isn't an officially supported combination, although the motivation was appreciated.
Gerd looked into the release notes and felt that it would be OK to leave the pool+door nodes at dCache v1.9.0-8 and upgrade the SRM to v1.9.1-10 provided the PnfsManager was also running dCache v1.9.1-10. However, he strongly recommended testing this before deploying it on the production site.
Who has upgraded?
Patrick asked the current status of sites: which sites have upgraded or are planning to upgrade in the immediate future?
PIC: yes
GridKA: yes
NDGF : will upgrade tomorrow
Fermi: yes
DTNM
Proposed: same time, next week.