On Mon, Jul 23, 2012 at 8:48 AM, Eugen Leitl <[email protected]> wrote:
> We have to setup the pools and virtual servers feature, it’s a > nice-to-have to set up the “monitors” option which is also available (more > about that in the To Do paragraph and the end of this article). > > In the pools options you have to configure which vCloud Director cells are > available tot the load balancer. You have to define a separate pool for the > web interface and a seperate pool for the console proxy. The screendump > shows the configuration for the vCloud Director web interface pool: > > Define a name for the pool, configure the portnumber (443) and add both > vCloud director cells to this pool. I’ve configured ICMP as a monitor > option, this means a ping is send to a vCD cell to check it’s up and > running. Although this is not a very thorough test (the OS of a cell is up > and running, but the vCD service is down, the load balancer will still > think the cell is available), this option is fine for this first setup. > How much traffic are you able to push thru the load balancer, and what is your CPU load? I found (and others have too) that if you are pushing your CPU that the load balancer crumbles under that pressure, and you end up with very very slow page loads and connections, and many timeouts for clients. I recently put a very very high-powered pair of servers in service as my pfSense firewall (replaced a dual ALIX system), so need to re-evaluate this again. Right now I am just using port-forwards to a single back end.
_______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
