feat: Adding a sync function to runpod-python sdk to help copying workspace between pods #426
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.
Details
croc
is not a good enough solution, it is often extremely slow since RunPod is using our own middle-man servers.This is an option to help mitigate the issue so that if people are using RunPod official pod templates, and have the proper public keys configured, they can sync the data.
Worst happens, they can pause the pod, add the key, and then move on. This is at the very least a very easy way to sync data across to a new pod when someone gets spun up with zero GPUs.
Test
Added unit tests
Manual testing