-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Globus transfer for zstash extract #173
Comments
@lukaszlacinski : I did not realize that you had already implemented all these features. This is wonderful! I ran a few tests today from Chrysalis accessing a zstash archive on NERSC HPSS. Everything worked as expected. Below is some of the functionality I tested (ls, extract, check; single and multiple workers):
Thanks for implementing the Globus functionality. It will make life much so easier for zstash users. |
@lukaszlacinski @golaz This is great! However, I'd like to note that we should update |
@golaz Do we want to advertise/officially support the Globus extract capability with the in-progress release (v1.2.0)? #154 doesn't include information on |
I created #192 to address these points. |
Given the success of #154, it would be great to have the option of using Globus for extracting files.
The idea is that a user could be on Chrysalis and retrieve files from a zstash archive on NERSC HPSS. This would greatly reduce the number of steps required. (Currently a user must manually transfer zstash files, or extract on NERSC and then manually transfer the files to Chrysalis).
For extraction, we only need to implement blocking Globus transfers. I think much of the infrastructure that was put in place for zstash create can be reused for zstash extract.
The text was updated successfully, but these errors were encountered: