...
Note that agent LB has nothing to do with load balancing of API requests. These needs to be handled separately by means of an external load-balancer sitting in front of the MS cluster.
The load calculation for comparing with the load threshold (agent.load.threshold) is done using the following logic.
Load = (Managed routing hosts) / (All routing hosts)
The average host per MS is calculated using the following logic.
Average host count = (Managed routing hosts) / (# of MS in 'Up' state)
Routing host : Host type is set to 'Routing' in host table DB
Managed routing host : Host is owned by a MS (MS id is set in host table in DB)
MS state : Refer to mshost table in DB for the state of each MS
...
3.6) Get all the requests from the transfer attache.
3.7) Create forward attache
3.8) RouteToPeer all the requests
3.9) Finsih Finish rebalance by deleting the entry in op_host_transfer map
agent.lb.enabled - Enable agent load balancing between management server nodes. Defaulted to false, i.e. agent LB is disabled
agent.load.threshold - Percentage of the agents that can be held by one management server before load balancing happens. Defaulted to 70%
A new table op_host_transfer is added to keep track of agent transfers
Applicable for all directly managed agents like XenServer, Vmware, Simulator
None
None
...