You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having an issue with the Storage Element putFile API. We have some standalone xrootd servers at a remote location that don't split out checksums. In my dirac setup, I have some proper grid storage elements (which splits checksum) and some non-grid storage elements. The 'ChecksumType' is a global configuration in StorageElements.
The problem is that when I use the putFile API, it needs the checksum to be returned from the remote SE. But in the getFile API, we have the option to disable the checksum by defining DisableChecksum=True. Is it possible we can have the same option in the putFile API too? or is there any solution already available to that ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey everyone,
I'm having an issue with the Storage Element putFile API. We have some standalone xrootd servers at a remote location that don't split out checksums. In my dirac setup, I have some proper grid storage elements (which splits checksum) and some non-grid storage elements. The 'ChecksumType' is a global configuration in StorageElements.
The problem is that when I use the putFile API, it needs the checksum to be returned from the remote SE. But in the getFile API, we have the option to disable the checksum by defining DisableChecksum=True. Is it possible we can have the same option in the putFile API too? or is there any solution already available to that ?
If not can we have some thing similar in putFile api to what we had in getFile api src/DIRAC/Resource/Storage/GFAL2_StorageBase.py
Beta Was this translation helpful? Give feedback.
All reactions