Bug 1010708

Summary:	Recommended way to bypass single HAProxy
Product:	OpenShift Container Platform	Reporter:	Arthur Enright <aenright>
Component:	RFE	Assignee:	jofernan
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	2.2.0	CC:	bleanhar
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-02-04 14:33:26 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 Arthur Enright 2013-09-22 17:19:45 UTC

In our non-cloud deployment, we have an F5 load balancer in front of two or more Apache servers running mod_proxy.

The single HAProxy implementation for a scaled application represents a single point of failure which we would like to resolve.

Does Red Hat have a suggested way of eliminating the single point of failure?

Options I've thought of (but not had time to test):

a.) allowing multicast broadcast to mod_cluster.

b.) tracking the gears by following the HAProxy config file.

c.) tracking the gears by subscribing to some event in ActiveMQ.

I'm open to discussions are ideas here.

Comment 3 Brenton Leanhardt 2014-02-04 14:33:26 UTC

This was addressed in the 2.0 release with External Load Balancing:

https://access.redhat.com/site/documentation/en-US/OpenShift_Enterprise/2/html-single/Deployment_Guide/index.html#sect-External_Load_Balancing

If you feel there is something else required please let us know.