Skip to content

docs: separate host DPU policy from observed device mode#3473

Open
chet wants to merge 1 commit into
NVIDIA:mainfrom
chet:gh-issue-3472
Open

docs: separate host DPU policy from observed device mode#3473
chet wants to merge 1 commit into
NVIDIA:mainfrom
chet:gh-issue-3472

Conversation

@chet

@chet chet commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

The provisioning, ingestion, Flat VPC, glossary, metrics, and admin CLI docs now use HostDpuPolicy::{Manage, UseAsNic, Ignore} for desired behavior and BlueFieldOperatingMode::{Dpu, Nic} for observed hardware state.

Existing dpu_mode fields, flags, values, and protobuf/Redfish names are called out as backwards-compatible boundaries rather than the canonical vocabulary.

This is the separately reviewed documentation companion to #3453 and should merge after that code PR.

Validation:

  • cargo make format-nightly
  • cargo make clippy
  • cargo make carbide-lints
  • git diff --check

This supports #3472

@chet chet requested a review from polarweasel as a code owner July 14, 2026 05:20
@coderabbitai

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: dc27e666-2346-468d-af30-5146cdd5961b

📥 Commits

Reviewing files that changed from the base of the PR and between 1eb3a7f and 421d8d3.

📒 Files selected for processing (9)
  • docs/development/new_hardware_support.md
  • docs/glossary.md
  • docs/index.yml
  • docs/manuals/nico-admin-cli/commands/expected-machine/expected-machine-add.md
  • docs/manuals/nico-admin-cli/commands/expected-machine/expected-machine-patch.md
  • docs/manuals/vpc/flat_vpcs_zero_dpu.md
  • docs/observability/core_metrics.md
  • docs/provisioning/boot-interfaces-and-dpu-modes.md
  • docs/provisioning/ingesting-hosts.md

Walkthrough

The documentation adopts dpu_policy terminology, defines host policy and observed operating mode concepts, updates CLI and provisioning examples, and documents legacy compatibility mappings.

Changes

DPU policy documentation

