Add optional external compute provider support#40
Open
Links17 wants to merge 7 commits into
Open
Conversation
added 7 commits
June 18, 2026 10:45
This file contains hidden or 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
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.
Summary
This PR adds an optional external compute provider path for training jobs, with a Seeed Cloud provider implementation behind configuration.
The goal is to make LeLab training easier to run for users who have robot data locally but do not have a CUDA-capable workstation. Seeed Cloud is currently available as a free Seeed-hosted compute option for configured users, and this flow is already being used around LeRobot-compatible Seeed hardware such as reBot Arm B601-DM. Seeed's public B601-DM LeRobot guide covers data collection and training in the LeRobot framework: https://wiki.seeedstudio.com/rebot_arm_b601_dm_lerobot/
The implementation keeps that support optional: without provider configuration, the default local and Hugging Face Cloud flows remain unchanged.
What changed
Review notes
The Seeed-specific integration is intentionally isolated behind the provider interface and local configuration. If no Seeed Cloud token/config is present, users should only see the existing local/HF behavior plus any public provider flavor catalog exposed by configured providers.
I kept the provider interface generic so other hosted compute backends can be added without coupling the job registry to one vendor.
Test plan
python -m pytest tests/test_compute_providers.py tests/test_seeed_cloud_config.py tests/test_jobs.py tests/test_record.py tests/test_train.py tests/test_utils_hf_auth.pynpm run build