dpdk-bond-mappings could accept PCI address

Bug #1903732 reported by Michał Ajduk
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
charm-ovn-chassis
Triaged
Wishlist
Unassigned

Bug Description

Currenly ovn-chassis dpdk-bond-mappings accepts a list of all MAC addresses of all DPDK NICs. In case of multiple nodes of the same type this list grows (2*node count).

It would be nice if the charm allowed specifying PCI address directly which in this case, if all the nodes are the same, would allowing cleaner and simpler configuration.

Revision history for this message
Frode Nordahl (fnordahl) wrote :

Thank you for the bug. I will triage this as wish list on the charm because it is a new feature request, please don't view it as feedback on how important we think your request is.

FWIW; the current DPDK implementation in the ovn-*-chassis and neutron-openvswitch charms is pre-deprecated awaiting support for setting the required values through the Netplan.io OVS support. If DPDK-support and features is important to you and your project I would aim the focus at getting attention on adding proper support for it in Netplan.io.

Changed in charm-ovn-chassis:
status: New → Triaged
importance: Undecided → Wishlist
Revision history for this message
Gábor Mészáros (gabor.meszaros) wrote :

I believe the relevant code to extend is in the charmhelpers:
https://github.com/juju/charm-helpers/blob/master/charmhelpers/contrib/openstack/context.py#L2600

in the PCINetDevices class there is already a function to get_device_from_pci_address()
https://github.com/juju/charm-helpers/blob/master/charmhelpers/contrib/hardware/pci.py#L276

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.