https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETVIRT-133 netvirt <p>Old netvirt iterated over the interfaces in bridge, and set the bridge type to netdev if it found a dpdk interface.</p> <p>New vpnservice netvirt has a configuration flag (ovsdb.userspace.enabled) to determine the same (this is problematic as it doesn't allow usage of different types of OVS)</p> <p>The first option isn't ideal because we might have br-int bridge that has no dpdk port, but has a patch port connected with dpdk bridge, and thus has to be a dpdk bridge as well.</p> <p>Operating System: All<br/> Platform: All</p> NETVIRT-133

when mixing dpdk & non-dpdk OVS with the same ODL - no way to configure different datapath types

Bug Resolved Done Tali Ben-Meir Koby Aizer Sun, 11 Sep 2016 12:33:55 +0000 Wed, 21 Sep 2016 15:50:10 +0000 Wed, 21 Sep 2016 15:50:10 +0000 Boron General 0 2 <p>the logic for determining which datapath type to use is implemented in ovsdb according to old netvirt implementation (iterates on Open_vSwitch table iftypes and look for dpdk). The global configuration is only relevant when the dpdk iftype is missing. <br/> To summarize, no code change is required.</p> <p>Race between br-int creation and iface-type retrieval from Open_vSwitch table in OVSDB<br/> Suggested solution: attempt to create br-int only after iface-type exist</p> Development External issue ID 6690 External issue URL Rank 0|i01px3: