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

Copy to Vast: status indicator #356

Open
pgarrison opened this issue Dec 9, 2024 · 2 comments · May be fixed by #388
Open

Copy to Vast: status indicator #356

pgarrison opened this issue Dec 9, 2024 · 2 comments · May be fixed by #388
Assignees

Comments

@pgarrison
Copy link
Contributor

pgarrison commented Dec 9, 2024

User story

Scientists 1 and 2 are working on a project that needs to use file A on local storage, but File A is only on the cloud. Scientist 1 uses BFF to copy the file to the Vast. The file is 4TB so it isn't immediately available. Scientist 2 goes to BFF to do the same thing: they would like to know if the download is already in progress.

Design

In “canonical file path field” write “Copying to Vast in progress…” (italics) for in-progress downloads

Implementation details

  • Cloud only: shouldBeInLocal is False
  • Download in progress: shouldBeInLocal is True and eviction date is null
  • Download complete: shouldBeInLocal is True and eviction date is non-null
@pgarrison
Copy link
Contributor Author

More design decisions needed: The plan above uses "File Path (Canonical)" but does not account for "File Path (Local)", since our test usage of BFF didn't surface files with a "File Path (Local)". Need to get clarity on how the three paths (Cloud, Local, Canonical) interact and decide which to display for downloads in progress. "Canonical" path may be of little value to users, compared to the other two.

@pgarrison pgarrison assigned pgarrison and unassigned pgarrison Dec 18, 2024
@pgarrison pgarrison self-assigned this Jan 7, 2025
@pgarrison
Copy link
Contributor Author

We can also use the presence of a local path to identify whether the download is in progress

@pgarrison pgarrison linked a pull request Jan 9, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants