dCache upgrade task force

Introduction

The third-party-copy sub-group of the DOMA working group is dedicated to improving bulk transfers between WLCG sites. All WLCG sites are required to upgrade to the releases of storage implementation which support third-party-copy. For dCache storage implementation the recommended versions are those which are equal or higher than 5.2.0. Another important feature which has to be provided by the WLCG storage services is enabling of the Storage Resource Reporting (SRR). The task force will follow up migration of the WLCG dCache sites to version 5.2.0 and higher and enabling of SRR

Initial status

dCache versions of the WLCG dCache sites as of 29.09.2019

  • According to CRIC there are 43 sites which are running dCache and are used by the WLCG VOs. The number can be higher since for some of sites CRIC is lacking information about storage implementation and implementation versions the sites are running. In particular it concerns OSG sites, though the number of the OSG sites running dCache might be low.
  • Only 6 sites (JINR is counted twice as T1 and T2) are currently running dCache instances with version 5.2.0 and higher. However, not necessarly all instances of the sites are upgraded to 5.2.*.

Current activities

  • Ticket sites for upgrade to version 5.2.* or to enable SRR in case site is already running versions 5.2.*
  • Follow up on progress

Site Instructions

Step by step instructions and useful links are listed below. In case you have questions or comments do not hesitate to contact dcache-upgrade-tf@cernNOSPAMPLEASE.ch

General dCache instructions

SRR

Update information for your site in CRIC

After changes performed on your service, please, update information in CRIC

Authentication & authorization step

  • Go to WLCG cric server , click Core (menu on the top of the page) -> Services. Enable filtering, by clicking on the 'Filter' button and select your site. By default , you won't see implementation and implementation version columns in the table. In order to see this info, you need to click on 'Columns' and then select corresponding columns in the drop down list.

  • You should be able to list all CRIC entities (sites (GocDB /OIM and experiment-specific ones), federations, pledges, services, storage protocols and queues) without authentication. However, once you would like to see details of any particular entity, you would be asked to login.

  • Those who are registered in the CERN DB, please, use SSO authentication. Authentication with certificate is not yet enabled on this instance, will come soon.

  • Those who are not registered in the CERN DB would need to ask for CRIC local account. Please, send a mail to
cric-devs@cernNOSPAMPLEASE.ch with your name, family name and mail address to be used by CRIC to communicate with you.

  • As soon as you are logged in, you will be able to see details of any CRIC entity, however in order to edit in information, one would need to get specific privileges. * As soon as you are authenticated, you will see 'Request privileges' on the top of the page next to your login name. Please, click on it and follow up the request procedure which allows to request global admin privileges, site admin privileges or federation admin privileges. Ask for sites admin privileges for your site. You will be shortly informed that your privileges are enabled. Please re-login.

Editing storage info

  • Once you login with appropriate privileges, you should be able to edit information about your site. At the moment we are particularly interested in storage info at your site, namely its implementation, implementation version and SRR URL when it enabled.

  • CRIC creates virtual storage service per site/per VO/per media/per implementation. By default it creates 1 disk and 1 tape virtual storage for every VO which is served by a given T1 site and 1 disk visrtual storage for T2 site. However, if for a given VO there are storage instances for the same media but different implementation (for example EOS and dCache instances for disk storage for ATLAS), CRIC should create two different disk virtual storage instances for this VO. Unfortunately, for the moment, there is no reliable primary source for this kind of information, so it is highly likely that only a single virtual storage will be created by CRIC in such cases. Would be great if you could correct it using CRIC UI and add other storage virtual instances with their implementation , implementation versions for your site and SRR URL when it is enabled. In the future we hope to get this information through SRR (Storage Resource Reporting).

  • In the service table view, click on a particular service name
  • You get a form with detailed information about service
  • Click on the 'Edit' button under the first block of information
  • You get another form. Please, correct 'Version' of your dCache implementation. In the "Resource Reporting URL" field provide your SRR link
  • Click on 'Check input data' and save info

WLCG sites which need upgrade to 5.2.*

