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 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.
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.
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 if an online copy exists and is accessible by the process that requested it. Otherwise either a pool-to-pool automatic copy operation is triggered to make a copy of the file available in the pool where the process requesting it has access or a stage from tape operation can be triggered. This behavior can interfere with production operations. CASTOR honors the token if passed to select the pool where the copy of the file should be 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 keep it into account must be given.
