Generic backend in HAProxy config with server options as placeholders

2018-11-13 Thread Vijay Bais
Hello, We have a requirement wherein a single generic backend with server options configured as placeholders, which will resolve on the fly or at runtime. Currently, we have to define multiple backends (has to be hardcoded) and select them using the *use_backend* keyword. Kindly help us with

[PATCH] CLEANUP: fix typos in reg-tests

2018-11-13 Thread Joseph Herlant
Hi, This patch fixes typos in comments and error messages of reg-tests. Note that this has not been qualified as minor as it is used for testing purposes, not end-users. Let me know if I need to re-qualify the patch as MINOR (and split it as one part is comment, one part is info messages). The

[PATCH] CLEANUP: fix a misspell in tests/filltab25.c

2018-11-13 Thread Joseph Herlant
Hi, This is the only typo detected in the tests, so leaving it for a patch of its own. The patch is attached, but if you want to view the diff online, you can check: https://github.com/haproxy/haproxy/compare/master...aerostitch:cleanup_tests_typo Thanks for your help, Joseph From

[PATCH] MINOR: fix typos in the examples files

2018-11-13 Thread Joseph Herlant
Hi, This patch deals with typos in the example files. To be more specific the error 500 example page and the transparent_proxy.cfg page. For the later, it is all in the comments but still user-visible as those are examples. I wasn't sure if you consider the examples files as documentation or

[PATCH] CLEANUP: fix typos in comments in ebtree

2018-11-13 Thread Joseph Herlant
Hi, This patch is mainly about misspells of the word "occurrence" in the code of ebtree. The misspells are only located in code comments. The patch is attached, but if you want to view the diff online, you can check: https://github.com/haproxy/haproxy/compare/master...aerostitch:ebtree Thanks

[PATCH] DOC: Fix typos in different subsections of the documentation

2018-11-13 Thread Joseph Herlant
Hi guys, Fix typos found in the design-thoughts, internals and lua-api subsections of the documentation. Note: I split the whole documentation typos patch in 2 to make it more readable but those can be merged if preferred of course. The patch is attached, but if you want to view the diff

[PATCH] DOC: fix a few typos in the documentation

2018-11-13 Thread Joseph Herlant
Hi guys, This commit deals with a few misspells in the documentation. One point I'm not sure in the following sentence is if the "unsed" should be "used" or "unset" (from doc/SPOE.txt): The engine name must be uniq for a proxy. If no engine name is provided on the SPOE filter line, the SPOE

Re: OCSP stapling with multiple domains

2018-11-13 Thread Igor Cicimov
On Sun, Nov 11, 2018 at 2:48 PM Igor Cicimov wrote: > Hi, > > # haproxy -v > HA-Proxy version 1.8.14-1ppa1~xenial 2018/09/23 > Copyright 2000-2018 Willy Tarreau > > I noticed that in case of multiple domains and OCSP setup: > > # ls -1 /etc/haproxy/ssl.d/*.ocsp >

Re: Balance based on network/cpu load

2018-11-13 Thread Aaron West
Hi Jessy, We made an opensource feedback agent which you can use if you like, it'll save you the need to make anything: https://www.loadbalancer.org/blog/open-source-windows-service-for-reporting-server-load-back-to-haproxy-load-balancer-feedback-agent/ Aaron West Loadbalancer.org Ltd.

Re: Balance based on network/cpu load

2018-11-13 Thread Pavlos Parissis
On 13/11/18 9:37 π.μ., Bruno Henc wrote: > Hello, > > > Not sure if there is a direct way to do this, but you can always create a > monitoring process that > will use the haproxy runtime API to MAINT or DRAIN a server until the CPU / > network load drops. So > you have a simple watchdog

Re: [PATCH] HTTP 103 response (Early Hints)

2018-11-13 Thread Willy Tarreau
On Tue, Nov 13, 2018 at 09:48:03AM +0100, Frederic Lecaille wrote: > Thank you for having pointed out this issue (fixed by this new patch > attached to this mail). Merged, thank you. Willy

Re: [PATCH] HTTP 103 response (Early Hints)

2018-11-13 Thread Frederic Lecaille
On 11/13/18 7:48 AM, Aleksandar Lazic wrote: Hi Fred. Hello Aleksandar, Sorry to be picky but I still think that there is some missing text in the documentation, as mentioned before. http://git.haproxy.org/?p=haproxy.git;a=commitdiff;h=06f5b6435ba99b7a6a034d27b56192e16249f6f0 MINOR: doc: 

Re: Balance based on network/cpu load

2018-11-13 Thread Bruno Henc
Hello, Not sure if there is a direct way to do this, but you can always create a monitoring process that will use the haproxy runtime API to MAINT or DRAIN a server until the CPU / network load drops. So you have a simple watchdog process which reads the output from your monitoring tools to

Balance based on network/cpu load

2018-11-13 Thread Jessy van Baal
Hi there! Is there a way that HAProxy 1.8 can balance based on the network or CPU load on the backend servers? Let's say, a backend server has 90% CPU usage, it gets out of the load balancing pool for a while until it gets stable. Thanks in advance. Yours sincerely, Jessy van Baal