Site dCache Version (11.12.2019) Upgrade is planned (date) SRR Comments GGUS ticket Contacts
USCMS-FNAL-WC1 [None, None]       GGUS:144503 cms-t1@fnalNOSPAMPLEASE.gov
GoeGrid [u'2.16.50']       GGUS:144489 goegrid_admin@physikNOSPAMPLEASE.uni-goettingen.de
IEPSAS-Kosice [u'3.2.40']       GGUS:144490 grid.support@saskeNOSPAMPLEASE.sk
wuppertalprod [u'4.2.23']       GGUS:144504 lcg-admin@physikNOSPAMPLEASE.uni-wuppertal.de
CIEMAT-LCG2 [u'3.2.46'] Jan. 2020     GGUS:144484 lcg.support@ciematNOSPAMPLEASE.es
BNL-ATLAS [u'4.2.22', u'3.0.11']       GGUS:144481 jhover@bnlNOSPAMPLEASE.gov
CSCS-LCG2 [u'3.2.53', u'3.2.53', u'3.2.53']       GGUS:144485 grid@cscsNOSPAMPLEASE.ch
INFN-LNL-2 [u'4.2.42']       GGUS:144492 grid-prod@lnlNOSPAMPLEASE.infn.it
INFN-ROMA1-CMS [u'2.13.56']       GGUS:144493 grid-prod@roma1NOSPAMPLEASE.infn.it
DESY-ZN [u'4.2.31'] Jan 2020     GGUS:144487 grid-admin@zeuthenNOSPAMPLEASE.desy.de
CA-VICTORIA-WESTGRID-T2 [u'4.2.31']       GGUS:144482 rcf-lcg@uvicNOSPAMPLEASE.ca
CA-WATERLOO-T2 [u'2.16.65']       GGUS:144483 lcg-support-waterloo@computeontarioNOSPAMPLEASE.ca
UAM-LCG2 [u'4.2.27']       GGUS:144501 lcg.support@uamNOSPAMPLEASE.es
T3_CH_PSI [u'3.2.18']       GGUS:144499 cms-tier3@listsNOSPAMPLEASE.psi.ch
RWTH-Aachen [u'4.2.24'] Feb 2020     GGUS:144498 lcg-contact@physikNOSPAMPLEASE.rwth-aachen.de
RU-Protvino-IHEP [u'3.2.21', u'3.2.21', u'3.2.21']       GGUS:144497 lcg@ihepNOSPAMPLEASE.ru
ITEP [u'3.2.21']       GGUS:144494 lublev@itepNOSPAMPLEASE.ru
praguelcg2 [u'4.2.38']       GGUS:144496 ngi-firstline@metacentrumNOSPAMPLEASE.cz
UNI-FREIBURG [u'2.16.51']       GGUS:144502 lcg-admin@bfgNOSPAMPLEASE.uni-freiburg.de
BEIJING-LCG2 [u'2.16.22']     Plan to move to DPM GGUS:144480 lcg-admin@ihepNOSPAMPLEASE.ac.cn
DESY-HH [u'5.2.3', u'4.2.22']     Not all instances run required version GGUS:144486 grid@desyNOSPAMPLEASE.de
TRIUMF-LCG2 [u'4.2.39', u'5.2.4', u'4.2.39']     Not all instances run required version GGUS:144500 support@lcgNOSPAMPLEASE.triumf.ca

WLCG dCache sites which upgraded to 5.2.* but need to enable SRR

