-
Notifications
You must be signed in to change notification settings - Fork 7.2k
Open
Labels
community-backlogenhancementRequest for new feature and/or capabilityRequest for new feature and/or capabilitytriageNeeds triage (eg: priority, bug/not-bug, and owning component)Needs triage (eg: priority, bug/not-bug, and owning component)
Description
Description
As part of the Ray History Server project, the Ray Dashboard needs to be updated to send Ray API requests to the history server. The history server component will serve the same endpoints as Ray API server but for terminated clusters.
From discussions with @alanwguo and @MengjinYan, it was suggested to add a proxy middleware in Ray Dashboard to redirect API requests to an external history server. The configuration of the proxy middleware will be via environment variables that specifies the external address to redirect requests to.
Use case
Run Ray Dashboard with history server backend to view states of terminated Ray clusters.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
community-backlogenhancementRequest for new feature and/or capabilityRequest for new feature and/or capabilitytriageNeeds triage (eg: priority, bug/not-bug, and owning component)Needs triage (eg: priority, bug/not-bug, and owning component)