I was wondering this myself (we use F5) but if he doesn&#39;t have the budget for a  redundant pair of F5&#39;s )they are pricey...) then he may be trying to get resilience this way....<br><br>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....<br>
<br><div class="gmail_quote">2010/1/8 nate <span dir="ltr">&lt;<a href="mailto:centos@linuxpowered.net">centos@linuxpowered.net</a>&gt;</span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><a href="mailto:avi@myphonebook.co.in">avi@myphonebook.co.in</a> wrote:<br>
<br>
&gt; Is this the end of the road, for installing apache as a service with ONE<br>
&gt; public IP<br>
&gt; address??<br>
<br>
</div>You sure you have the right solution? Using RHCS for web serving<br>
seems really complicated, I would use a load balancer instead. Myself<br>
I have most experience with F5 gear but there is LVS on linux(never<br>
used it). With load balancers you can often offload things like<br>
SSL, compression, etc. It makes life much easier for scaling, since<br>
you can have multiple systems serving content for the same public<br>
IP, and add/remove more at will, really trivial to manage.<br>
<br>
Depends on the size of your cluster..<br>
<br>
<a href="http://www.redhat.com/docs/manuals/csgfs/browse/rh-cs-en/pt-lvs.html" target="_blank">http://www.redhat.com/docs/manuals/csgfs/browse/rh-cs-en/pt-lvs.html</a><br>
<font color="#888888"><br>
nate<br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
CentOS mailing list<br>
<a href="mailto:CentOS@centos.org">CentOS@centos.org</a><br>
<a href="http://lists.centos.org/mailman/listinfo/centos" target="_blank">http://lists.centos.org/mailman/listinfo/centos</a><br>
</div></div></blockquote></div><br>