Enable SRR at dCache sites

Introduction

All dCache sites are requested to enable Storage Resource Reporting (SRR) functionality which implies publishing of the SRR json file on the dCache frontend. This functionality is provided by dCache starting from dCache version dCache-6.2.29 (released 22.9.2021 the first version with new SRR implementation), though of course the latest 7.2 series are recommended. Publishing SRR on the dCache frontend with public access allows to use SRR information by interested clients, among those are CRIC, WLCG Storage Space accounting (WSSA) , applications used by ATLAS operations and others.

Instructions

  • Sites which are running dCache version higher than dCache-6.2.29 can just enable SRR following the instructions below. Sites which are running older versions are requested to upgrade to the latest dCache releases (currently 14, 15) of 7.2.* series and enable SRR.
  • dCache documentation for enabling SRR

  • Tips from the sites
    • Comment from FI_HIP_T2
      • I think the dcache instructions for SRR are not optimal because it will disable ssl for the frontend. This seems to work for CMS SE just fine allowing normal and secure web gui frontend usage with dcache 6.2.44:


[frontendDomain]
[frontendDomain/frontend]
frontend.authz.anonymous-operations=READONLY
frontend.srr.shares=default:/cms
frontend.srr.public=true

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 "Site Topology" in the menu on the top of the page -> Services. Enable filtering, by clicking on the 'Filter' button and select your site and SE service type. You see the list of storage services registered at the site.

  • 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.

  • 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.
For SE services with enabled SRR link in CRIC, CRIC is updated with storage implementation and its version according to information published in SRR

  • 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 "RR URL" field provide your SRR link. Note that the URL that needs to be published in CRIC for the site will look something like http://<service-FQDN-hostname>:3880/api/v1/srr
  • Click on 'Check input data' and save info

Initial status

By the 29.04.22, there are 12 sites which need to (re)enable SRR. Among them, 8 sites have to be upgraded to the dCache version higher than 6.2.29.

Tracking progress

Site dCache Version (28.04.2022) Plan (date) SRR Comments GGUS ticket
CA-SFU-T2 6.2.41 Requires follow-up   No API access; file written to the storage instead. GGUS:157103, GGUS:157815
CA-VICTORIA-WESTGRID-T2 5.2.41, no SRR     No API access; file written to the storage instead. GGUS:157104
CA-WATERLOO-T2 6.2.49 , SRR enabled but currently blocked by firewall     Pending review. GGUS:157105
ifae 5.2.6 Requires follow-up   No API access; file written to the storage instead. GGUS:157110
praguelcg2 5.2.15, no SRR.     This dCache instance was used for LOCALGROUPTAPE. No point for SRR GGUS:157106
SE-SNIC-T2 5.2.31 , no SRR     Pending review. GGUS:157107
UAM-LCG2 5.2.20, SRR published but with the old mode       GGUS:157108
UKI-LT2-IC-HEP 7.2, SRR enabled but there is a problem Requires follow-up   opened ticket against dCache. Almost done, need to update SRR links for all SE instances in CRIC GGUS:157109
NDGF-T1 6.2.6, bad SRR     Pending review. GGUS:157111
NIKHEF-ELPROD 6.2.30     No API access; file written to the storage instead. GGUS:157112, GGUS:157689
USCMS-FNAL-WC1 5.2, no SRR       GGUS:157113
JINR-T1 5.2.28, SRR is not valid     Pending review. GGUS:157147
MPPMU 7.2.15     No API access; file written to the storage instead. GGUS:157358
RRC-KI 5.2.46       GGUS:157359
Ru-Protvino-IHEP 5.2.31       GGUS:157360
SARA -Matrix 7.2.10     No API access; file written to the storage instead. GGUS:157361
BEgrid-ULB-VUB 5.2.26       GGUS:157354
CIEMAT-LCG2 5.2.27     Pending review. GGUS:157355
FI_HIP_T2 6.2.44 DONE     GGUS:157356
ITEP 5.2.31       GGUS:157357
T3_CH_PSI 5.2.14     No API access; file written to the storage instead. GGUS:157362
UAM-LCG2 5.2.25       GGUS:157363
UNI-Freiburg 5.2.52       GGUS:157364

-- JuliaAndreeva - 2022-04-28

Edit | Attach | Watch | Print version | History: r16 < r15 < r14 < r13 < r12 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r16 - 2022-06-22 - DimitriosChristidis
 
    • 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-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback