Bug 1396602

Summary: Provide further insight into why LACP is "problematic and unsupported"
Product: Red Hat OpenStack Reporter: Kyle Squizzato <ksquizza>
Component: documentationAssignee: Martin Lopes <mlopes>
Status: CLOSED CURRENTRELEASE QA Contact: RHOS Documentation Team <rhos-docs>
Severity: low Docs Contact:
Priority: low    
Version: 8.0 (Liberty)CC: dsneddon, mlopes, srevivo
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-22 06:27:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Kyle Squizzato 2016-11-18 18:10:18 UTC
Description of problem:
Our documentation uses the following statement after mentioning any configurations having to do with LACP OVS-bonds: 

"Do not use LACP with OVS-based bonds, as this configuration is problematic and unsupported. Instead, consider using bond_mode=balance-slb as a replacement for this functionality. In addition, you can still use LACP with Linux bonding."

See: https://access.redhat.com/documentation/en/red-hat-openstack-platform/8/paged/director-installation-and-usage/appendix-g-open-vswitch-bonding-options

The only BZ I can find that's associated with LACP OVS-bonds that provides evidence of this "problem" is: BZ 1289825

The issue is, customers are opening cases wanting more information on "why" LACP is not recommended or unsupported.

If the above BZ is the reason for the note, then the documentation should be updated to reflect that issue (which is well on its way to being backported to RHOSP)

Comment 4 Martin Lopes 2016-11-22 06:19:43 UTC
Backported docs updates to osp9 and osp8.