LHCb SRM v2.2 test details

In the planning LHCb envisages a data transfer test at the end of July/early August 2007. It now seems natural to do this in the context of SRM2.2. After discussion at the GSSD it was agreed some sites could support LHCb. Please find below my first brain dump on what needs to be done in preparation.

Aim: Transfer of data to LHCb T1 centres and triggering of recons jobs using SRM2.2. Original aim was to achieve rates similar to those expected in data taking, maybe wise to downgrade.

• The storage resources available are the ones listed below. In particular CERN has setup an SRM v2 endpoint that allows LHCb production data to be accessed via the SRM v2 endpoint. Tests to verify the correct configuration (including Storage Classes and Storage Tokens setup) for LHCb will be performed by Flavia Donno.
  • CERN
  • IN2P3
  • SARA
  • FZK
  • CNAF

• The exercise will be carried out with computing resources available in the WLCG production infrastructure. Therefore the sites providing storage involved in the tests should publish their SRM v2 test endpoint in the WLCG production BDII. They should not publish any SRM v1 service for those test instances. Flavia Donno

• As agreed at GSSD original tests will be with dCache sites. Nick Brook will identify 15TB of DIGI files at CERN to be transferred (DONE). We originally said that we could create RAW files from DIGI. For what it is worth my opinion is for this SRM2.2 exercise we don't need to but will for exercise later in the year.
  • 5.7 TB of data to IN2P3
  • 5.1 TB of data to SARA
  • 3.3 TB of data to FZK

• Nick Brook will identify DIGI files at CERN to be transferred for CASTOR tests. Need to confimr participating sites: CNAF and RAL assumed.

• Setup FTS 2.0 channels in the production FTS service between the CERN CASTOR SRM v2.2 instance and the other Tier-1 SRM v2.2 sites. Flavia Donno

• Enable DIRAC DMS to use space tokens for FTS2, including small scale tests.

• Check if lcg-utils/GFAL can operate without consulting the BDII (in this case there would be no need to publish the Storage Services with SRM v2.2 in the production BDII). Flavia

• Understand the time scale to have pinning and releasing SRM v2 functionalities (together with BringOnline and GetSpaceMetadata) exposed through GFAL. These should be ready before August 1st, 2007 and installed in the experiment application external area. Flavia

• Move the current functionality of stager to SRM 2.2, including small scale tests - next DIRAC meeting - Stuart

• New functionality of stager with SRM 2.2 - "pinning","releasing",...:
  • preparation work associated with new plug-ins - Andrew
  • full pinning etc functionality (relies on lcg utils) - 3/4 week - Andrew/Stuart

• Workflow for processing jobs - Joel

Timeline

26th July - 1st FTS test transfers performed; new DIRAC SE's in config service

3rd August - GFAL Python binding incorporated into DIRAC

8th August - stager agent with SRM 2.2 with current functionality; DaVinci tests

17th August - stager agent with cache managment functionality

20th August - commence stress tests, with reconstruction dataflow

September - re-run of dCache tests CASTOR sites

November - CERN -> T1 -> recons/stripping -> CERN & T1 tests (will involve disk SE tests)