feature: unify naming of production-stack, vllm-stack and vllm-router

[bufferoverflow]

Describe the feature

Today multiple names are used, e.g.,

• repo name: production-stack
• release: vllm-stack
• container: production-stack/router
• python package name: vlllm-router

It would be great to have consistent naming all over, e.g., vllm-router

Why do you need this feature?

Simplifies usage and avoid confusion with different names

Additional context

No response

[ApostaC]

Thanks for your suggestion! It makes a lot of sense!

"production-stack" is the name of the whole project and it contains a couple of components, including router, the helm chart, and the observability stack. We are also expecting more features around vLLM to be added into production-stack in the future, such as autoscaling, and kv cache offloading interface.

I think it makes sense to change the release/container/python-package name to something like:

• release: production-stack-chart
• container (for router) and python package name (for router): production-stack-router

Also cc @YuhanLiu11 @gaocegege for your opinions.

[YuhanLiu11]

Thanks for your suggestion! It makes a lot of sense!

"production-stack" is the name of the whole project and it contains a couple of components, including router, the helm chart, and the observability stack. We are also expecting more features around vLLM to be added into production-stack in the future, such as autoscaling, and kv cache offloading interface.

I think it makes sense to change the release/container/python-package name to something like:

• release: production-stack-chart
• container (for router) and python package name (for router): production-stack-router

Also cc @YuhanLiu11 @gaocegege for your opinions.

production-stack-chart and product-stack-router sounds good to me!

[bufferoverflow]

I personally would prefer having vllm within the name as this is the focus and hosting group here

[wangchen615]

I second @YuhanLiu11 's comment.

[gaocegege]

I personally would prefer having vllm within the name as this is the focus and hosting group here

I agree. "Production stack" is too broad and makes SEO and community marketing challenging. Including "vllm" in the name would clarify that our stack is specifically tailored for vllm, similar to how "sglang-router" is purpose-built for its use case.