add support for ovs 2.7 port binding.
Bug #1662289 reported by
sean mooney
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-ovs-dpdk |
Fix Released
|
High
|
jaroslavx.safka | ||
Ocata |
Won't Fix
|
Critical
|
Unassigned |
Bug Description
ovs 2.7+ nolonger use the dpdkX naming scheme and now requires
the pciadress to be passed when adding dpdk interfaces.
old:
ovs-vsctl --no-wait --may-exist add-port $bridge "dpdk${
new:
ovs-vsctl --no-wait --may-exist add-port $bridge $nic -- set Interface $nic type=dpdk options:
networking-ovs-dpdk should be modifed to support both the old and new form.
Changed in networking-ovs-dpdk: | |
assignee: | nobody → jaroslavx.safka (jaroslavx-safka) |
Changed in networking-ovs-dpdk: | |
status: | Triaged → In Progress |
To post a comment you must log in.
this should be completed before the ocata branch is created.
the ocata branch will track dpdk 16.11 and ovs 2.7 branches.