That said a single front end apache server with mod_proxy and load balanced across N nodes (depending on front end firewall too) might be simpler overall....
2010/1/8 nate <centos@xxxxxxxxxxxxxxxx>
avi@xxxxxxxxxxxxxxxxx wrote:You sure you have the right solution? Using RHCS for web serving
> Is this the end of the road, for installing apache as a service with ONE
> public IP
> address??
seems really complicated, I would use a load balancer instead. Myself
I have most experience with F5 gear but there is LVS on linux(never
used it). With load balancers you can often offload things like
SSL, compression, etc. It makes life much easier for scaling, since
you can have multiple systems serving content for the same public
IP, and add/remove more at will, really trivial to manage.
Depends on the size of your cluster..
http://www.redhat.com/docs/manuals/csgfs/browse/rh-cs-en/pt-lvs.html
nate
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
_______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos