I think you might have misunderstood. By "adding new server", I mean to add it as a server in HAProxy configuration. That is, the effect is to add the "server" line for the new server into the config file. This has nothing to do with launching the server in the cloud. It is the reverse of marking a server DOWN, except that the server being marked UP was not originally included in the list of servers for the HAProxy backend.
On Jan 9, 2013, at 4:21 PM, Zachary Stern <[email protected]> wrote: > > > On Wed, Jan 9, 2013 at 4:13 PM, Kevin Heatwole <[email protected]> wrote: > 4. Adding new server to backend by having configuration check return new > server configuration. > > I don't know about the other features, but this one I think violates the UNIX > philosophy of "do one thing and do it well". There are already plenty of > tools you can use to achieve this with HAproxy, like puppet or chef, and > things like the ruby fog gem for cloud provisioning, etc. > > > -- > > zachary alex stern I systems architect > > o: 212.363.1654 x106 | f: 212.202.6488 | [email protected] > > 60-62 e. 11th street, 4th floor | new york, ny | 10003 > > www.enternewmedia.com >
