docs(gpu): add a GPU overview page that maps the five paths - #704
Draft
Andrei Kvapil (kvaps) wants to merge 3 commits into
Draft
Andrei Kvapil (kvaps) wants to merge 3 commits into
Andrei Kvapil (kvaps) wants to merge 3 commits into
Conversation
GPU documentation is spread over five pages in four sections, and nothing tells a reader which one applies to them. The variant choice is made once per node and is not reversible by a values edit, so a reader who lands on the wrong page first pays for it on the host. Adds one orientation page under Learn Cozystack: a table from consumer to path, the reason the three operator variants are mutually exclusive, how tenant clusters stack on passthrough, and the limits worth knowing before planning around them (MIG, vGPU licensing, HAMi glibc, HAMi over the container variant). No procedure is restated, so the page does not go stale when the underlying guides change. Assisted-by: LLM Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
The KubeVirt paragraph no longer promises a starter device table for every VM-facing variant: on main the vgpu variant gets the feature gate and no table at stock values, so the page now says the platform owns the list and points at the guide for what it carries. The MIG item now says only what holds everywhere, that a MIG instance cannot be passed to a VM, so it does not read as contradicting the AI Conformance page on MIG inside tenant clusters. That page is now linked from the tenant section, since it is where DRA, Kueue and DCGM on tenant clusters are recorded. Assisted-by: LLM Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
Contributor
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
✅ Deploy Preview for cozystack ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
1 participant
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.
GPU docs are spread over five pages in four sections, and nothing tells a reader which one they need. It matters here more than elsewhere: the gpu-operator variant is picked once per node, and undoing a wrong pick means reworking the host.
This adds one map page under Learn Cozystack, in
next/andv1.6/. It only links to the existing guides and doesn't repeat any procedure from them, so it won't need updates when they change. The tenant part also links the AI Conformance page for DRA, Kueue and DCGM.The container row names the variant and not the bundle key. Since cozystack/cozystack#4101 the key accepts
container, but the container guide innext/still describes the old way, and I don't want the map to disagree with the page it points to.Left out on purpose, these need a real GPU node to check:
gpu=onlabel,NvLinkDisable)Also stale on main and not touched here: the gpu-sharing example still sets
spec.nodeGroupson the Kubernetes app, but worker pools moved to KubernetesNodes. And vgpu.md says the mdev table is filled whenever the variant isvgpu, while on main it also needsgpu.vgpuDeviceManager.enabled.Checked:
hugobuilds, all internal links on the v1.6 page resolve.