EC2 auto registration
Common practice is to do this the right scale / IBM way.
When a backend server is launched via autoscaling then it makes an ssh
remote command call to the loadbalancer calling an api script that adds the
backend to the running haproxy configuration.
By all means steal t
Hi Holger,
thanks for the answer. I already assemble HA-Proxy configuration with the help
of Puppet. Now things require a bit more logic fe. I dont want to restart
HA-Proxy if the config that ships with the RPM does not change. I'll definitely
have a look at your script - thanks for the pointer
Jens,
Many people have a script that builds a working configuration file from
various bits and pieces. As the actual needed configuration typically
isn't something which follows a common path but depends on the
environment and the actual applications and a thousand other bits, there
isn't a standa
Hi Baptiste,
sorry for my wording. But you are right, with "registration" I mean
- add ACL
- add use_backend
- add backend section
so to sum it up "make haproxy aware of a new application".
There might be cases there I want to "only" add a server to existing backend,
but that would be the second
Hi Jens,
What do you mean by "registration"?
Is that "make haproxy aware of the freshly deployed application" ?
cheers
On Wed, Aug 3, 2011 at 5:46 PM, Jens Bräuer wrote:
> Hi HA-Proxy guys,
>
> I wonder whats the current state of the art to automate the registration of
> backend. My setup run
Hi HA-Proxy guys,
I wonder whats the current state of the art to automate the registration of
backend. My setup runs in on EC2 and I run HA-Proxy in front of local
applications to easy administration. So a typical config file would be like
this.
frontend http
bind *:8080
acl is-auth
6 matches
Mail list logo
