 So, I thought it would be useful to do a run-through of a new feature of vCloud Director and that's Load Balancing. So, it's freely available in vCloud Director 5.1 and 5.5. This demo we're using our Cloud Platform at edu-serve which is running vCloud Director 5.1. The configuration for Load Balancing is really simple. Here I've deployed a vApp. In that vApp there are two CentOS 6 virtual machines both running Apache and I've taken note of the internal IP address of both of those machines because we'll need that in part of the configuration in a minute. If we head over to the administration tab and edit the services of the Edge Gateway device for the VDC where the vApp is deployed, the first thing that we need to do is add a firewall rule. For the demonstration I'm just looking at port 80 traffic so I've added a firewall rule that allows port 80 traffic straight through to the virtual IP address which is effectively the internet IP address that will be the edge of the Load Balancing service. Once I've done that we can go over to the Load Balancer tab and the first action we need to do is add servers to the pool. The pool is effectively just the web servers which will receive traffic sent to the virtual IP address which was the Edge IP address that we've just set up in the firewall. So, if I add a new pool, very original name and in this demonstration I'm only going to be looking at HTTP traffic but it can support HTTPS and other forms of TCP ports. Again for the demonstration I'm only going to be using round robin but other Load Balancing algorithms are supported such as IP, hash, URI and least connected. So if we select next and for the demonstration again I'm just going to use the Monitor Port 80 and I'm going to set these intervals to a lower value just so that it's slightly quicker during the failover for the demonstration and I'm going to leave the URI for the HTTP service as the default. So the first thing we do is add the IP address of the first node that we want to balance the connections through to. So that was 3.2 and Port 80 and again Monitor Port 80 on that server as well and then add the second server in, 2.6.8.3.6 and again Port 80 and Port 80 and once we've set that up we'll head over to the Virtual Service tab and add in a new name for the VIP address again very original and add the edge IP address that we configured for the firewall and enable it for Port 80 traffic. Again I'm not going to use any session persistence for this but Cookie is supported so I'll inject Cookie and try and pass the user back to the same node if that cookies presented again. Click OK and this takes a couple of seconds for it to configure the VShield Edge device but once that's done you'll be able to see we should be able to hit that and effectively flop between the two web servers that are part of that balance so that's finished configuring. So if we refresh this web page we should see that we alternate between the two web servers in the balance. So if we head back over to VCloud Director and go to the Vapp and do something fairly crucial to the running of the second web server and that's power it off and we'll just wait a couple of seconds for this to complete and once that's powered off effectively traffic should be only sent and as we can see here only sent to the first web server thus providing continuity for the service. So that's VCloud Director 5.1 and load balancing thank you very much.