[Starlingx-discuss] [Containers] FYI: StarlingX SR-IOV CNI and device plugin images

Webster, Steven Steven.Webster at windriver.com
Wed May 29 23:04:45 UTC 2019


Hi All,

Just an FYI for users of the SR-IOV CNI plugins and/or those with private docker image repos.  StarlingX is now building images based on the plugins:

https://github.com/intel/sriov-network-device-plugin
https://github.com/intel/sriov-cni

The images can be found here:

https://hub.docker.com/r/starlingx/k8s-cni-sriov
https://hub.docker.com/r/starlingx/k8s-plugins-sriov-network-device

And are now being referenced here:

https://opendev.org/starlingx/config/src/branch/master/puppet-manifests/src/modules/platform/templates/sriov-cni.yaml.erb#L29
https://opendev.org/starlingx/config/src/branch/master/puppet-manifests/src/modules/platform/templates/sriovdp-daemonset.yaml.erb#L42

Users familiar with the feature should be aware that the DPDK netconf option of the NetworkAttachmentDefinition has been deprecated by sriov-cni [1].  As such, a user who wishes to use an SR-IOV interface in a pod with DPDK enabled virtual functions should bind the VFs to the vfio-pci module first.   To aid in this, the --vf-driver option of the host-if-modify command may be used [2].  For example:

# system host-if-modify -m 1500 -n sriov1 -d datanet1 -c pci-sriov -N 4 --vf-driver=vfio worker-1 ens801f1

Cheers,

Steve

[1] https://github.com/intel/sriov-cni/commit/ca31173989fa555320f2d29ca2757a321b2d6970
[2] https://opendev.org/starlingx/config/commit/13b142ff8ba25b6035b461218ef86d9fb14db2ad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20190529/f42585a6/attachment.html>


More information about the Starlingx-discuss mailing list