Design doc for AWS S3 sync to MIT Engaging HPC #2070
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kabilar
changed the title
yarikoptic
reviewed
Nov 20, 2024
| [WIP] | ||
|
|
||
| ## Version Tracking on S3 | ||
| [WIP] |
There was a problem hiding this comment.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.