4fbbdfd250
Signed-off-by: zwhzzz0821 <2831474076@qq.com> Co-authored-by: zwhzzz0821 <zwhzzz0821@users.noreply.github.com> Co-authored-by: SYLAR <125541396+lishunyang12@users.noreply.github.com> Co-authored-by: Hongsheng Liu <liuhongsheng4@huawei.com>
65 lines
2.6 KiB
Markdown
65 lines
2.6 KiB
Markdown
# vllm-omni serve
|
|
|
|
## Stage-based CLI quickstart
|
|
|
|
The stage-based CLI is designed for deployments that require launching each pipeline stage in an isolated process
|
|
(e.g., across separate operating system processes, distinct GPUs, or distributed hosts).
|
|
|
|
- For **migrated models** that utilize the bundled deployment YAML configurations located in
|
|
`vllm_omni/deploy/`, the `--deploy-config` flag is only required to override the default configuration. By default, executing `vllm serve MODEL --omni ...`
|
|
automatically loads the bundled deployment configuration.
|
|
- For custom legacy `stage_args` YAMLs, pass the file with `--stage-configs-path`.
|
|
|
|
Example: Initializing Stage 0 (Orchestrator and API Server):
|
|
The commands below show a common device mapping where Stage 0 uses GPU 0 and
|
|
worker stages use GPU 1 via `CUDA_VISIBLE_DEVICES`.
|
|
|
|
```bash
|
|
CUDA_VISIBLE_DEVICES=0 vllm serve Qwen/Qwen3-Omni-30B-A3B-Instruct --omni \
|
|
--port 8091 \
|
|
--stage-id 0 \
|
|
--omni-master-address 127.0.0.1 \
|
|
--omni-master-port 26000
|
|
```
|
|
|
|
Example: Initializing a Headless Worker Stage (Stage 1):
|
|
|
|
```bash
|
|
CUDA_VISIBLE_DEVICES=1 vllm serve Qwen/Qwen3-Omni-30B-A3B-Instruct --omni \
|
|
--stage-id 1 \
|
|
--headless \
|
|
--omni-master-address 127.0.0.1 \
|
|
--omni-master-port 26000
|
|
```
|
|
|
|
When utilizing a custom deployment YAML based on the new schema, append `--deploy-config /path/to/override.yaml` to each command execution. Conversely, for legacy models, substitute this parameter with `--stage-configs-path /path/to/stage_configs.yaml`.
|
|
|
|
In the standard execution paradigm, the `--stage-overrides` argument is utilized to apply stage-specific configurations from a single CLI command.
|
|
However, under the **stage-based CLI** paradigm, where each process strictly encapsulates a single stage, it is recommended to specify tuning parameters directly via discrete command-line flags for the respective stage, rather than constructing a composite `--stage-overrides` JSON string.
|
|
|
|
For example, as an alternative to the following composite configuration:
|
|
|
|
```bash
|
|
vllm serve Qwen/Qwen3-Omni-30B-A3B-Instruct --omni --port 8091 \
|
|
--stage-overrides '{"1": {"gpu_memory_utilization": 0.5}}'
|
|
```
|
|
|
|
the stage-based CLI permits the direct initialization of Stage 1 with explicit parameters:
|
|
|
|
```bash
|
|
CUDA_VISIBLE_DEVICES=1 vllm serve Qwen/Qwen3-Omni-30B-A3B-Instruct --omni \
|
|
--stage-id 1 \
|
|
--headless \
|
|
--gpu-memory-utilization 0.5 \
|
|
--omni-master-address 127.0.0.1 \
|
|
--omni-master-port 26000
|
|
```
|
|
|
|
## JSON CLI Arguments
|
|
|
|
--8<-- "docs/cli/json_tip.inc.md"
|
|
|
|
## Arguments
|
|
|
|
--8<-- "docs/generated/argparse_omni/omni_serve.inc.md"
|