Bug 1462339 - Documentation Bug: OSP 11 NVF configuration guide missing "Two-Port OVS-DPDK Bonding with VXLAN" Tun Section
Documentation Bug: OSP 11 NVF configuration guide missing "Two-Port OVS-DPDK ...
Status: CLOSED WONTFIX
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director (Show other bugs)
11.0 (Ocata)
x86_64 Linux
medium Severity low
: ---
: ---
Assigned To: Sandra McCann
Yariv
: Triaged, ZStream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-16 15:15 EDT by Chris Paquin
Modified: 2017-11-14 12:58 EST (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Feature: Two-Port OVS-DPDK Bonding with VXLAN Reason: Result:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-11-14 12:58:42 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Chris Paquin 2017-06-16 15:15:25 EDT
Description of problem:

The document below [1] appears to be missing documentation pertaining to the scenario in the BZ Summary

[1]https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11/html-single/network_functions_virtualization_configuration_guide/

The following scenarios are outlined in the document.


1. Configure Single-Port OVS-DPDK with VLAN Tunnelling

2. Configure Two-Port OVS-DPDK with VLAN Tunnelling

3. Configure Two-Port OVS-DPDK Data Plane Bonding with VLAN Tunnelling

4. Configure Single-Port OVS-DPDK with VXLAN Tunnelling

Should we also not document the scenario below?

Configure Two-Port OVS-DPDK with VXLAN Tunnelling
Comment 2 Franck Baudin 2017-11-14 12:58:42 EST
We cannot document all combinations, as long as we have VxLAN and bonding separate documentation, as long as they work properly fine together, and we're assuming so until a bug is open, we don't need to write such documentation. I hope that it make sense, so I'm closing this bug, feel free to reopen if I missed something, thanks! Maybe a Kbase article or a blogpost would be a better fit, just to show that we can make it work by following in sequence bonding and VxLAN doecumentation.

Note You need to log in before you can comment on or make changes to this bug.