Am 10-04-2017 20:19, schrieb Willy Tarreau:
On Mon, Apr 10, 2017 at 05:00:14PM +0200, Baptiste wrote:
On Mon, Apr 10, 2017 at 2:30 PM, Willy Tarreau <[email protected]> wrote:
> On Mon, Apr 10, 2017 at 10:02:29AM +0200, Frederic Lecaille wrote:
> > With server templates, haproxy could preallocate 'server' objects which
> > would derive from 'default-server' (with same settings as default server
> > settings), but with remaining parameters which are unknown at parsing
> time
> > (for instance their names, addresses, anything else). In fact here,
> names or
> > addresses are particular settings: a default server has not any default
> name
> > or default address.
>
> Absolutely. And this combined with the recent features of dynamic
> consistent
> cookies and with Baptiste's upcoming DNS patches will easily result in
> pretty
> dynamic backends!
>
> Willy
>
>
I just had a look at the implementation of server-templates. To make
it
work with DNS resolution, we need to find a way to provide a fqdn to
the
default-server directive. This might not be too complicated.
I hadn't thought about this one, good point. At least as a first step
you'll just have to use the same fqdn for all servers (and thus
templates).
We definitely want it to be changeable over the CLI.
Thanks all for explanation.
In case I have understood you all right I will be able to add and remove
servers without reloading/restarting haproxy just with some cli
commands, right.
That would be very great ;-)
Will be this also possible for listen/frontend/backend in the next step.
This will be a big challenge because there are so much combinations and
permission issues which can create a lot or headache 8-O
regards
Aleks
