Let’s give operators one clear vocabulary for choosing how NICo treats host DPU hardware. The docs should consistently use HostDpuPolicy::{Manage, UseAsNic, Ignore}, distinguish that desired policy from BlueFieldOperatingMode::{Dpu, Nic}, and spell out the backwards-compatible inputs that existing deployments can keep using.
What this involves
- Update provisioning, ingestion, Flat VPC, and glossary docs from operating-mode language to host-policy language.
- Explain the separation between desired host policy and observed BlueField operating mode.
- Document why protobuf and Redfish boundaries retain the legacy
DpuMode and NicMode names.
- Refresh the
nico-admin-cli expected-machine reference for --dpu-policy and its legacy --dpu-mode alias.
- Keep
core_metrics.md aligned with the policy-oriented site-explorer metric description.
Companion documentation for #3447.
Let’s give operators one clear vocabulary for choosing how NICo treats host DPU hardware. The docs should consistently use
HostDpuPolicy::{Manage, UseAsNic, Ignore}, distinguish that desired policy fromBlueFieldOperatingMode::{Dpu, Nic}, and spell out the backwards-compatible inputs that existing deployments can keep using.What this involves
DpuModeandNicModenames.nico-admin-cli expected-machinereference for--dpu-policyand its legacy--dpu-modealias.core_metrics.mdaligned with the policy-oriented site-explorer metric description.Companion documentation for #3447.