Repository navigation
docs: update NVIDIA Dynamo for scale to zero, console P/D, and RDMA - #85
Merged
Merged
Conversation
The Dynamo page last changed substantively in August. Since then the platform added aggregated scale to zero, console create, edit, and clone for disaggregated deployments, the GPU Direct RDMA KV transfer policy, the runtime version selector, Storage volume mounts, and Dynamo inference metrics on the Usage tab. - Document Min Replicas 0, the concurrency rule for a 0..1 range, the cooldown default, and how requests behave while no Worker is running. - Describe the console's serving topology selector, the Prefill and Decode pool settings, and Edit/Clone for both topologies. - Split the KV transport section by policy (allow_tcp and require_gpu_direct_rdma). - Switch the API example to canonical min_replicas/max_replicas and show communications.kv_transfer.policy. - Add Dynamo Runtime Version, Priority class, the router mode, and Storage volumes. - Remove the GPU quota claim; no platform check enforces it. - Update the monitoring text (pod-count wording, Detail and Usage contents) and the current-scope list, and point the Frontend card at the v1.5.1 docs instead of the redirect to the dev docs. - Managing Deployments: rollout settings and in-place scaling apply to aggregated Dynamo deployments, and logs list Prefill and Decode pods. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
🌿 Preview your docs: https://nvidia-preview-pr-85.docs.buildwithfern.com/ccluster |
Replace the Advanced and Hardware step screenshots with captures of the current console. The Advanced step now shows the runtime version selector and Priority class. The Hardware step shows the serving topology selector, the Storage section, and the capacity summary. Both images are downscaled to 1516 px wide to match the existing screenshots, and their alt text now describes the new content. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
HanFa
marked this pull request as ready for review
November 10, 2026 20:46
atokayev
approved these changes
Nov 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The Dynamo page last changed substantively on 2026-08-19 (#63). This PR updates it to match CentML/platform
mainata53e4be2b.0.allow_tcpkeeps the existing UCX/TCP text and the B200 validation.require_gpu_direct_rdma:FI_*andNIXL_*environment variables.min_replicas/max_replicasinstead of the deprecatedreplicas(CentML/platform#4403).communications.kv_transfer.policyand a note onruntime_version.DYN_ROUTER_MODE, which defaults tokv.observed pods ready.POST/PUT /deployments/dynamohas no quota check, and Dynamo pods run in KAI'sdefault-queue.Section 6 (Call the endpoint) is unchanged, so this PR merges cleanly with #84, which fixes the 404 KServe link there. I checked with
git merge-treeagainst #84's head.Before merging
centml0.7.1 pinsplatform-api-python-client4.31.0 (2026-09-23). In that client,DynamoWorkerPoolConfig.min_replicasis stillge=1, so it cannot read a Dynamo deployment with Min Replicas 0. CentML/platform#4784 asks for the SDK to be published before scale to zero is announced. Either publish it first or add an SDK note to this page.dynamo-advanced-configuration.pnganddynamo-hardware-scaling.pngwere re-captured from the current console, downscaled to 1516 px wide, and given updated alt text. The Endpoint screenshot is unchanged.Validation
I ran the CI checks locally with the pinned Fern CLI 5.168.0:
fern check: 0 errors. The one warning is the missing-redirects check, which needsFERN_TOKEN.fern docs md check: all 20 MDX files valid.fern docs broken-links --strict: all checks passed.python3 tools/check-docs-mdx docs/: OK.python3 tools/check-docs-paths --allow '../docs/' docs fern: OK.git diff --check: clean.fern docs dev:broken-linksdoes not check in-page anchors, so I rendered the page. The new anchors (#aggregated-workers,#scale-to-zero,#disaggregated-serving,#understand-kv-transfer-transport) match heading ids, and both tables render.Context
Each statement was checked against CentML/platform
main: the API schemas and validators, thedynamo_deploymentchart, and the console. CentML/platform#4784 lists this docs update as a follow-up.For #84: the versioned KServe page, https://docs.nvidia.com/dynamo/v1.5.1/knowledge-base/modular-components/frontend/kserve-grpc-frontend, matches the default runtime.
/dynamo/components/frontendredirects to the Frontend overview in the dev docs instead.Two open platform PRs will need another docs update when they merge:
🤖 Generated with Claude Code