feat(ray): rework host-submit lineage around roar-worker and fragments#32
Merged
Conversation
b76a953 to
0236bc8
Compare
0236bc8 to
f07cda7
Compare
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 reworks the
roar run ray job submit ...path so Ray jobs bootstrap through a dedicatedroar-worker, stream lineage as encrypted fragments, and reconstitute that lineage back into the host-local.roar/roar.dbafter submission completes.It also rounds out the supporting pieces: packaged preload/native tracer artifacts, new register targets for Ray-shaped lineage, and a much larger host-submit/cloud-topology test suite.
What Changed
roar.ray.driver_entrypoint, useworker_process_setup_hookplusroar-workerinstead of the oldroar.ray.workerpath, add fixedlocal proxy / node-agent bootstrap behavior, and support cluster-visible GLaaS/S3 endpoint overrides.
RAY_JOB_IDandROAR_JOB_INSTRUMENTEDfor Ray job auto-init and git-bypass behavior when drivers run from extracted working dirs rather than a repo checkout.working_dirpaths to host project paths, and materialize composite outputs during rebuild.roar_inject.pth, probe preload launcher readiness, add Linux GLIBC floor verification for wheels, and carry thread-aware metadata through native tracing.roar registerto accept artifact paths, DAG step refs like@4, and local session hash/prefixes, with better parent normalization for Ray-shaped/reconstituted jobs.roar.ray.workercontract and restoreruff,mypy, and unit-test green status after the refactor.