Closed jhasm closed 1 year ago
cc @edoakes @architkulkarni
There is already a metadata
field where you can pass an arbitrary JSON dictionary and it's returned in the GET
job endpoint. This just needs to be exposed in the dashboard.
Added to the polish item
@edoakes , @scottsun94 noticed that these metadatas are not able to be passed in via the CLI today. Is this something that can be added?
certainly can be
Maybe cc @architkulkarni? seems like an easy fix (I assume it would take 10m to finish it). If he's busy I can also take a look
Addressed here https://github.com/ray-project/ray/pull/34586 for the CLI.
Description
It will be very helpful to allow users to add custom tags to ray jobs at the time of submission, and see those tags in job metadata on the dashboard. If there is a way of exporting this data or storing it in an external durable storage, this metadata will become a great resource for fault, latency, resource analysis and reporting.
The tags can be used for grouping, filtering and reporting purposes. This can also be used for enriching ML experiment tracking and model lineage, as well as cost attribution.
Use case
We run multi-tenant ray clusters to balance between the number of idle ray clusters latency of creating a new cluster on-demand. This means there are multiple users from various teams/projects submitting jobs to a given ray cluster. In this situation, the only definite information the users know is the ray job_id and they have to track their jobs in a separate database to track their work for the team or project.
Following challenges are hard to address without any metadata on the jobs.