vllm-project / vllm-project/aibrix

Model orchestration with heterogeneous hardwares

Open
#13 4 comments 0 reactions 1 assignee Claimed by @Jeffwan View on GitHub
area/heterogeneous kind/enhancement priority/important-soon
Dominant language
Go
Stars
5.1k
Forks
694
Avg merge
1d 20h
Merged PRs (30d)
98

Description

We meet a few cases that single deployment needs to be deployed across different chips due to quota or resource shortage. However, in Kubernetes, most of the time we use `Deployment` to manage a group of pods using one type of GPU, If we remove GPU type constraints, then it's hard to control the ratio. Technically, we can workaround the problem using multiple deployment, but the rolling upgrade control additional control, same as HPA. The RoleSet CRD is not able to manage the such cases as well.

1. We may need other orchestrators for instances using heterogeneous hardwares, HPA, Rolling upgrade need to be revised as well.
2. We need more advanced Traffic Routing solutions to handle such differences
3. It also brings lots of challenges on monitoring at the service level etc

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.