OVS DPDK representor port always use system datapath_type

Bug #1879890 reported by Junbo Jiang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
os-vif
New
Undecided
Unassigned

Bug Description

Hi,

I follow the link https://docs.openstack.org/neutron/train/admin/config-ovs-offload.html, it use system datapath_type, and it works well, after I change the ovs to ovs-dpdk, the os-vif still plug the vf port to br-int, see below

    Bridge br-int
        Controller "tcp:127.0.0.1:6633"
        fail_mode: secure
        datapath_type: netdev
        Port int-br-ex
            Interface int-br-ex
                type: patch
                options: {peer=phy-br-ex}
        Port "ens2f1_2"
            Interface "ens2f1_2"
        Port br-int
            Interface br-int
                type: internal

as you can see the datapath_type use netdev now, it should use the below command,

ovs-vsctl add-port br0 dpdk-rep3 -- set Interface dpdk-rep3 type=dpdk \
   options:dpdk-devargs=0000:08:00.0,representor=[3]

see http://docs.openvswitch.org/en/latest/topics/dpdk/phy/

solution

I will patch the code to fill datapath_type field in _get_ovs_representor_port_profile in nova/network/os_vif_util.py

Junbo Jiang (junbo)
Changed in neutron:
assignee: nobody → junbo (junbo)
Revision history for this message
Maciej Jozefczyk (maciejjozefczyk) wrote :

Hey Junbo,

do you think that is Neutron bug even you pointed that Nova should be patched to include datapath_type?

Revision history for this message
Junbo Jiang (junbo) wrote :

Oh, I don't why I post the bug in neutorn.. should I close this and open an new bug in nova?

Revision history for this message
Slawek Kaplonski (slaweq) wrote :

Hi,

No need to open new bug. I just changed affected project in this one.

no longer affects: neutron
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.