|
| Clustered MS configuration: |
|
---|
SNO | Testcase Name | Procedure | Expected Results | Test Case Type( Sanity | Functional |Negative) | is Automatable | Priority | Pass/Fail | |||
---|---|---|---|---|---|---|---|---|---|---|
1 | Verify_Host_transition_states | 1. Add each Host to each cluster and make sure each host managed by each MGMT server | 1. Check the Host state changed | SANITY, | N | P1 | PASS | |||
2 | Only_One MS_UP | 1.Make sure each host is managed by each management server | a)Able to access the MS UI from MS3 | SANITY, | Y | P2 | PASS | |||
3 | All_MGMTServices_UP_at_sameTime | 1.Make sure each host is managed by MGMT server | Hosts should get re-distributed to all the 3 management servers. deployVM should be successful without | FUNCTIONAL | Y | P2 | PASS | |||
4 | restart_ALL_MGMT services's | 1.Make sure each host is managed by each MGMT server | All the MGMT server should up | FUNCTIONAL/ |
| P2 | PASS | |||
5 | Change_SystemDate_ON_1MGMT Server | 1.Make sure each host is managed by each MGMT Server | When one of the MS date is not synched | FUNCTIONAL/ |
| P3 | PASS | |||
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, | Y | P1 | PASS | |||
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/ |
| P2 | PASS | |||
8 | verify_ForwardAgent_becomes DA | 1.Stop the MS1 | From MGMT2,Direct Agent Request transferred to MGMT2 from MGMT1 and Vm deployment should | SANITY, FUNCTIONAL | Y(Its possible to automate | P1 | PASS | |||
9 | verify ForwardAgent_functionality | 1.Stop the MS1 | 3.Request get forwarded to MGMT2 from MGMT3 and Vm deployment should successful on MS2. | SANITY, FUNCTIONAL | Y | P1 | PASS | |||
10 | Host_Force_reconnect_From_non-managed MS | Find the management server that owns | We should see the request | FUNCTIONAL |
| P1 | PASS | |||
11 | Host-maintenance_Mode_Mgmg_status | 1.Select the Host from any MGMT server(says MS1) 2.Put the Host into maintenance mode | 2.Host should be maintenance mode | SANITY, FUNCTIONAL |
| P2 | PASS | |||
12 | Cancel_MaintenanceMode | 1.Select the Host from any MGMT server(say MS2) 2.Put the Host into maintenance mode | 3.MGMT_ID should be Null | SANITY, FUNCTIONAL |
| P1 | PASS | |||
13 | Take the Host out of maintenance Mode | Find the management server that owns this host. | We should see the requests for both | SANITY, FUNCTIONAL |
| P1 | PASS | |||
14 | HostMaintenance_Join_MS | 1.Select the Host from any MGMT server | when Host is in maintenance | FUNCTIONAL |
| P2 | PASS | |||
15 | Cancel_Maintenance_Join_MS | 1.Select the Host from any MGMT server(Say MS1) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 2..MGMT_ID should be Null | SANITY, FUNCTIONAL | Y | P2 | PASS | |||||
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 | PASS | |||
17 | AsyncJobState_StopMS_while_Job(Maintenance)_inProgress | 1.Select the Host owned by MGMT server(eg: | Async job should not be | SANITY, FUNCTIONAL | Y | P2 | PASS | |||
18 | DeleteHost_from_other_MS | Find the management server that owns this host. | We should see the requests for | FUNCTIONAL | Y | P1 | PASS | |||
19 | AsyncJobState_StopMS_while_Job(Snapshots)_inProgress | From the management server which is NOT the | Async job should get marked as | FUNCTIONAL | Y | P2 | PASS | |||
20 | AgentLB_HostState_UP_cluster_Disabled | 1. zone> pod1> cluster1 cluster2 cluster3 each | MS1 gives away 2nd cluster & | FUNCTIONAL |
| P1 | PASS | |||
21 | AgentLB_HostState_Down_cluster_Disabled | 1. zone> pod1> cluster1 cluster2 cluster3 each | No agent load balancing will | FUNCTIONAL |
| P2 | PASS | |||
22 | AgentLB_ThresHold_lessThan_default value | 1. zone> pod1> cluster1 cluster2 cluster3 each | No agent load balancing will trigger | SANITY, FUNCTIONAL |
| P1 | PASS | |||
23 | AgentLB_ThresHold_moreThan_default value | 1. zone> pod1> cluster1 cluster2 cluster3 each | Agent load balancing will | SANITY, FUNCTIONAL |
| P1 | PASS | |||
24 | AgentLB_ThresHold_moreThan_Non_default_ value | 1. zone> pod1> cluster1 cluster2 cluster3 | Agent load balancing will |
| FUNCTIONAL | P1 | PASS |
| ||
25 | Direct agent-loads |
| As per the configured load size(2),At same time 2 hosts should be consider(processed) for re-balancing. | FUNCTIONAL |
| P2 | PASS | |||
26 | AgentLB_sourceMS_down_during_Re-balancing | 1. In multi clustered Env, make sure all hosts | All hosts already transferred to MS2 | FUNCTIONAL |
| P2 | PASS | |||
27 | AgentLB_DestinationMS_Down_during_Rebalancing | 1. In multi clustered Env, make sure all hosts | If M2 dies, all re balancing should be stopped | SANITY, FUNCTIONAL |
| P1 | PASS | |||
28 | dbServer_ UsageServer on different machines | 1. configure cluster management setup and Make sure | In all the cases usage statistics should be collected and details should be accurate | SANITY, FUNCTIONAL |
| P1 | FAIL | |||
29 | dbServer_ UsageServer on _Same_Machines | 1. configure cluster management setup and Make | In all the cases usage statistics should be | SANITY, FUNCTIONAL |
| P2 | FAIL | |||
30 | Ping Timeout | 1.make sure all the MS's are synch | once ping command timeouts,The corresponding | Negative |
| P1 |
| |||
31 | Upgrade test 3.0.2 to ASF 4.0 | 1.prepare the cluster management setup before upgrade | Upgrade should be successful, | SANITY, FUNCTIONAL |
| P1 | PASS |
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)