-
Notifications
You must be signed in to change notification settings - Fork 610
[Doc] add ray cluster uv sample yaml #3720
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: fscnick <fscnick.dev@gmail.com>
@kevin85421 PTAL |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you need to create a worker group? If this example doesn't require worker group, please remove it. If you want to run something on the worker Pods, please try to schedule the Ray tasks on the worker Pods (ex: setting num-cpus: 0
to the head group).
@MortalHappiness can you review this PR and ray-project/ray#53303? |
Signed-off-by: fscnick <fscnick.dev@gmail.com>
Signed-off-by: fscnick <fscnick.dev@gmail.com>
f911cb5
to
a9fd0d4
Compare
Hi @MortalHappiness, CI has passed. |
Why are these changes needed?
In order to help users getting involved uv easier, provides this
ray-cluster.uv.yaml
as an example. It enables the runtime env hook so thatuv run ...
could work with runtime environment in the RayCluster, reference uv + Ray: Pain-Free Python Dependencies in Clusters for more information about this runtime env hook.By the way, the
working_dir
is under/home/ray
as default, which contains files. It might cause some errors during preparing runtime env because some limitations. Changing to folder/home/ray/samples
could avoid this issue.Related issue number
Closes #3039
Checks