Re: [PATCH 0/2] openssl 1.1 async mode and engine support

Hi Grant, On Thu, Jan 19, 2017 at 11:27:43PM -0800, Grant Zhang wrote: > Hi Willy, > > Thank you very much for your review! > > WRT engine configuration, I agree with your point of finer control over > which crypto ops get handled by hardware engine vs. software. It is possible > to

Re: [PATCH 0/2] openssl 1.1 async mode and engine support

Hi Willy, Thank you very much for your review! WRT engine configuration, I agree with your point of finer control over which crypto ops get handled by hardware engine vs. software. It is possible to load/initialize engines using openssl configuration file, which is documented in

Dynamically adding server's to backend

Hello, What do you think about making possible to add servers to backend at runtime via CLI/socket? Changing addresses and wieghts of servers is ok, because we can use "placeholders", but it's not the best solution and requires to configure many placeholders when it comes to autoscaling. This

Propagating agent-check weight change to tracking servers

Hello, We use track's in haproxy to minimize check traffic in some situations and after my last patch we are probably going to switch to agent-checks for live management of weights and statuses. One problem I see now - track don't propagate weight setting to trackers, so if we set agent-check on

Re: HAProxy Lua Map.end & reserved keywords

Hi. Just a quick message: I don't forget this bug, I'm just just very busy. Thierry Le 12 janvier 2017 10:54:42 AM "Robin H. Johnson" a écrit : On Wed, Jan 11, 2017 at 12:17:26PM +0100, Willy Tarreau wrote: On Mon, Jan 09, 2017 at 08:47:17PM +, Robin H.

Re: [PATCH 0/2] openssl 1.1 async mode and engine support

Hi Grant, sorry for the longer delay than what I expected. I rebased your work on top of the latest development tree so that it's easier to review since it's where it's ultimately going to get merged. First I have a question regarding the engines configuration. I still have a pretty similar

Re: Status code "-1" in logs

Hello John Thank you for your clarification, I guess its an easy mistake to make when you see a 503 and assume its the error when I knew you were talking about the "-1" issue. Regards Andrew Smalley Loadbalancer.org Ltd. On 19 January 2017 at 00:24, Skarbek, John