Page History

...

1. Configure the direct.agent.load.size =2
2. make sure 3 hosts should be consider for rebalacning
3. check the number of hosts consider for rebalancing at same time | As per the configured  load size(2),At same time 2 hosts should be consider(processed) for re-balancing. | FUNCTIONAL | Y | | | |

   26	AgentLB_sourceMS_down_during_Re-balancing	1. In multi clustered Env, make sure all hosts  state is UP(eg:cluster1 with 4 hosts) and "agent.lb.enabled" should be set to "true 2.Join the another MGMT server 3.during agent load balancing,stop the source MGMT server(MS1)	All hosts already transferred to MS2 should get new MGMT server ID.	FUNCTIONAL		P2
   27	AgentLB_DestinationMS_Down_during_Rebalancing	1. In multi clustered Env, make sure all hosts  state is UP(eg:cluster1 with 4 hosts)) and "agent.lb.enabled" should be set to "true 2.Join the another MGMT server(MGMTServer 2) 3.during agent load balancing(from MS1 to MS2),stop the destination MGMT server(MHMT server 2)	If M2 dies, all re balancing should be stopped as it's running on M2. All hosts already transfered to M2 should be marked as Disconnected.	SANITY, FUNCTIONAL		P1
   28	dbServer_ UsageServer on different machines	1. configure cluster management setup and Make sure database and usage on separate machine 2.Deploy VM's on Host2 and generate usgae traffic from one management server  MGMT 2 on the GuestVMs.(download some  files from internet into guestVMs) 3.check the network usage statistics 4.stop the current Mangement server i.e MGMT 2 5.check the network statistics 6.From another management server ,generate public traffic and check the network usage statistics	In all the cases usage statistics should be collected and details should be accurate	SANITY, FUNCTIONAL		P1
   29	dbServer_ UsageServer on _Same_Machines	1. configure cluster management setup and Make sure database and usage on the machine 2.Deploy VM's on Host2 and generate usgae traffic  from one management server  MGMT 2 on the GuestVMs.(download some  files from internet into guestVMs) 3.check the network usage statistics 4.stop the current Management server i.e MGMT 2 5.check the network statistics 6.From another management server ,generate public traffic and check the network usage statistics	In all the cases usage statistics should be collected and details should be accurate	SANITY, FUNCTIONAL		P1
   30	Ping Timeout	1.make sure all the MS's are synch 2.On one management remove or comment the IPtable rule for 9090 port(to make sure MS communication failed with ping timed out but still other MS's can communicate to common mysql DB)	once ping command timeouts,The corresponding MS will be disconnect state and host on the current MS(M2) will get the another management ID(MS3 ID)	Negative
   31	Upgrade test(2.2.14 to Bonita and 3.0 to Bonita)	1.prepare the cluster management setup before upgrade 2. perform basic operations(vm life-cycle,snapshots) 3.make sure before host ownership changed from MS1 to MS2 4.Upgrade the all the Management Servers in the cluster management-setup 5.check after upgrade able to perform basic sanity test	Upgrade should be successful, able to perform basic sanity  cases(Agent load balancing &Direct agent and forward agent functionality)	SANITY, FUNCTIONAL		P1

1) When the cluster is disabled(Hosts are in UP state) ,does the agent load balancing will happen?

       A) In the disabled cluster,If hosts are UP, they'll be considered for re-balancing

2) How the agent load balancing works on remote agents or is it specific to direct agents only ?

      A) Its Specific to direct agents only.

3) Is agent load balancing is hypervisor specific or its same for all the agents

     A) Behavior is same for all  the supported Hypervisors

4) How to restrict the host to same management ID

   A) Current design its not possible to  restrict the  host to same management ID \[Not advisable because if the management server dies no re-balancing happen \]

5)If host is rebalanced and move from M1->M2->M3 and when we stop MS service on M3  ..how it will determine future_owner_id(assuming both M1

&M2 has 1 host each)

  A ) Agent rebalancing happens just on the management server start, never on stop. So when new management server joins the cluster ,it asks other MS to give the hosts away. That's when rebalancing happens. When MS leaves the cluster, all its agents are marked as Disconnected, and will be picked up by other management server. It's a separate process called Direct agent scan.

6) During agent rebalancing(M1 to M2) if M2 server is down suddenly what is the expected behavior ..does it look for other MS(MS3) first to   rebalanced(based on calculation) or host is stick to Ms1.

  A) If M2 dies, all rebalancing should be stopped as it's running on M2. All hosts already transfered to M2 should be marked as Disconnected.

7) Agent load balancing happen only when any Ms joins /start & stop of cloud-management service or does it happened regular intervals

A) Only on MS join (start of MS)

8) When we perform host reconnect ..does the agent load balancing triggers

A) No.

9) what  is the significance of the Global configuration parameters( Direct.agent.load.size &thresh hold ) related agent LB

  A) Direct.agent.load.size - determines how many concurrent reconnects we can perform. So if 32 hosts were considered for rebalancing, 16 of them will be processed at the same time.

0.7 threshold - don't start agent rebalance if there are less than 70% of host in UP state in the entire MS cluster.

(Thanks to Alena for providing Answers to above questions)