Selecting spaces for read operations in srmPrepareToGet, srmBringOnline, and srmCopy requests. The SRM v2.2 WLCG Usage Agreement specifies that clients must not specify a token for read operations. However, the document assumes silently that the file will be retrieved somehow in the “right” place. The SRM servers at the moment implements different behaviors: dCache serves the file from the place it was put, interfering with production operations; CASTOR honors the token if passed to select the pool where the file should be D DR RA AF FT T read from. This complicates the task to manage the space and to control the access. The possibility to specify a token for read operations and have the server properly keeping it into account must be given.
Appears in 4 contracts
Samples: indico.cern.ch, indico.cern.ch, indico.cern.ch