Skip to content
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

Could/Should our caching step support scp? #753

Open
jbusecke opened this issue Jun 6, 2024 · 4 comments
Open

Could/Should our caching step support scp? #753

jbusecke opened this issue Jun 6, 2024 · 4 comments

Comments

@jbusecke
Copy link
Contributor

jbusecke commented Jun 6, 2024

I am currently facing a lot of request to ingest data from various servers/HPC centers. For example in leap-stc/data-management#126 (comment) http, ftp, or globus are not accessible.

I think this is pushing the concept of pgf a bit, but enabling this would unlock a LOT of interesting datasets for ingestion.

I guess my naive way to think about this is we could store ssh login creds in the feedstock secrets, then transfer the data to the local worker storage, and move them to a cloud bucket?

Any thoughts concerns @rabernat @moradology @ranchodeluxe @cisaacstern?

@yuvipanda
Copy link
Contributor

fsspec has an SFTP implementation: https://github.com/fsspec/sshfs, and I'm a big fan of asyncssh (what backs this)

@jbusecke
Copy link
Contributor Author

That is super useful! Thank you @yuvipanda.
So the situation above is actually more complex, since that server is only available from within the columbia network or via VPN. Wondering if there is an elegant way to navigate this?

@yuvipanda
Copy link
Contributor

What would the direction of data flow be? Something 'pushing' into 'pangeo forge' or pangeo forge 'pulling'? Right now everything is really a pull.

@jbusecke
Copy link
Contributor Author

I would like to keep it as a pull if possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants