Skip to main content
This playbook serves the canonical native-FP8 zai-org/GLM-5.3 checkpoint with vLLM on one 8×H200 node. It is the simplest vendor-documented topology that leaves useful runtime headroom.
Vendor-verified · AI Reserve qualification pending. The model and vLLM recipes are upstream-supported, but this exact AI Reserve launch has not completed the acceptance run. Pin an image digest after qualification; a floating image or version tag is not a production release artifact.

Recipe contract

The full 1M window is a separate capacity target. Upstream documents 8×B200 with FP8 KV for that operating point; on H200, admit only the maximum context and concurrency your load test proves.

1. Set up the API client

Every command on this page is copy-paste. Paste the shell block once per terminal and replace only the API key; every later step reads these variables. The Python and TypeScript tabs read the same variables from the environment.
Two keys, two jobs. AIRESERVE_API_KEY authenticates you to AI Reserve and creates the volume, quote, and instance. VLLM_API_KEY is a password you invent for the vLLM server you are about to start: step 5 passes it as vLLM’s --api-key, so the public HTTP port rejects anyone who does not send it. No vendor issues it and AI Reserve never sees it.
The shell tabs need curl and jq.

Check stock first

A quote is free and creates nothing. Run one before creating storage, because the volume in step 2 is placed next to this hardware and fails the same way when none is in stock:
A response with availability and price means you can continue. An error with code: no_capacity means this shape is not in stock in that region right now: try another region here and in steps 2 and 3, or wait, and read no_capacity reasons.

2. Create the weights volume

Available now. The accelerator hint places the volume where an H200 can mount it. Storage bills until you delete it, even after compute is terminated.
In the shell, wait for the operation before quoting compute (the Python and TypeScript tabs already call wait):

3. Quote the serving node

Available now. The quote creates nothing, expires after 120 seconds, and binds the hardware, image, disk, and volume.

4. Pin and download the model

Manual today. AI Reserve does not yet have a model-preload resource. vLLM downloads the pinned revision into HF_HOME during first launch. To preload it separately, run this in a qualified loader image with the same volume mounted. The verification command requires the current hf CLI from huggingface_hub 1.18 or later, not the deprecated huggingface-cli:
Do not substitute zai-org/GLM-5.3-BF16: its runtime budget is about 1.786 TB and it requires a different topology. Treat third-party NVFP4 builds as separate artifacts that need their own quality run.

5. Launch vLLM

Available now, runtime qualification pending. The image entrypoint receives the model and engine arguments below. HF_HOME keeps the resumable download on the persistent volume. The raw vLLM port is public, so --api-key is mandatory.
In the shell, wait for the launch operation (the Python and TypeScript tabs already call wait):
A running instance is not a ready model. vLLM still has to load about 756 GB of weights (downloading them first unless step 4 staged them) and shard them across eight GPUs, which takes tens of minutes. Step 6 waits for /v1/models before the first request. To watch progress:
The upstream recipe body still mentions 0.28.0, but its current compatibility header requires 0.29.0+. This playbook deliberately requires 0.29.0 and remains qualification-pending until one immutable image digest passes.

6. Discover and verify the endpoint

Retrieve the HTTP URL only after the operation succeeds. The shell block sets ENDPOINT from the port 8000 connection, then waits for the first successful /v1/models, which is the readiness signal.
clear_thinking=true is required for ordinary multi-turn chat; otherwise the template preserves prior reasoning. Run the same test at low, high, and max, then add a tool schema and verify that tool_calls is valid JSON and that arguments satisfy the schema.

7. Qualify throughput and context

Run the benchmark client from another machine so it does not contend with the server. Start with prefix caching disabled for a clean baseline, then enable it and measure the production request mix.
Sweep 4K, 32K, 128K, then the largest context you intend to admit. Repeat at increasing request rates and concurrency until p95 TTFT or TPOT misses your objective. Synthetic prompts understate MTP acceptance; repeat with real agent traces and report mean accepted draft length. Before promotion, verify:
  • no OOM, worker restart, or malformed tool call at the admitted limits;
  • p50/p95/p99 TTFT, TPOT, end-to-end latency, queue time, and error rate;
  • input/output throughput, KV and prefix-cache hit rate, HBM and host memory;
  • MTP enabled and disabled on identical prompts;
  • rolling restart and rollback to the prior image digest.
AI Reserve does not currently provide managed replicas, load balancing, draining, durable workload logs, customer GPU metrics, or autoscaling for raw instances. Those are platform gaps, not optional production checks. Put an authenticated load balancer and monitoring layer in front before accepting customer traffic.

8. Clean up

Terminate compute first. Delete the volume only after confirming the checkpoint cache is no longer needed.

Primary sources