Hi,
> Hi, > > My answers inline. > > On Tue, Dec 17, 2013 at 9:14 AM, Annika Wickert > <[email protected]> wrote: >> - One global statssocket which can be switched through to see stats of every >> bind process. And also an overall overview summed up from all backends and >> frontends. >> - One global control socket to control every backend server and set them >> inactive or active on the fly. >> - In general better nbproc > 1 support > > Will be fixed once we have a real multiprocess mode in HAProxy. Sounds cool :). > >> - CPU pinning in haproxy without manually using taskset/cpuset > > already here, check the cpu-map feature. Sorry, didn’t find it ;). > >> - sflow output > > Can't log-format already do this? Sure, but it might be a better integration in the rest of networking infrastructure if sflow is supported. > >> - latency metrics at stats interface (frontend and backend, avg, 95%, 90%, >> max, min) > > interesting ideas > >> - accesslist for statssocket or ldap authentication for stats socket > > chown is your friend here. Sorry meant auth for HTTP but wrote statssocket :x. Never type faster than you think ;). > >> Are there any others things which would be cool? I hope we can have a nice >> discussion about a “fancy” feature set which could be provided by lovely >> haproxy. > > Caching, HTTP auth using LDAP, etc :) Caching would be nice. But putting haproxy before varnish is ok. > > Baptiste Annika
