--Norton-- wrote:
Whilst it is true that the network load balancer can balance the network requests across the 2 or more cells from what I've read only one of those cells can actually utilise vCenter and the other cells mearly off load there requests via it at intervals?
Sort of. For each vCenter server, there's (in normal operation) 1 cell designated as a vCenter proxy (listed in the "vCenter Proxy" column on the vCenters page of the Manage & Monitor section of the UI). That cell is responsible for listening to updates from the vCenter server. Other cells should be able to perform other communication with the vCenter.
The best consolidated documentation I know of is actually buried in a post (on another topic) on Tom Fojta's blog: Graceful Shutdown of vCloud Director Cell
--Norton-- wrote:
This was seen on one of my environments when requests were being made to create new machines and delete them via the VCD interface but a 5 min (300 second) wait time was seen between each set of 2 tasks in vCenter.
That's... odd. Is this in an otherwise idle system? What version of vCloud Director are you using? It's probably worth filing a support request to get someone to take a look at your environment.
--Norton-- wrote:
What was happening was that the requests were going via the second cell server. The cell server that was NOT listed as the proxy cell server within VCD.
That's fine. The cell which handles the REST API (or UI) request to initiate an operation isn't necessarily the cell that performs the operation (a sort-of load balancing of operations; even if you trigger numerous operations from one cell, actual execution will be balanced across the server group).