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

Native support for artifacts stored on HPC cluster #224

Open
zjgemi opened this issue Jan 24, 2023 · 0 comments
Open

Native support for artifacts stored on HPC cluster #224

zjgemi opened this issue Jan 24, 2023 · 0 comments

Comments

@zjgemi
Copy link
Collaborator

zjgemi commented Jan 24, 2023

If a whole workflow runs on an HPC cluster. There is no need to upload/download files between the HPC fs and the artifact repository (e.g. S3). Of course one can save the absolute path of the files on HPC as parameters. While dflow can provide a more native support for this.

For example, one can specify input/output artifacts as usual but the storage backend is the HPC fs. It will be better if one can download/preview files on the frontend UI, where the backend implements an FTP client with HPC.

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

1 participant