Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1752422

Summary: Modify computes configuration from balance-slb/A-S to balance-slb + LACP
Product: Red Hat OpenStack Reporter: Eduard Barrera <ebarrera>
Component: openvswitchAssignee: Open vSwitch development team <ovs-team>
Status: CLOSED NOTABUG QA Contact: Eran Kuris <ekuris>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 10.0 (Newton)CC: apevec, bperkins, chrisw, mcroce, njohnston, rhos-maint, twilson
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-10 13:48:36 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:
Embargoed:

Description Eduard Barrera 2019-09-16 10:37:56 UTC 
Description of problem:

Customer wants to perform the following changes during the upgrade to OSP13:

""
During the upgrade to OSP13 in production customer wants to change in all clusters the bonding configuration related to the provider network from  balance-slb/A-S to balance-slb + LACP for all computes on the Nova (OVS kernel) and  DPDK (OVS-DPDK) availability zones.
""

I know there are some OVS + LACP problems going on, so I would like to have some feedback from engineering about this step. Would you suggest as well perfrom the change to LACP before the upgrade, or first perfrom the upgrade and then update the network configuration ?

Version-Release number of selected component (if applicable):
OSP12 -> OSP13
Comment 1 Matteo Croce 2019-10-01 15:32:43 UTC 
It depends on the OVS version, if 2.9+ then LACP is supported fine, even with balance-slb. LACP with 2.6 is a no-go
Comment 2 Terry Wilson 2019-10-10 13:48:36 UTC 
Going ahead and closing since the answer was given. If more info is needed, please re-open.