feat: dpf: Sync to VR0.6 nightly#3302
Conversation
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
|
Caution Review failedAn error occurred during the review process. Please try again later. Summary by CodeRabbit
WalkthroughThis PR pins the DOCA source repository to a specific commit in the DPF build config and updates DPF SDK, flavor, harness, and type code to match newly optional/added fields in CRD-generated structs (bfb, flavor, DpuFlavorSpec, DpuDeviceSpec, DpuStatus, service templates, interfaces), including test and helper adjustments and a new DpuStatusPhase mapping. ChangesDOCA Source Pinning
CRD-Generated Struct Shape Alignment
Estimated code review effort: 3 (Moderate) | ~25 minutes Possibly related PRs
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
DPF nightly commit version: 84bc3187cfdae715e862e2af9356cfac5689265d
3b036a2 to
f8cec3c
Compare
|
@coderabbitai review |
🔍 Container Scan Summary
Per-CVE detail lives in the per-service |
|
What if this code runs on a DPF that's not upgraded to 84bc3187cfdae715e862e2af9356cfac5689265d? |
|
You said that DPF is backward compatible, but NICo needs to be Forward compatible. |
DPF nightly commit version: 84bc3187cfdae715e862e2af9356cfac5689265d
As per DPF team, current nightly does not break 26.4 API (except
DpfOperatorConfig, which is not handled by NICo). This is the only way as of now to test BF4 with NICO.Next PR will contain the changes to introduce
BluefieldSoftwarealong withbfb_url. For BF4, bfb_url is not used, but BluefieldSoftware field is used.Related issues
Type of Change
Breaking Changes
Testing
Additional Notes