Open Stack

If you choose to use DNS round robin, you can set TTL small and use a
script/tool to continous check proxy nodes to reconfigure DNS record if one
proxy node goes down, and vice-versa.

If you choose to use SW load-balancer, I suggest HAProxy for performance
(many high-traffic websites use it) and NGinx for features (if you really
need features provided by Nginx).
IMHO, I like Nginx more than Haproxy. It's stable, modern, high
performance, and full-featured.


On Fri, Jun 7, 2013 at 6:28 AM, Kotwani, Mukul <mukul.g.kotwani at hp.com>wrote:

>  Hello folks,****
>
> I wanted to check and see what others are using in the case of a Swift
> installation with multiple proxy servers for load balancing/distribution.
> Based on my reading, the approaches used are DNS round robin, or SW load
> balancers such as Pound, or HW load balancers. I am really interested in
> finding out what others have been using in their installations. Also, if
> there are issues that you have seen related to the approach you are using,
> and any other information you think would help would be greatly appreciated.
> ****
>
> ** **
>
> As I understand it, DNS round robin does not check the state of the
> service behind it, so if a service goes down, DNS will still send the
> record and the record requires manual removal(?). Also, I am not sure how
> well it scales or if there are any other issues. About Pound, I am not sure
> what kind of resources it expects and what kind of scalability it has, and
> yet again, what other issues have been seen.****
>
> ** **
>
> Real world examples and problems seen by you guys would definitely help in
> understanding the options better.****
>
> ** **
>
> Thanks!****
>
> Mukul****
>
> ** **
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130607/5b58f076/attachment.html>