...
For Agent Load balancing functionality – please refer below spec
http://intranet.lab.vmops.com/engineering/release-2.2-features/agent-load-balancing?searchterm=agent
| Clustered MS configuration: |
SNO | Testcase Name | Procedure | Expected Results | Test Case Type ( Sanity | Functional |Negative) | is Automatable | Execution Time | Priority | Executed on Release | Reviewed By | Status | Comments | Is automatable | |||||||||
1 | Verify_Host_transition_states | 1. zone> pod1> cluster1 cluster2 cluster3 each with at least 1 host | 1. Check Host state change Alert-disconnect-Connecting-UP | SANITY, FUNCTIONAL | N |
| P1 |
|
|
|
|
| |||||||||
2 | Only_One MS_UP | 1. zone> pod1> cluster1 cluster2 cluster3 each with at least 1 host | 7. Able to access the MS UI from MS3 and all system vms up running. | SANITY, FUNCTIONAL | P1 Y |
| P2 |
|
|
|
|
| |||||||||
3 | All_MGMTServices_ | 3 | All_MGMTServices_UP_at_sameT |
| 3. Host clusters re-distributed to all 3 management servers. | FUNCTIONAL | Y |
| P2 |
|
|
|
|
| |||||||
4 | restart_ALL_MGMT services's | 1.MS1 MS2 MS3 each manage 1 cluster | All the MGMT server should up with out any erros and all hosts get distributed to corresponding MS's | FUNCTIONAL/Negative |
|
| P2 |
|
|
|
|
| |||||||||
5 | Change_SystemDate_ON_1MGMT Server | 1.Make sure each host is managed by each MGMT Server and | When one of the MS date is not synched management state in mshost should be down | FUNCTIONAL/Negative |
|
| P3 |
|
|
|
|
| |||||||||
6 | Perform_task_From_non-managed_MS | 1.host 1 is managed by MS1 | 1. task should be forward to managed MS(MS1) from MS2 and executed at MS1 and response should be received back to task initiator(i.e MS2) | SANITY, FUNCTIONAL | Y |
| P1 |
|
|
|
| ||||||||||
7 | Perform_Task_From_non-Managed MS_StopMS | 1.host 1 is managed by MS1 | Async Job shouldn't be in progress and it should be Done state. | FUNCTIONAL/Negative |
|
| P2 |
|
|
|
|
| |||||||||
8 | verify_ForwardAgent_becomes DA | 1.Stop MS1 | From MS2,Direct Agent Request transferred to MS2 from MS1 and Vm deployment should successful on MS2 | SANITY, FUNCTIONAL | Y(Its possible to automate but it s difficult judge which MS server takes the ownership if we have more than 2 MS ..always manual intervention required to get the accurate results for this cases) |
| P1 |
|
|
|
| errors | SANITY, FUNCTIONAL | P1 | |||||||
9 | verify ForwardAgent_functionality | 1.Stop the MS1 | 3.Request get forwarded to MS2 from MS3 and Vm deployment should successful on MS2. | SANITY, FUNCTIONAL | Y |
| P1 |
|
|
|
|
| |||||||||
10 | Host_Force_reconnect_From_non-managed MS | Find the management server that owns this host cluster. From | We should see the request being forwarded from non-managed MS to o the owner management server and the action should succeed. | FUNCTIONAL |
|
| P2 |
|
|
|
|
|
|
|
|
|
|
| the action should succeed. | FUNCTIONAL | P2 |
|
|
|
|
|
| ||||||||||||||||
11 | Host-maintenance_Mode_Mgmg_status | 1. On MS1 Put Host into maintenance mode | 1.Host should be maintenance mode with out any erros | SANITY, FUNCTIONAL |
|
| P2 |
|
|
|
|
| |||||||||
12 | Cancel_MaintenanceMode | 1.Select the Host from any MGMT server(say MS2) | 3.MGMT_ID should be Null | SANITY, FUNCTIONAL |
|
| P1 |
|
|
|
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
| ||||||||||||||||
13 | Take the Host out of maintenance Mode | Find the management server that owns this host. From any of the | We should see the requests for both the above actions being forwarded to the owner management server and the actions should succeed. | SANITY, FUNCTIONAL |
|
| P1 |
|
|
|
|
| |||||||||
14 | HostMaintenance_Join_MS | 1.MS1 Put its Host into maintenance mode | when Host is in maintenance mode ,agent load balancing won't happen. | FUNCTIONAL | Y |
| P2 |
|
|
|
|
| |||||||||
15 | Cancel_Maintenance_Join_MS | 1.Select the Host from any MS (Say MS1) and make sure the | 2..MGMT_ID should be Null | SANITY, FUNCTIONAL | Y |
| P2 |
|
|
|
|
| |||||||||
16 | StopMS1_Cancel_Maintenance Mode_fromMS2 | 1.Select the Host from any MGMT server(eg:MS1) | 3.MGMT_ID should be Null | SANITY, FUNCTIONAL | Y |
| P2 |
|
|
|
| ID | SANITY, FUNCTIONAL | P2 | |||||||
17 | AsyncJobState_StopMS_while_Job(Maintenance)_inProgress | 1.Select the Host owned by MGMT server(eg:MGMT 1) from MGMT Server MS 2 | Async job should not be in-progress state and its Job state should be done with FAILED. | SANITY, FUNCTIONAL | Y |
| P2 |
|
|
|
|
| |||||||||
18 | DeleteHost_from_other_MS | Find the management server that owns this host. From any of the other management servers ( that is NOT the | We should see the requests for both the above actions being forwarded to the owner management server and the | FUNCTIONAL | Y |
| P1 |
|
|
|
|
| |||||||||
19 | AsyncJobState_StopMS_while_Job(Snapshots)_inProgress | From the management server which is NOT the owner of the host in which the Vm is running , initiate a snapshot task. | Async job should get marked as done (FAILED) but it should not be in progress. | FUNCTIONAL | Y |
| P2 |
|
|
|
| . | FUNCTIONAL | P2 | |||||||
20 | AgentLB_HostState_UP_cluster_Disabled | 1. zone> pod1> cluster1 cluster2 cluster3 each with at least 1 host. all hosts state are in UP "agent.lb.enabled" true. MS1 manage 2 clusters. MS2 manage 1 cluster. | MS1 gives away 2nd cluster & Agent loadbalacing happens when hosts state is UP. | FUNCTIONAL |
|
| P1 |
|
|
|
|
| |||||||||
21 | AgentLB_HostState_Down_cluster_Disabled | 1. zone> pod1> cluster1 cluster2 cluster3 each with at least 1 host. all hosts state are in UP "agent.lb.enabled" true. MS1 manage 2 clusters. MS2 manage 1 cluster.2. MS1 unmanage 1 cluster >disable state and make sure state of the hosts are in disconnected state | No agent load balancing will trigger | FUNCTIONAL |
|
| P2 |
|
|
|
|
| |||||||||
22 | AgentLB_ThresHold_lessThan_default value | 1. zone> pod1> cluster1 cluster2 cluster3 each with at least 1 host. all hosts state are in UP "agent.lb.enabled" true. MS1 manage 2 clusters. MS2 manage 1 cluster.2.agent.load.threshhold =0.45 less than default thresh hold value(0.7) | No agent load balancing will trigger | SANITY, FUNCTIONAL |
|
| P1 |
|
|
|
|
| |||||||||
23 | AgentLB_ThresHold_moreThan_default value | 1. zone> pod1> cluster1 cluster2 cluster3 each with at least 1 host. all hosts state are in UP "agent.lb.enabled" true. MS1 manage 2 clusters. MS2 manage 1 cluster. | Agent load balancing will happen and host(selected host which are in giveway list) will get the new MGMT server ID | SANITY, FUNCTIONAL |
|
| P1 |
|
|
|
| ID | SANITY, FUNCTIONAL | P1 | |||||||
24 | AgentLB_ThresHold_moreThan_Non_default_ value | 1. zone> pod1> cluster1 cluster2 cluster3 each with at least 1 host. all hosts state are in UP "agent.lb.enabled" true. MS1 manage 2 clusters. MS2 manage 1 cluster.2. change the threshold is more than default thresh hold value(0.2) | Agent load balancing will happen and host(selected host which are in giveway list) will get the new MGMT server ID | FUNCTIONAL |
|
| P2 |
|
|
|
|
| |||||||||
25 | Direct agent-loads |
| 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. zone> pod1> cluster1 cluster2 cluster3 each with at least 1 host. all hosts state are in UP "agent.lb.enabled" true. MS1 manage 2 clusters. MS2 manage 1 cluster. | All hosts already transferred to MS2 should get new MGMT server ID. | FUNCTIONAL |
|
| P2 |
|
|
|
|
| |||||||||
27 | AgentLB_DestinationMS_Down_during_Rebalancing | 1. zone> pod1> cluster1 cluster2 cluster3 each with at least 1 host. all hosts state are in UP "agent.lb.enabled" true. MS1 manage 2 clusters. MS2 manage 1 cluster. | 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. | FUNCTIONAL |
|
| P2 |
|
|
|
| P2 | |||||||||
27 | dbServer_ UsageServer on different machines | 1. configure cluster management setup and Make sure database and usage on separate machine | In all the cases usage statistics should be collected and details should be accurate | SANITY, FUNCTIONAL |
| 6 Hrs | P1 |
|
|
|
|
| |||||||||
29 | dbServer_ UsageServer on _Same_Machines | 1. configure cluster management setup and Make sure database and usage on the machine | In all the cases usage statistics should be collected and details should be accurate | SANITY, FUNCTIONAL |
| 3 hrs | P1 |
|
|
|
|
| |||||||||
30 | Ping Timeout | 1.make sure all the MS's are synch | 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 | Upgrade should be successful,able to perform basic sanity cases(Agent load balancing &Direct agent and forward agent functionality) | SANITY, FUNCTIONAL |
| 12 hrs for each upgrade | P1 |
|
|
|
|
|
Q&A:
1) When the cluster is disabled(Hosts are in UP state) ,does the agent load balancing will happen?
...