List view
Tracker for req. 2: Users must be able to deploy an updated version of a foundation model For example, if using a curated IBM model, when IBM releases a new model version, users must be able to deploy the updated model version. The same scenario applies to foundation models from other sources such as Hugging Face.
Overdue by 1 year(s)•Due by August 25, 2023Tracker for work related to Req. 6: P0: Enable users to create & access http and grpc endpoints for model serving routes
Overdue by 1 year(s)•Due by August 25, 2023•2/2 issues closedTracking the work towards Req. 5: P0: Users must be able to access all applicable metrics for any deployed model including: - number of inference requests over defined time period - Avg. response time over defined time period - number of successful / failed inference requests over defined time period - Compute utilization (CPU,GPU, Memory)
Overdue by 1 year(s)•Due by August 25, 2023•2/2 issues closedTracking all of the work towards Req. 2 and 4. Req. 2: P0: Users must be able to deploy an updated version of a foundation model For example, if using a curated IBM model, when IBM releases a new model version, users must be able to deploy the updated model version. The same scenario applies to foundation models from other sources such as Hugging Face. Req. 4: P0: The system must support the ability to update the Caikit serving runtime version without impacting actively served models For example, the upstream version will be updated and need to incorporate in RHODS as appropriate without impacting deployed models. A new RHODS release must not break model serving functionality.
Overdue by 1 year(s)•Due by August 25, 2023•1/1 issues closedTracking all of the issues that need to be completed to be included in ODH 1.8.0 Release starting with ODH nightlies.
Overdue by 2 year(s)•Due by July 21, 2023•7/7 issues closed