Site dCache Version (11.12.2019) When SRR will be enabled (date) SRR Comments G GUS ticket Contacts
ifae [u'5.2']       GGUS:144491 lcg.support@picNOSPAMPLEASE.es
NDGF-T1 [u'5.2.2', u'5.2.2', u'5.2.2', u'5.2.2']       GGUS:144516 support@ndgfNOSPAMPLEASE.org
FI_HIP_T2 [u'5.2']       GGUS:144488 finnish-lhc-admins@helsinkiNOSPAMPLEASE.fi
LRZ-LMU [u'6.0.0']     Version is 6.0.0 GGUS:144495 lcg-admin@listsNOSPAMPLEASE.lrz.de
BEgrid-ULB-VUB [u'5.2.3']   https://maite.iihe.ac.be:2880/storage-descriptor.json DONE, but SRR to be checked GGUS:144506 grid_admin@listservNOSPAMPLEASE.vub.ac.be
JINR-LCG2 [u'5.2.3', u'5.2.3']     DONE GGUS:144511 lcgadm@lxmailNOSPAMPLEASE.jinr.ru
JINR-T1 [u'5.2.3', u'5.2.3']     DONE GGUS:144512 t1adm@lxmailNOSPAMPLEASE.jinr.ru
IN2P3-CC ['5.2.9-1']       GGUS:144510 grid.admin@ccNOSPAMPLEASE.in2p3.fr
FZK-LCG2 ['5.2.10']       GGUS:144509 lcg-admin@listsNOSPAMPLEASE.kit.edu
pic ['5.2.6']       GGUS:144517 lcg.support@picNOSPAMPLEASE.es
KR-KISTI-GSDC-02 [u'5.2.10']     SRR is enabled. But in SRR shares section is empty, only overall space size is provided , similar problem as in IN2P3 , has to be clarified with dCache developers GGUS:144513 geonmo@kistiNOSPAMPLEASE.re.kr
KR-KNU-T3 [u'5,2,10']     Same problem as in IN2P3 and KISTI GGUS:144514 lcg_knu@knuNOSPAMPLEASE.ac.kr
UKI-LT2-IC-HEP ['5.2.10']       GGUS:144521 lcg-site-admin@imperialNOSPAMPLEASE.ac.uk
MPPMU [u'5.2.10']       GGUS:144515 lcg-support@rzgNOSPAMPLEASE.mpg.de
UKI-SOUTHGRID-RALPP [u'5.2.5']       GGUS:144522 PPD.GRID.Support@stfcNOSPAMPLEASE.ac.uk;pete.gronbech@physics.ox.ac.uk
CA-SFU-T2 [u'5.2.9']       GGUS:144507 lcg-support@sfuNOSPAMPLEASE.ca
EELA-UTFSM [u'5.2.5']   https://se.hpc.utfsm.cl:2880/atlas/storage-descriptor.json DONE , but SRR to be checked GGUS:144508 grid@hpcNOSPAMPLEASE.utfsm.cl
SE-SNIC-T2 [u'5.2.7']       GGUS:144520 wlcg-tier2@listsNOSPAMPLEASE.snic.se
RRC-KI-T1 [u'5.2.4' tape and disk]       GGUS:144518 gridops@gridNOSPAMPLEASE.kiae.ru
SARA-MATRIX ['5.2.0']       GGUS:144519 eugrid.support@surfsaraNOSPAMPLEASE.nl

Performed tasks

Documentation for enabling SRR (DONE)

  • Task Force has requested dCache team to provide documentation of how to enable SRR. Jira ticket to follow the progress
  • First draft of documentation
  • Valery Mitsyn from JINR kindly agreed to validate the documentation. There are few comments from him below:
    • We needed to install additionally libxslt, it was not installed on our dCache nodes.
    • They got the question where/how file can be accessed
      • the file should be accessible through http protocol. URL to the file will be recorded in CRIC
    • With what credentials the file should be accessed
      • WLCG Storage Space accounting collector has robot certificates with the credentials of all 4 LHC experiments. These certificates can be used for this purpose

Membership

  • Edward Karavakis (Task Force coordinator)
  • Julia Andreeva (WLCG Operations)
  • Dimitrios Christidis (Storage Space Accounting expert)
  • Christoph Wissing ( CMS)
  • Oliver Freyermuth (ATLAS)

dCache team will provide all necessary technical expertise and guidance

Mailing lists

-- JuliaAndreeva - 2019-08-29

Edit | Attach | Watch | Print version | History: r14 < r13 < r12 < r11 < r10 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r14 - 2020-01-09 - JuliaAndreeva
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LCG All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback