Oh missed that; cool.  Sorry for my mistake with your name while
multitasking as well :)

On Mon, Feb 6, 2012 at 4:52 PM, Jeff Buchbinder <
[email protected]> wrote:

>  There is an API text file in the root of the git repo with some more 
> information. I try to keep it sync'd with Willy's upstream copy.
>
> carlo flores <[email protected]> wrote:
>
>
> John,
>
>  Where's the documentation for your patch?  I'm up for playing with this
> neat idea even if we don't use it in Prod.
>
>  Might hook in some suff to haproxyctl if you can output a version
> number/patch/something so the ctl script can recognize when someone is
> using this version...
>
> On Mon, Feb 6, 2012 at 4:39 PM, Jeff Buchbinder <
> [email protected]> wrote:
>
>> The api patch I have been working on at
>> https://github.com/jbuchbinder/haproxy has that functionality, but needs
>> more testing.
>>
>> Willy has said that he has no plans to include this patch, primarily due
>> to the potential for configuration issues in dynamically configured
>> frontends, backends, etc.
>>
>> Thanks,
>> Jeff
>>
>> Ivan Ator <[email protected]> wrote:
>>
>>
>> Going from the documentation, there doesn't appear to be functionality
>> for creating/destroying backends.
>>
>> Personally, I have accomplished your task by creating a series of
>> scripts for maintaining the configuration file and reloading it while
>> live.
>>
>> On 2/6/2012 3:21 PM, Dziuba, Ted wrote:
>> > Hi,
>> >
>> > I am wondering if it possible to create an haproxy backend
>> > programmatically, using the unix socket facility. I see that you can
>> > enable and disable existing back-ends, but I want to add a new one. This
>> > is my use case:
>> >
>> > HTTP server starts on a host, binding to port 0
>> >
>> > HTTP server announces itself to a load balancer, asking to be put into
>> > the pool
>> >
>> > Load balancer acknowledges HTTP server and starts sending it traffic
>> >
>> > Thanks,
>> >
>> > Ted
>> >
>> > ---
>> >
>> > Ted Dziuba
>> >
>> > Co-Founder, Milo.com
>> >
>> > [email protected]
>> >
>>
>>
>>
>

Reply via email to