-
Notifications
You must be signed in to change notification settings - Fork 7.4k
[core] Combine NodeManagerClient and RayletClient #54816
Copy link
Copy link
Closed
Labels
P2Important issue, but not time-criticalImportant issue, but not time-criticalcoreIssues that should be addressed in Ray CoreIssues that should be addressed in Ray CoreenhancementRequest for new feature and/or capabilityRequest for new feature and/or capabilitygood-first-issueGreat starter issue for someone just starting to contribute to RayGreat starter issue for someone just starting to contribute to Ray
Description
Description
There's currently a NodeManagerClient and a RayletClient but ideally the NodeManagerClient should be moved into the RayletClient. This requires some major refactoring though because NodeManagerClient and RayletClient have the same function names and RayletClient uses the NodeManagerClient. See #54803 for context.
The ideal refactoring would scrap the functions in RayletClient and have the caller code create the requests itself and then call into the functions created by the macros. Feel free to reach out and comment here with any questions if you're willing to pick this up!
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P2Important issue, but not time-criticalImportant issue, but not time-criticalcoreIssues that should be addressed in Ray CoreIssues that should be addressed in Ray CoreenhancementRequest for new feature and/or capabilityRequest for new feature and/or capabilitygood-first-issueGreat starter issue for someone just starting to contribute to RayGreat starter issue for someone just starting to contribute to Ray