[core] (cgroups 25/n) Making cgroup_path a part of the public API for ray.init(...)#60726
[core] (cgroups 25/n) Making cgroup_path a part of the public API for ray.init(...)#60726
Conversation
ray.init(...) Signed-off-by: irabbani <israbbani@gmail.com>
There was a problem hiding this comment.
Code Review
This pull request makes cgroup_path a public parameter in ray.init(), which is a sensible change given its necessity in non-privileged container environments. The implementation correctly updates the function signature, documentation, and internal usage. I have a couple of minor suggestions to improve the documentation's clarity and to clean up some leftover code.
Signed-off-by: irabbani <israbbani@gmail.com>
|
Don't forget to update the docs page |
|
Yep waiting for this to merge and then I'll update the other PR. |
Kunchd
left a comment
There was a problem hiding this comment.
Assuming, we probably want to modify scipt.py to make cgroup-path public as well: https://github.com/ray-project/ray/blob/master/python/ray/scripts/scripts.py#L672.
… irabbani/cgroups-21
Good point. Fixed |
… ray.init(...) (ray-project#60726) Follow up from ray-project#60183. When not running inside privileged containers, the user will have to specify a `cgroup_path`. It makes sense for this to be a part of the public API for `ray.init(...)`. Things I'm changing 1. Promoting `cgroup_path` to a public API parameter for `ray.init` 2. Updating tests to use that parameter. 3. Running all cgroup tests on CI for all C++ and python changes. --------- Signed-off-by: irabbani <israbbani@gmail.com> Signed-off-by: tiennguyentony <46289799+tiennguyentony@users.noreply.github.com>
… ray.init(...) (ray-project#60726) Follow up from ray-project#60183. When not running inside privileged containers, the user will have to specify a `cgroup_path`. It makes sense for this to be a part of the public API for `ray.init(...)`. Things I'm changing 1. Promoting `cgroup_path` to a public API parameter for `ray.init` 2. Updating tests to use that parameter. 3. Running all cgroup tests on CI for all C++ and python changes. --------- Signed-off-by: irabbani <israbbani@gmail.com> Signed-off-by: tiennguyentony <46289799+tiennguyentony@users.noreply.github.com>
… ray.init(...) (ray-project#60726) Follow up from ray-project#60183. When not running inside privileged containers, the user will have to specify a `cgroup_path`. It makes sense for this to be a part of the public API for `ray.init(...)`. Things I'm changing 1. Promoting `cgroup_path` to a public API parameter for `ray.init` 2. Updating tests to use that parameter. 3. Running all cgroup tests on CI for all C++ and python changes. --------- Signed-off-by: irabbani <israbbani@gmail.com> Signed-off-by: tiennguyentony <46289799+tiennguyentony@users.noreply.github.com>
… ray.init(...) (ray-project#60726) Follow up from ray-project#60183. When not running inside privileged containers, the user will have to specify a `cgroup_path`. It makes sense for this to be a part of the public API for `ray.init(...)`. Things I'm changing 1. Promoting `cgroup_path` to a public API parameter for `ray.init` 2. Updating tests to use that parameter. 3. Running all cgroup tests on CI for all C++ and python changes. --------- Signed-off-by: irabbani <israbbani@gmail.com> Signed-off-by: tiennguyentony <46289799+tiennguyentony@users.noreply.github.com>
… ray.init(...) (ray-project#60726) Follow up from ray-project#60183. When not running inside privileged containers, the user will have to specify a `cgroup_path`. It makes sense for this to be a part of the public API for `ray.init(...)`. Things I'm changing 1. Promoting `cgroup_path` to a public API parameter for `ray.init` 2. Updating tests to use that parameter. 3. Running all cgroup tests on CI for all C++ and python changes. --------- Signed-off-by: irabbani <israbbani@gmail.com> Signed-off-by: tiennguyentony <46289799+tiennguyentony@users.noreply.github.com>
… ray.init(...) (ray-project#60726) Follow up from ray-project#60183. When not running inside privileged containers, the user will have to specify a `cgroup_path`. It makes sense for this to be a part of the public API for `ray.init(...)`. Things I'm changing 1. Promoting `cgroup_path` to a public API parameter for `ray.init` 2. Updating tests to use that parameter. 3. Running all cgroup tests on CI for all C++ and python changes. --------- Signed-off-by: irabbani <israbbani@gmail.com>
… ray.init(...) (#60726) Follow up from #60183. When not running inside privileged containers, the user will have to specify a `cgroup_path`. It makes sense for this to be a part of the public API for `ray.init(...)`. Things I'm changing 1. Promoting `cgroup_path` to a public API parameter for `ray.init` 2. Updating tests to use that parameter. 3. Running all cgroup tests on CI for all C++ and python changes. --------- Signed-off-by: irabbani <israbbani@gmail.com> Signed-off-by: elliot-barn <elliot.barnwell@anyscale.com>
… ray.init(...) (#60726) Follow up from #60183. When not running inside privileged containers, the user will have to specify a `cgroup_path`. It makes sense for this to be a part of the public API for `ray.init(...)`. Things I'm changing 1. Promoting `cgroup_path` to a public API parameter for `ray.init` 2. Updating tests to use that parameter. 3. Running all cgroup tests on CI for all C++ and python changes. --------- Signed-off-by: irabbani <israbbani@gmail.com>
… ray.init(...) (ray-project#60726) Follow up from ray-project#60183. When not running inside privileged containers, the user will have to specify a `cgroup_path`. It makes sense for this to be a part of the public API for `ray.init(...)`. Things I'm changing 1. Promoting `cgroup_path` to a public API parameter for `ray.init` 2. Updating tests to use that parameter. 3. Running all cgroup tests on CI for all C++ and python changes. --------- Signed-off-by: irabbani <israbbani@gmail.com> Signed-off-by: Adel Nour <ans9868@nyu.edu>
… ray.init(...) (ray-project#60726) Follow up from ray-project#60183. When not running inside privileged containers, the user will have to specify a `cgroup_path`. It makes sense for this to be a part of the public API for `ray.init(...)`. Things I'm changing 1. Promoting `cgroup_path` to a public API parameter for `ray.init` 2. Updating tests to use that parameter. 3. Running all cgroup tests on CI for all C++ and python changes. --------- Signed-off-by: irabbani <israbbani@gmail.com>
… ray.init(...) (ray-project#60726) Follow up from ray-project#60183. When not running inside privileged containers, the user will have to specify a `cgroup_path`. It makes sense for this to be a part of the public API for `ray.init(...)`. Things I'm changing 1. Promoting `cgroup_path` to a public API parameter for `ray.init` 2. Updating tests to use that parameter. 3. Running all cgroup tests on CI for all C++ and python changes. --------- Signed-off-by: irabbani <israbbani@gmail.com> Signed-off-by: peterxcli <peterxcli@gmail.com>
… ray.init(...) (ray-project#60726) Follow up from ray-project#60183. When not running inside privileged containers, the user will have to specify a `cgroup_path`. It makes sense for this to be a part of the public API for `ray.init(...)`. Things I'm changing 1. Promoting `cgroup_path` to a public API parameter for `ray.init` 2. Updating tests to use that parameter. 3. Running all cgroup tests on CI for all C++ and python changes. --------- Signed-off-by: irabbani <israbbani@gmail.com> Signed-off-by: peterxcli <peterxcli@gmail.com>
Follow up from #60183.
When not running inside privileged containers, the user will have to specify a
cgroup_path. It makes sense for this to be a part of the public API forray.init(...).Things I'm changing
cgroup_pathto a public API parameter forray.init