On 25/11/2012, at 3:13 PM, Tomasz Kuzemko <[email protected]> wrote:
> Hello, > I'm working on a project with a similar setup and would like to use ATS as a > reverse proxy with caching. > > My "PoOS" hosts thousands of domains, so I configured ATS as an open relay > and made a plugin to authorize requests based on a whitelist of backend IP > addresses. > > For now I used option 2) for a simple round robin LB on PoOS, but in the > future I may need a more sophisticated solution, for example with stickiness. > > So my question is about the balancer plugin - why exactly is it broken? It has a bunch of dependencies on Yahoo infrastructure that were never open sourced. > Does the planned rewrite by Alan have an ETA? The plugin works by making an IPC call to a balancing service. We would need to evaluate and choose a suitable service, then implement the balancer IPC calls or implement a full balancer. I guess that what I'm saying is that there's not actually much load balancing code in the balancer plugin ;) > > -- > Tomasz Kuzemko > [email protected] > > W dniu 22.11.2012 17:36, Leif Hedstrom pisze: >> On 11/22/12 6:06 AM, deepak srinivasan wrote: >>> Hello, >>> We are working on a project which uses ATS as the main component of >>> the design. >>> We wanted to do a setup like LOAD BALANCERS --> POOL OF ATS SERVERS >>> --> POOL OF ORIGINS SERVER. >>> From some discussion on the mailing list we came to know that this is >>> not possible. >>> Would request if some one can put a light on this and guide me if its >>> possible or not. >>> would like to know if remap.config or any other config file will help >>> me achieve ATS to forward 1 single HTTP request to multiple Origin >>> servers. >>> We are using ATS v 3.2 >>> >> >> You have a few options: >> >> 1) Create a DNS entry for the "Pool of Origin Servers" (PoOS from now on >> ;), with multiple A-records. ATS will round-robin across those IPs, and >> detect connect failures etc. >> >> 2) Use the Parent Proxy config (parent.config), and add your PoOS >> machines there. >> >> 3) Write a simple plugin that does something intelligent when setting >> the destination address of the PoOS. This is how the (broken!) balancer >> plugin works, it's just not fully open sourced. >> >> -- Leif >> >> >> P.s >> 3) needs some serious loving, not only from the plugin perspective, but >> from the fact that we don't integrate nicely with our DNS cache, health >> checks, or how to handle failures (such as allowing it to try a >> different machine upon failures, calling the plugin again). Alan M. >> Carroll has promised he will rewrite all this, and we all get ponies >> too. Thanks Alan! >> >> P.p.s >> That was a wee bit of Thanksgiving fun at the end. We get no ponies :/. >>
