Add DPDK support to host-device plugin [oversight]

Goal

The main goal is for Openshift pods/containers CNFs (DPDK applications) to have bare-metal networking performance on secondary interfaces with OpenStack fast datapath (FDP) services including OVS-DPDK, SR-IOV, PCI passthru, OVS HW offlaod , when using OpenShift on OpenStack

SDN Team oversight/review

Request for oversight and/or review from Openshift SDN team to bring in support host-device plugin for DPDK pod network attachment

https://github.com/containernetworking/plugins/pull/490
https://bugzilla.redhat.com/show_bug.cgi?id=1989342
https://coreos.slack.com/archives/CH98TDJUD/p1628529206294200?thread_ts=1626967171.128200&cid=CH98TDJUD

Feature Overview

Make host-device plugin as a placeholder for a DPDK device when applications wants to attach the host-device with a pod container through network attachment definition.

Name of feature: Add DPDK support to the host-device plugin

Feature Details

The feature allows PCI devices that have been bound to a non-kernel driver to be attach to a pod. The feature skips actions tied to kernel netdev (e.g. IPAM) in a similar way as the SR-IOV CNI plugin. Kubernetes users would not need to use a special CNI plugin (i.e. NO-OP) when using virtio-net devices bound to the vfio driver.

Business Justification

Enables the use of accelerated OVS/OVN-dpdk interfaces in a Shift on Stack deployment.

Business impact

Needed to support existing and new NFV/Telco customers on OpenStack and Shift on Stack

The feature has already been implemented upstream and this request to include the upstream feature in the downstream release.

https://github.com/containernetworking/plugins/pull/490