yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #82752
[Bug 1879890] Re: OVS DPDK representor port always use system datapath_type
Hi,
No need to open new bug. I just changed affected project in this one.
** Also affects: os-vif
Importance: Undecided
Status: New
** No longer affects: neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1879890
Title:
OVS DPDK representor port always use system datapath_type
Status in os-vif:
New
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/os-vif/+bug/1879890/+subscriptions
References