[NETVIRT-133] when mixing dpdk & non-dpdk OVS with the same ODL - no way to configure different datapath types Created: 11/Sep/16 Updated: 21/Sep/16 Resolved: 21/Sep/16 |
|
| Status: | Resolved |
| Project: | netvirt |
| Component/s: | General |
| Affects Version/s: | Boron |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Koby Aizer | Assignee: | Tali Ben-Meir |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 6690 |
| Description |
|
Old netvirt iterated over the interfaces in bridge, and set the bridge type to netdev if it found a dpdk interface. 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) 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. |
| Comments |
| Comment by Ravit Peretz [ 13/Sep/16 ] |
|
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. |
| Comment by Tali Ben-Meir [ 19/Sep/16 ] |
|
Race between br-int creation and iface-type retrieval from Open_vSwitch table in OVSDB |