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

Design doc for AWS S3 sync to MIT Engaging HPC #2070

Closed
wants to merge 3 commits into from

Conversation

puja-trivedi
Copy link

@puja-trivedi puja-trivedi commented Nov 4, 2024

Note: Document is still a work in progress

Design document explaining the current plan for the initial data transfer as well as future incremental bi-directional transfers between s3 and engaging.

@kabilar kabilar marked this pull request as draft November 4, 2024 18:59
@kabilar kabilar changed the title [WIP] AWS S3 <--> Engaging Data Transfer Document Design doc for AWS S3 sync to MIT Engaging HPC Nov 4, 2024
[WIP]

## Version Tracking on S3
[WIP]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A tool to provide efficient solution is being implemented by @jwodder in https://github.com/dandi/s3invsync . IMHO it should be the first candidate to try

@kabilar
Copy link
Member

kabilar commented Feb 11, 2025

Thank you for your work on this, @puja-trivedi. I will close this pull request since you are no longer working on this target. We haven't yet created a clear design document, but are proceeding with https://github.com/dandi/s3invsync. We will document our use of s3invsync once we are ready, and incorporate material from your document.

@kabilar kabilar closed this Feb 11, 2025
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

Successfully merging this pull request may close these issues.

3 participants