On 2018/6/10 13:27, Aleksandar Lazic wrote:
> Hi.
>
> On 10/06/2018 17:56, amotz wrote:
>> Baptiste wrote:
>>> Hi,
>>>
>>> what's the use case?
>>> Is this API gateway kind of thing?
>>>
>>> Baptiste
>>
>> From my experience this is mostly needed for operations/management API.
>>
>> Some examples
Hi.
On 10/06/2018 17:56, amotz wrote:
Baptiste wrote:
Hi,
what's the use case?
Is this API gateway kind of thing?
Baptiste
From my experience this is mostly needed for operations/management API.
Some examples:
getStaus (i.e get the status/health from all endpoint)
flashCache (make all endp
>From my experience this is mostly needed for operations/management API.
Some examples:
getStaus (i.e get the status/health from all endpoint)
flashCache (make all endpoint flash their cache)
setConfig (you get the point ...)
more...
with regard to the fan-in question by Jonathan.
Maybe return 207
On Sun, Jun 10, 2018 at 3:22 AM Baptiste wrote:
>
> Thanks for giving me this idea!
> I wrote a quick and inflexible one here:
> https://github.com/bedis/dnsserver
> So feel free to contribute to it or write your own :)
>
>
I'm going to use it to troubleshoot the issue you reported. That said,
>
Hey Baptiste,
On Sun, Jun 10, 2018 at 3:19 AM Baptiste wrote:
>
> ==> while writing this mail, I am able to reproduce the issue I think:
> - start HAProxy with SRV records
> - dump servers state
> - update haproxy conf to prevent dns resolution at runtime
> - reload haproxy
> ==> my servers are
On Sun, Jun 10, 2018 at 12:36 PM, Jonathan Matthews wrote:
> On 10 June 2018 at 08:44, amotz wrote:
> > I found myself needing the options to do "fantout" for a call. Meaning
> > making 1 call to haproxy and have it pass that call to all of the
> endpoint
> > currently active.
> > I don't mind
On 10 June 2018 at 08:44, amotz wrote:
> I found myself needing the options to do "fantout" for a call. Meaning
> making 1 call to haproxy and have it pass that call to all of the endpoint
> currently active.
> I don't mind implementing this myself and push to code review Is this a
> feature you
Hi Baptiste,
On Sun, Jun 10, 2018 at 09:27:09AM +0200, Baptiste wrote:
> Hi Willy,
>
> I don't see anywhere DNS over TCP mentioned.
I have reported what I'm aware people are currently working on, as you
know I don't want to speculate anymore about what would be nice to have
if someone was willin
I found myself needing the options to do "fantout" for a call. Meaning making
1 call to haproxy and have it pass that call to *all* of the endpoint
currently active.
I don't mind implementing this myself and push to code review Is this a
feature you would be interested in ?
Thanks,
Amotz
Hi Willy,
I don't see anywhere DNS over TCP mentioned.
>From my point of view (and integration with consul / kubernetes), it's an
important topic and I'd like to get it done by 1.9, ideally.
I have not checked yet how this could be implemented in HAProxy, but I
don't really feel comfortable to do
>
> I'm a little swamped with other work at the moment, but when I get a
> chance I would be able to provide a DNS server (written in Go) that returns
> additional records to test with if that helps.
>
Thanks for giving me this idea!
I wrote a quick and inflexible one here: https://github.com/bed
Hi Tait,
1. Reloading with SRV records ignores server-state-file
>
Can you tell me more about this one. How do you see that?
I mean, I have a conf similar to yours and I can see HAProxy parsing the
server state file (and returning a bunch of warning I'm working on about
backend name and ID mismat
12 matches
Mail list logo