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

Bug 1788993

Summary: [RFE] Support Controller HA deployment across multiple L2 networks / Multirack-HA
Product: Red Hat OpenStack Reporter: Darin Sorrentino <dsorrent>
Component: puppet-pacemakerAssignee: Luca Miccini <lmiccini>
Status: CLOSED DUPLICATE QA Contact: pkomarov
Severity: high Docs Contact:
Priority: high    
Version: 17.0 (Wallaby)CC: aherr, bdobreli, chjones, djuran, dsneddon, eelena, jjoyce, jschluet, lmiccini, ltomasbo, mariel, michele, nlevinki, pneedle, slinaber, spower, tvignaud
Target Milestone: AlphaKeywords: FutureFeature, Reopened, TechPreview, Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2059983 (view as bug list) Environment:
Last Closed: 2022-10-14 10:21:51 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:
Bug Depends On: 2059983    
Bug Blocks: 1895458    

Comment 7 Anthony Herr 2020-03-31 14:21:18 UTC
I understand the need for a solution to this problem.  With Spine & Leaf configurations, and customers asking for using L3 at the top of rack switches, there needs to be a way to enable this configuration with Pacemaker. To properly set expectations, this request will not be developed into new capabilities within the product but I would like to leave this RFE open until we work through a solution to this problem and include it within the BZ.

Comment 8 Anthony Herr 2020-04-07 22:32:33 UTC
My understanding is that the suggestions to make this work across L3 configurations including VLANs, and network routes.
We will be looking into these as solutions to this configuration.

If there are alternatives that the customer would like to suggest, please add this information detail into the case.

Comment 11 Luca Miccini 2020-07-30 07:23:44 UTC
*** Bug 1356627 has been marked as a duplicate of this bug. ***

Comment 17 spower 2021-11-30 10:53:35 UTC
This needs to go through the exception process to be included in OSP 17 as it missed the Nov 25th date to be in POST/Modified