Layer / File(s) Summary
Policy terminology and host configuration
docs/glossary.md, docs/provisioning/ingesting-hosts.md, docs/observability/core_metrics.md
Defines host DPU policies and BlueField operating modes, updates zero-DPU terminology, documents per-host inheritance and legacy aliases, fixes export formatting, and aligns the migration metric description.
CLI and zero-DPU operator guidance
docs/manuals/nico-admin-cli/commands/expected-machine/*, docs/manuals/vpc/flat_vpcs_zero_dpu.md
Replaces documented --dpu-mode usage with --dpu-policy, defines supported values, and updates Flat VPC procedures and verification steps.
Provisioning policy workflows
docs/provisioning/boot-interfaces-and-dpu-modes.md, docs/index.yml
Updates provisioning defaults, resolution rules, scenarios, boot handling, troubleshooting, navigation wording, and CLI references for dpu_policy.
Development workflow documentation
docs/development/new_hardware_support.md
Clarifies consistent boot-interface MAC usage across hardware validation steps and adjusts mock-coverage formatting.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related issues

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the core documentation change: separating host DPU policy from observed device mode.
Description check ✅ Passed The description is directly aligned with the documented policy/mode terminology changes and the companion PR context.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands.

@chet

chet commented Jul 14, 2026

Copy link
Copy Markdown
Contributor Author

@coderabbitai full_review, thanks!

@coderabbitai

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

@chet Sounds good, I'll perform a full review of all the changes in this PR.

ʘ‿ʘ

✅ Action performed

Full review finished.

@github-actions

Copy link
Copy Markdown

@github-actions

Copy link
Copy Markdown

🔍 Container Scan Summary

No Grype artifacts were found to aggregate.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/manuals/vpc/flat_vpcs_zero_dpu.md`:
- Around line 103-143: Update all listed documentation sites to use the existing
DpuMode/dpu_mode contract until the policy rename lands: replace dpu_policy,
HostDpuPolicy, and --dpu-policy guidance with the current dpu_mode/DpuMode names
and CLI values, while preserving legacy behavior descriptions. Apply the
corresponding updates in docs/manuals/vpc/flat_vpcs_zero_dpu.md (lines 103-143,
73-74, and 416-418), docs/glossary.md (lines 54-61 and 159),
docs/provisioning/ingesting-hosts.md (line 192),
docs/manuals/nico-admin-cli/commands/expected-machine/expected-machine-add.md
(lines 19-20, 117-131, and 164), and expected-machine-patch.md (lines 20-21,
123-137, and 170).

In `@docs/provisioning/boot-interfaces-and-dpu-modes.md`:
- Around line 53-73: The guide must match the implemented DPU-policy contract:
document legacy dpu_mode and --dpu-mode names with their mappings, and use
accepted CLI flags and payload fields. Update
docs/provisioning/boot-interfaces-and-dpu-modes.md lines 53-73, 97, 115,
129-137, 148-152, 161-165, 174-181, and 197-200; retain
ExpectedMachine.dpu_mode, correct the add and patch flags, update all zero-DPU,
NIC-mode, and managed-DPU payloads, and correct the admin-CLI reference table.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 25e4efc6-d359-4d69-8126-1474e6bbb303

📥 Commits

Reviewing files that changed from the base of the PR and between da30d63 and 664d165.

📒 Files selected for processing (9)
  • docs/development/new_hardware_support.md
  • docs/glossary.md
  • docs/index.yml
  • docs/manuals/nico-admin-cli/commands/expected-machine/expected-machine-add.md
  • docs/manuals/nico-admin-cli/commands/expected-machine/expected-machine-patch.md
  • docs/manuals/vpc/flat_vpcs_zero_dpu.md
  • docs/observability/core_metrics.md
  • docs/provisioning/boot-interfaces-and-dpu-modes.md
  • docs/provisioning/ingesting-hosts.md

Comment thread docs/manuals/vpc/flat_vpcs_zero_dpu.md
Comment thread docs/provisioning/boot-interfaces-and-dpu-modes.md

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/provisioning/boot-interfaces-and-dpu-modes.md`:
- Around line 63-67: Update the `manage` row in the JSON/TOML and CLI policy
table so it describes DPU lifecycle management without requiring DPU/Admin boot.
State that DPU/Admin is the default boot path only when no plain-NIC primary
interface is declared, while preserving the existing inheritance behavior for
per-host `manage` declarations.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: d30fb5b5-5753-4503-8729-5437ce1d358d

📥 Commits

Reviewing files that changed from the base of the PR and between da30d63 and 664d165.

📒 Files selected for processing (9)
  • docs/development/new_hardware_support.md
  • docs/glossary.md
  • docs/index.yml
  • docs/manuals/nico-admin-cli/commands/expected-machine/expected-machine-add.md
  • docs/manuals/nico-admin-cli/commands/expected-machine/expected-machine-patch.md
  • docs/manuals/vpc/flat_vpcs_zero_dpu.md
  • docs/observability/core_metrics.md
  • docs/provisioning/boot-interfaces-and-dpu-modes.md
  • docs/provisioning/ingesting-hosts.md

Comment thread docs/provisioning/boot-interfaces-and-dpu-modes.md
The provisioning, ingestion, Flat VPC, glossary, metrics, and admin CLI docs now use `HostDpuPolicy::{Manage, UseAsNic, Ignore}` for desired behavior and `BlueFieldOperatingMode::{Dpu, Nic}` for observed hardware state.

Existing `dpu_mode` fields, flags, values, and protobuf/Redfish names are called out as backwards-compatible boundaries rather than the canonical vocabulary.

This supports NVIDIA#3472

Signed-off-by: Chet Nichols III <chetn@nvidia.com>
@chet

chet commented Jul 14, 2026

Copy link
Copy Markdown
Contributor Author

@coderabbitai full_review, thanks!

@coderabbitai

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

@chet Understood, kicking off a full review of the PR once more.

ʘ‿ʘ

✅ Action performed

Full review finished.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant