You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 11
Next »
|
|
Clustered MS configuration:
MS1: cluster DB MS2, MS3: MS in cluster each 1 host Primary storage: NFS and ISCSI Load balancer: netscaler
For agent_load-balancing cases
Minimum requirement is at least 2 management servers and recommended is 2+
3 management servers - > 1 pod -> 2 clusters -> 4 hosts.(3 hosts on 1 cluster and another host on another cluster) Have Vms running on all hosts
Set up : Avg time to setup cluster management setup is 4 to 6 hrs
The below testcases to be repeated for all the supported hyper-visors.
Also repeated for basic and advanced zone. |
|
SNO |
Testcase Name |
Procedure |
Expected Results |
Test Case Type( Sanity | Functional |Negative) |
is Automatable |
Priority |
Pass/Fail |
Comments |
1 |
Verify_Host_transition_states |
1. Add each Host to each cluster and make sure each host managed by each MGMT server
2.Stop the Management
Server server(MS1) and check the Host transition state when owner ship changed form one MS to another MS(eg:MS1 toMS2) |
1. Check the Host state changed
from Alert-disconnect-Connecting-UP 2.Query the ms-host & host tables for the details |
SANITY, FUNCTIONAL |
N |
P1 |
|
|
2 |
Only_One MS_UP |
1.Make sure each host is managed by each management server
2.Except one Management server, stop other remaining management server(eg:stop MS1,MS2 and keep MS3 up and
running state)
3.Deploy new VMs and perform
VM life-cycle operations(vm stop/start/destroy/restore)
4.snapshot on the volumes
5.register new templates |
a)Able to access the MS UI from MS3 and all
system vms should be up and running
b)All the hosts stats are UP
3)deploy VM should be successful without any errors
4)snapshot should be successful
5.Should be able to register the new templates
successfully |
SANITY, FUNCTIONAL |
Y |
P2 |
|
|
3 |
All_MGMTServices_UP_at_sameTime |
1.Make sure each host is managed by MGMT server
2.Stop the all the running cloud management service once(service cloud-management stop)
3.Start the all the Stopped Management servers (service cloud-management start)
4.Deploy new VMs and perform snapshot on the volumes |
Hosts should get re-distributed to all the 3 management servers. deployVM should be successful without
any errors snapshot operation should be successful
with out any errors |
FUNCTIONAL |
Y |
P2 |
|
|
4 |
restart_ALL_MGMT services's |
1.Make sure each host is managed by each MGMT server
2.restart the cloud-management Service on all
the Management Servers (MS1,MS2,MS3)
(service cloud-management restart) |
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 system date is sync on all the hosts and MS
2.Change the system date in one of MS(MS1) in cluster MS
3. Check the MS state in mshost table
4. Check the MS ownership on host tables
5. Synch the date on MS1(i.e change the sysdate again to synch with other MGMT server) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|