Browse Source

Update DPDK docs with note about using veth pairs

In case when ovs-dpdk is used together with ``ovs_use_veth`` config
option set to True, it cause invalid checksum on all packets send from
qdhcp namespace.
This commit adds short info about this limitation to ovs-dpdk config
guide.

Change-Id: I6237abab3d9e625440e95e75f5091d09a1ec44f0
Related-Bug: #1832021
tags/15.0.0.0b1
Slawek Kaplonski 4 months ago
parent
commit
051b58f566
1 changed files with 7 additions and 0 deletions
  1. 7
    0
      doc/source/admin/config-ovs-dpdk.rst

+ 7
- 0
doc/source/admin/config-ovs-dpdk.rst View File

@@ -152,3 +152,10 @@ Known limitations
152 152
   will not function.
153 153
 * Expect performance degradation of services using tap devices: these devices
154 154
   do not support DPDK. Example services include DVR, FWaaS, or LBaaS.
155
+* When the ``ovs_use_veth`` option is set to ``True``, any traffic sent
156
+  from a DHCP namespace will have an incorrect TCP checksum.
157
+  This means that if ``enable_isolated_metadata`` is set to ``True`` and
158
+  metadata service is reachable through the DHCP namespace, responses from
159
+  metadata will be dropped due to an invalid checksum. In such cases,
160
+  ``ovs_use_veth`` should be switched to ``False`` and Open vSwitch (OVS)
161
+  internal ports should be used instead.

Loading…
Cancel
Save