StoRM upgrade task force


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 StoRM storage implementation the recommended versions are those which are equal or higher than 1.11.15. 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 StoRM sites to version 1.11.15 and higher and enabling of SRR

Initial status

dCache versions of the WLCG StoRM sites as of 27.05.2020

  • According to CRIC there are 24 sites which are running StoRM 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.
  • 5 sites are currently running StoRM instances with version 1.11.15 and 2 are running 1.11.17
  • There are 3 sites with unknown StoRM version in CRIC and BDII
  • 13 sites need upgrade

Current activities

  • Ticket sites for upgrade to version 1.11.15 or higher and to enable SRR in case site is already running required version
  • 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 or

General StoRM instructions

  • The recommended version for StoRM TPC is v1.11.15 (or latest versions). As soon as v1.11.18 will be released (by the end of June), this version will become the new recommended version for TPC.
  • If you want to upgrade your StoRM site to the latest version (StoRM v1.11.17), please read carefully and follow the StoRM latest version upgrading instructions.
  • In case of earlier versions, in particular if you are upgrading to v1.11.15 you can follow the StoRM v1.11.15 upgrading instructions.


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 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 StoRM implementation. In the "Resource Reporting URL" field provide your SRR link
  • Click on 'Check input data' and save info

Configuration for Third Party Copy

WLCG sites which need upgrade to 1.11.15

Site StoRM Version (27.05.2020) Upgrade is planned (date) SRR Comments GGUS ticket Contacts
mainz [None] 30/09/2020 [u'1.11.14']
WEIZMANN-LCG2 [u'1.11.7']
UKI-SOUTHGRID-SUSX [None]     According to site admin site does not run StoRM any more. not clear what they are running. Waiting for an answer
INFN-GENOVA [u'1.1.11']     DONE, waiting for Dimitrios for SRR validation
INFN-MILANO-ATLASC [u'1.11.13', u'1.11.13']
INFN-TRIESTE [u'1.11.11', u'1.11.11']
INFN-MIB [u'1.11.14'] 01/11/2020
INFN-CATANIA [u'1.11.9']
INFN-PISA [u'1.11.14']
INFN-BARI [u'1.11.9', u'1.11.9']
IFCA-LCG2 [u'1.11.3'] 30/08/2020
Australia-ATLAS [None]
IL-TAU-HEP [u'1.11.9']     DONE. Waiting for Dimitrios to validate SRR
BY-NCPHEP [u'1.1.13']     Upgraded. Still need to enable SRR
INFN-TORINO [u'1.11.9']

WLCG StoRM sites which upgraded to 1.11.15 or higher but need to enable SRR

Site StoRM Version (27.05.2020) When SRR will be enabled (date) SRR Comments GGUS ticket Contacts
INFN-T1 [u'1.11.15', u'1.11.15', u'1.11.15', u'1.11.15', u'1.11.15']
NCG-INGRID-PT [u'1.11.15', u'1.11.15']
UNI-SIEGEN-HEP [u'1.11.15'] 2020-06-09 storage-descriptor.json
TECHNION-HEP [u'1.11.17']     DONE SRR to be validated by Dimitrios
INFN-ROMA3 [u'1.11.15']
UKI-LT2-QMUL [u'1.11.17', u'1.11.17', u'1.11.17'];;
IFIC-LCG2 [u'1.11.15']
INFN-LECCE [u'1.1.15']


  • Enrico Vianello (StoRM)
  • Julia Andreeva (WLCG Operations)
  • Dimitrios Christidis (Storage Space Accounting expert)

Mailing lists

-- JuliaAndreeva - 2020-05-27

Edit | Attach | Watch | Print version | History: r12 < r11 < r10 < r9 < r8 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r12 - 2020-06-16 - 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