Ricky Xu 44daf3ecd7 [Core][State Observability] Get API using List endpoints + filtering on ids (#25894) ... ## Why are these changes needed? This is a first implementation of GET APIs for nodes actors placement groups workers tasks objects E.g. # CLI (dev) ➜ ray git:(ricky/obs-get) ray get nodes cab26304d105caa6f2100908f7b461ef9ed244984ec30b4b46f953f9 --- node_id: cab26304d105caa6f2100908f7b461ef9ed244984ec30b4b46f953f9 node_ip: 172.31.47.143 node_name: 172.31.47.143 resources_total: CPU: 8.0 memory: 16700517582.0 node:172.31.47.143: 1.0 object_store_memory: 8350258790.0 state: ALIVE # Python from ray.experimental.state.api import get_node from ray.experimental.state.common import NodeState node :NodeState = get_node(<id>) print(node) We currently do not support getting specific resources by id for 'jobs' and 'runtime-envs' jobs: it is not exposing id to be queried easily yet runtime envs: it doesn't have an id associated. TODO: it uses list endpoints + filtering as for now, future iterations will implement GET-specific endpoints and interaction with raylet/GCS with point query APIs. Unit testing for state_manager for GET endpoints when implemented. Getting jobs by id		2022-06-27 17:14:29 -07:00
..
__init__.py	Revert "Revert "[State Observability] Basic functionality for central… (#23933)	2022-04-18 21:15:43 -07:00
state_head.py	[Core][State Observability] Get API using List endpoints + filtering on ids (#25894)	2022-06-27 17:14:29 -07:00