Re: Multiplexing multiple services behind one agent (feature suggestion; patch attached)

2015-11-03 Thread James Brown
Attached is a `git-format-patch`-formatted patch with some extra strduping and freeing. On Fri, Oct 30, 2015 at 11:39 PM, Willy Tarreau wrote: > Hi James, > > On Wed, Oct 28, 2015 at 10:27:22AM -0700, James Brown wrote: > > Sorry for being thickheaded, Willy, but what's your

Re: Multiplexing multiple services behind one agent (feature suggestion; patch attached)

2015-11-03 Thread Willy Tarreau
On Tue, Nov 03, 2015 at 03:12:59PM -0800, James Brown wrote: > Attached is a `git-format-patch`-formatted patch with some extra strduping > and freeing. Thank you. I've just removed the two unneeded "if != NULL" before the free(), and merged it. Willy

Re: Multiplexing multiple services behind one agent (feature suggestion; patch attached)

2015-10-31 Thread Willy Tarreau
Hi James, On Wed, Oct 28, 2015 at 10:27:22AM -0700, James Brown wrote: > Sorry for being thickheaded, Willy, but what's your decision here ??? do you > want me to make it per-Backend instead of per-Server, or do you want to > merge it as-is? Well, I think we can take it as-is then. The

Re: Multiplexing multiple services behind one agent (feature suggestion; patch attached)

2015-10-28 Thread James Brown
Sorry for being thickheaded, Willy, but what's your decision here — do you want me to make it per-Backend instead of per-Server, or do you want to merge it as-is? I'm glad to defer completely to your judgement on this. On Thu, Oct 22, 2015 at 1:12 PM, Willy Tarreau wrote: > On

Re: Multiplexing multiple services behind one agent (feature suggestion; patch attached)

2015-10-22 Thread Willy Tarreau
On Thu, Oct 22, 2015 at 11:37:47AM +0200, Baptiste wrote: > This is interesting. Yep, that's in line with the HTTP option to send some server info with HTTP checks (name, weight and I don't remember what). > That said, I'm suggesting an improvement: use the log format varialble. No, please no!

Re: Multiplexing multiple services behind one agent (feature suggestion; patch attached)

2015-10-22 Thread James Brown
It would be... more convenient for my use case to be able to encode the string in the config (we may have several backends for a different service to correspond to phased deployment rollouts, and I'd prefer to encode the logic for mapping backend name to service name in my existing haproxy config

Re: Multiplexing multiple services behind one agent (feature suggestion; patch attached)

2015-10-22 Thread James Brown
That would definitely be more useful, although it would also require rewriting a lot of the code around how log variables are interpolated. Right now, it looks like interpolation is pretty tightly tied to the actual act of logging (the build_logline function is pretty attached to the idea of

Re: Multiplexing multiple services behind one agent (feature suggestion; patch attached)

2015-10-22 Thread Willy Tarreau
On Thu, Oct 22, 2015 at 01:04:28PM -0700, James Brown wrote: > It would be... more convenient for my use case to be able to encode the > string in the config (we may have several backends for a different service > to correspond to phased deployment rollouts, and I'd prefer to encode the > logic

Re: Multiplexing multiple services behind one agent (feature suggestion; patch attached)

2015-10-22 Thread Baptiste
On Thu, Oct 22, 2015 at 3:59 AM, James Brown wrote: > Hello haproxy@: > > My name is James Brown; I wrote a small piece of software called hacheck > (https://github.com/Roguelazer/hacheck) which is designed to be a healthcheck > proxy for decentralized load balancer control

Multiplexing multiple services behind one agent (feature suggestion; patch attached)

2015-10-21 Thread James Brown
Hello haproxy@: My name is James Brown; I wrote a small piece of software called hacheck (https://github.com/Roguelazer/hacheck) which is designed to be a healthcheck proxy for decentralized load balancer control (remove a node from a load balancer without knowing where the load balancers are;