[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: HAproxy gears and HA apps across data centers




On 30/05/2014 11:32 pm, "Clayton Coleman" <ccoleman redhat com> wrote:
>
>
>
> > On May 30, 2014, at 9:26 AM, Luke Meyer <lmeyer redhat com> wrote:
> >
> > I'm looking for clarity on what happens in the routing behind HA apps. If I've made an app HA and it has two+ haproxy gears, does each HAproxy route requests to all available gears, or to a subset of them?
>
> Today it's all of them.
>
> >
> > This is relevant to designing an app that spans multiple data centers for HA in case one DC is offline. If I set up nodes in each DC as a separate zone, causing the app to span DCs when scaled up, would requests from HAproxy gears be proxied only to gears in the same DC or randomly to all of them? Generally the former would seem preferable to minimize bandwidth use, but I can foresee some issues with that and suspect it's the latter.
>
> All - if you need distinct routing groups with isolated traffic, you can create multiple apps with the same alias and dns balance across them.
>
> >
> > I suspect the only good way to approach this scenario is to have the routing layer proxy directly to each gear, bypassing the gear-level LBs. Or to set up separate apps in separate regions, but that's extra administrative hassle. Am I on the right track?
>
> If you want to deeply control routing,  proxying directly to gears from a router is the natural extension.
>

If we have this scenario with external LB. Does openshift bring up new gears if it notices a node has gone offline?  Does auto scaling also still work, or was that dependent on the haproxy gear?
> >
> > _______________________________________________
> > dev mailing list
> > dev lists openshift redhat com
> > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
>
> _______________________________________________
> dev mailing list
> dev lists openshift redhat com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]