[codex] Support packing students into GPU pods - #3456
Open
morganmcg1 wants to merge 7 commits into
Open
Conversation
|
I have read the CLA Document and I hereby sign the CLA You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot. |
morganmcg1
marked this pull request as ready for review
May 23, 2026 10:28
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
Adds an opt-in deployment topology for scarce-GPU targets where multiple logical SENPAI students share one GPU pod.
students_per_gpu_podwith default1, preserving the current one-student-per-pod behavior./workspace/senpai-<student>with separateHOMEdirectories.senpai/student-namesso advisor pod-health helpers can find both normal and grouped student pods.train.py, GPU, and Claude activity to the right logical student checkout.Why
Some targets, such as short inference-optimization benchmarks, have one large GPU but still benefit from several logical students preparing launchers, analyzing logs, doing smoke checks, and taking turns on the same device. This keeps the PR-routing model intact while allowing a single GPU pod to host a small student fleet.
Validation
python3 -m py_compile k8s/launch.py k8s/launch_helpers.pybash -n k8s/entrypoint-advisor.sh k8s/entrypoint-student.sh k8s/entrypoint-student-group.sh k8s/student-claude-watchdog.sh k8s/senpai-processes.sh plugins/senpai/scripts/senpai-gh.sh scripts/arm_senpai_cluster_cutoff.shsh -n k8s/senpai-processes.shgit diff --checkuv run --frozen --with simple-parsing python k8s/launch.py --tag pack-test --target_repo_url https://github.com/morganmcg1/tandemfoil2.git --names alice,bob,charlie --gpus_per_student 1 --students_per_gpu_pod 2 --dry_runuv run --frozen --with simple-parsing python k8s/launch.py --tag solo-test --target_repo_url https://github.com/morganmcg1/tandemfoil2.git --names alice,bob --gpus_per_student 1 --students_per_gpu_pod 1 --dry_runNotes
This is intentionally minimal: one global image remains in use, the advisor deployment is unchanged, grouped mode is opt-in, and singleton/grouped student deployments share one template. The advisor still owns research coordination and GPU scheduling through assignments and PR comments.