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

Re: [OpenShift OSE3] multi-tenant Load balancer question




----- Original Message -----
> From: "Dejardin Sylvain" <Sylvain Dejardin ebrc com>
> To: dev lists openshift redhat com, openshiftbeta redhat com
> Sent: Tuesday, May 5, 2015 6:05:39 AM
> Subject: [OpenShift OSE3] multi-tenant Load balancer question
> 
> Hello Everybody,
> 
> Question regarding load balancer other than the default one HA proxy,
> another one like Load balancer Big IP F5.
> Why using F5 ? It is the frontend we are using also as (WAF / Web
> Application Firewall)
> 
> In OSE2 : only one pool is used to be managed by openshift OSE2 in order to
> address a load balancer F5 type, for multi-tenancy purpose it is a problem
> for us.
> In OSE3 : having more than one pool is possible? or a configurable pool
> dedicated per client or per application is it possible?

That kinda sounds like a router config implementation detail. What is the significance of a pool?

I suspect OpenShift v3 doesn't really care. Each route is going to have a set of IP:port endpoints that are reachable on the SDN; the master exposes these via an API and that's the end of OpenShift's involvement really. Your router listens to the master for route creation/modification events and updates proxy configuration accordingly. You simply point DNS at your routing layer and it proxies external connections into connections on the SDN.

If you want to create a pool for every route, I don't see why you couldn't do it that way. But if you want to talk F5 specifics, we might want to loop in Miciah, who's been working on an F5 implementation of the routing layer.

> Thanks,
> Best regards,
> 
> Sylvain Déjardin  Senior Middleware Engineer – Linux & Application
> Services
>  Tél. +352 26 06 1 sylvain dejardin ebrc com
> EBRC  5, rue Eugène Ruppert, L-2453 Luxembourg  www.ebrc.com
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 


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