Description of problem: Support for BF-2 in the NIC mode. Currently, BF-2 can operate in NIC mode and DPU mode that supports H/W acceleration via DPU. The customer requests support for BF-2 support in NIC mode. OP1 CRAWL mode: Basic datapath with BF2 OS (Ubuntu-based) in (separated) host mode The customer is planning to use BF-2 in host mode with basic datapath (OVS kennel, OVS-DPDK, and SR_IOV with host control) for OSP 17.1. Datapaths OVS, OVS-DPDK, HWOL and SR-IOV are supported and run on the host, with the host controlling the NIC. OSP does not need to deploy anything on the NIC or DPUs. OSP Director will need to boot x86 compute with RHEL but not be required to boot BF-2 with RHEL 8 for ARM? since it is not used in the datapath. This may be a security liability since OSP /RHEL are not managing the BF-2 boot-up or management. By default BF-2 cards ship with Bluefield-OS. BF-2 will need some Nvidia-provided initialization script to be run to verify BF-2 is up, with the right OS, firmware, and driver. Nvidia to support initialization and boot up for BF-2. Nvidia initialization script will change from default DPU (switchdev) mode to separated host mode, to enable the host to control NIC datapath. Enable separated host mode from DPU (ECPF default) mode. Run commands, power cycle, and verify host mode of operation Support for operation in NIC mode must be verified with OVN deployment for OVS, OVS-DPDK, and SR-IOV transport modes. Additionally, all the OVN testing applicable for OVN migration must be completed and verified for BF-2 in NIC mode with the exception of H/W offload. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
needs devel ack.