Bug 1752422 - Modify computes configuration from balance-slb/A-S to balance-slb + LACP
Summary: Modify computes configuration from balance-slb/A-S to balance-slb + LACP
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openvswitch
Version: 10.0 (Newton)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Open vSwitch development team
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-16 10:37 UTC by Eduard Barrera
Modified: 2019-10-10 13:48 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-10 13:48:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.