| Hypervisor : XenserverAbbreviation |
|
|
|
|
|
|
|
| |||||||
Test Case ID | Test Case Name | Steps | Expected Results | Priority | Test Case Type | Automatable(Y/N) | Xenserver | Comments | VMware | Comments | ||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | UI and API | 1-Check for upgrade button | 1-Upgrade button should be present. | P0 | Functional | Y | Pass | 1- | Pass |
| ||||||
| User VM CPU/ RAM scale up |
|
|
|
|
|
|
|
|
| ||||||
2 | Scaling up CPU | 1-Select a running user vm | 1- SO upgrade should be successful | P0 | Functional | Y | Passed with workaround | Pass |
| |||||||
3 | Scaling up CPU | 1-Select a running user vm | 1-Vm should migrate(live) to another host (having Capacity). | P0 | Functional | Y | Pass |
|
| Fail | ||||||
4 | Scaling up CPU | 1-Select a running user vm | 1-SO upgrade should fail. | P0 | Functional | Y | Pass |
| Pass |
| ||||||
5 | Scaling up RAM | 1-Select a running user vm | 1-SO upgrade should be successful | P0 | Functional | Y | Pass |
| Pass | Fail | ||||||
6 | Scaling up RAM | 1-Select a running user vm | 1-Vm should migrate(live) to another host (having Capacity). | P0 | Functional | Y | Fail |
|
| |||||||
7 | Scaling up RAM | 1-Select a running user vm | 1-SO upgrade should fail.. | P0 | Functional | Y | Pass |
|
|
| ||||||
8 | Scaling up CPU and RAM | 1-Select a running user vm | 1- SO upgrade should be successful | P0 | Functional | Y | Pass |
| Pass |
| ||||||
9 | Scaling up CPU and RAM | 1-Select a running user vm | 1-Vm should migrate(live) to another host (having Capacity). | P0 | Function | Y | Fail |
| Fail | |||||||
10 | Scaling up CPU and RAM | 1-Select a running user vm | 1-SO upgrade should fail.. | P0 | Functional | Y | Pass |
| Pass |
| ||||||
| System VM CPU/RAM scale up( Need to repeat for SSVM,CPVM,VR) |
|
|
|
|
|
|
|
|
| ||||||
11 | Scaling up CPU | 1-Select a running system vm | 1- SO upgrade should be successful | P0 | Functional | Y | Pass | Fail | ||||||||
12 | Scaling up CPU | 1-Select a running system vm | 1-Vm should migrate(live) to another host (having Capacity). | P1 | Functional | Y | blocked |
| Blocked |
| ||||||
13 | Scaling up RAM | 1-Select a running system vm | 1- SO upgrade should be successful | P0 | Functional | Y | Pass |
| Blocked |
| ||||||
14 | Scaling up RAM | 1-Select a running system vm | 1-Vm should migrate(live) to another host (having Capacity). | P1 | Functional | Y | blocked |
| Blocked |
| ||||||
15 | Scaling up CPU and RAM | 1-Select a running system vm | 1- SO upgrade should be successful | P0 | Functional | Y | Pass |
| Blocked |
| ||||||
16 | Scaling up CPU and RAM | 1-Select a running system vm | 1-Vm should migrate(live) to another host (having Capacity). | P1 | Functional | Y | blocked |
| Blocked |
| ||||||
| Scaleup Scale up vm while Restart/power off VM is in process |
|
|
|
|
|
|
|
|
| ||||||
17 | 1-Restart/stop VM | 1-Use API to restart/stop VM | 1- DB should get updated with new compute offering | P0 | Functional | Y | Pass |
| Pass |
| ||||||
18 | Scale up system vm while Restart/power off VM is in process( Need to repeat for SSVM,CPVM,VR ) |
|
|
|
|
|
|
|
|
| ||||||
18 | 1-Restart/stop VM | 1 VM while scaling UP CPU | 1-Scaling up DB should get updated with new compute offering | P0 P1 | Functional | Y | Pass |
| Pass Blocked |
| ||||||
19 | Restart VM while scaling UP RAM | 1-Select a running vm | 1-DB should get updated with new compute offering | P0 | Functional | Y | Pass |
|
|
| ||||||
20 | Restart VM while scaling UP RAM | -Select a running vm | 1-VM should live mirgate | P0 | Functional | Y | Fail |
|
| |||||||
21 | Restart VM while scaling UP CPU and RAM | -Select a running vm | 1-DB should get updated with new compute offering | P0 | Functional | Y | Pass |
|
|
| ||||||
22 | Restart VM while scaling UP CPU and RAM | -Select a running vm | 1-Vm should live migrate | P0 | Functional | Y | Fail |
|
| |||||||
| Restart system vms during operation( Need to repeat for SSVM,CPVM,VR ) |
|
|
|
|
|
|
|
|
| ||||||
23 | Restart VM while scaling UP CPU | 1-Select a running system vm | 1-DB should get updated with new compute offering | P1 | Functional | Y | blocked |
|
|
| 24 | Restart VM while scaling UP CPU | 1-Select a running system vm | 1-VM should migrate |||
Scaling up while snapshot creation is in process |
|
|
|
|
| P1 | Functional | Y | blocked |
|
|
| ||||
25 | Restart VM while scaling UP RAM | 1-Select a running system vm | 1-DB should get updated with new compute offering | P1 | Functional | Y | blocked |
|
|
| ||||||
26 | Restart VM while scaling UP RAM | 1-Select a running system vm | 1-VM should migrate | P1 | Functional | Y | blocked |
|
|
| ||||||
27 | Restart VM while scaling UP CPU and RAM | 1-Select a running system vm | 1-DB should get updated with new compute offering | P1 | Functional | Y | blocked |
|
|
| ||||||
28 | Restart VM while scaling UP CPU and RAM | 1-Select a running system vm | 1-VM should migrate | P1 | Functional | Y | blocked |
|
|
| ||||||
| Scaling up while snapshot creation is in process |
|
|
|
|
|
|
|
|
| ||||||
19 29 | Scaling up RAM while snapshot creation is in process | 1-Select a running system vm. | scaling up should be successful | P2 | Functional | Y | Pass |
| Pass |
| ||||||
20 30 | Scaling up CPU while snapshot creation is in process | 1-Select a running system vm. | scaling up should be successful | P2 | Functional | Y | Pass |
| Pass |
| ||||||
31 21 | Scaling up CPU and RAM while snapshot creation is in process | 1-Select a running system vm. | scaling up should be successful | P2 | Functional | Y | Pass |
| Pass |
| ||||||
| Guest OS Support |
|
|
|
|
|
|
|
|
| ||||||
22 32 | Guest OS does not support scaling up | 1-Select a running user VM | Should throw "not supported exception" | P3 | Functional | Y |
|
|
|
| ||||||
| CS behavior when migration fails while scaling up CPU/RAM(power off /service network stop , Destination host) |
|
|
|
|
|
|
|
|
| ||||||
23 33 | Scaling up CPU | 1-select a running VM and upgrade SO | 1-Scaleup should failed | P1 | Functional | Y | Fail | Blocked |
| |||||||
34 24 | scaling up CPU | 1-select a running VM and upgrade SO | 1-Scaleup should failed | P1 | Functional | Y | Fail |
| Blocked |
| ||||||
25 35 | scaling up RAM | 1-select a running VM and upgrade SO | 1-Scaleup should failed | P1 | Functional | Y | Fail |
| Blocked |
| ||||||
26 36 | scaling up RAM | 1-select a running VM and upgrade SO | 1-Scaleup should failed | P1 | Functional | Y | Fail |
| Blocked |
| ||||||
27 37 | scaling up CPU and RAM | 1-select a running VM and upgrade SO | 1-Scaleup should failed | P1 | Functional | Y | Fail |
| Blocked |
| ||||||
28 38 | scaling up CPU and RAM | 1-select a running VM and upgrade SO | 1-Scaleup should failed | P1 | Functional | Y | Fail |
| Blocked |
| ||||||
|
|
|
|
|
|
|
|
|
| |||||||
| Scale Down |
|
|
|
|
|
|
|
|
| ||||||
29 39 | Scale down CPU and Memory | 1- Upgrade vm with CO(=Compute offering) have less RAM and CPU than current CO | should get a message "scale down not supported" | P1 | Functional | Functional | Y | Fail | Fail | Fail |
| |||||
| UPGRADE |
|
|
|
|
|
|
|
|
| ||||||
30 40 | upgrade path | Pre upgrade Steps | 1-upgrade should go properly | P1 | Upgrade | N |
|
|
|
| ||||||
| Other |
|
|
|
|
|
|
|
|
| ||||||
31 41 | Change SO of a stop VM | 1-Scale up vm | step 2 should be successful |
| Functional | Y | Pass |
| Pass |
| ||||||
| Dashboard |
|
|
|
|
|
|
|
|
| ||||||
42 32 | scale up cpu /RAM | 1-Change CO of a running VM | Dashboard should display new used and free value of CPU and RAM according to CO values. |
| Functional | N | Pass |
| Pass |
| ||||||
|
|
|
|
|
|
|
|
|
|
| ||||||
43 33 | Usage Event |
| Waiting for FS update |
|
|
|
|
|
|
| ||||||
| Race condition |
|
|
|
|
|
|
|
|
| ||||||
34 44 | update to many vms on same host | Update too many(5-10) vms on same host | vm should get updated without error-exception |
| Functional | Y | Pass |
| Pass |
| ||||||
| Manage-Unmanage/Disable-Enable |
|
|
|
|
|
|
|
|
| ||||||
35 45 | Manage-Unmanage cluster | 1-Scaleup vm (cpu and RAM) | 1-step 2 should not have any effect on step 1 |
| Functional | Y |
|
| Pass |
| ||||||
36 46 | Disable-Enable cluster/pod/zone | 1-Scaleup vm | 1-step 2 should not have any effect on step 1 |
| Functional | Y | Pass |
| Pass |
| ||||||
| Attach-Detach Volume |
|
|
|
|
|
|
|
|
| ||||||
37 47 | Attach-Detach volumes | 1-deploy vm | all operation should go smoothly |
| Functional | Y | Pass |
| Pass |
| ||||||
| VM Life cycle |
|
|
|
|
|
|
|
|
| ||||||
48 38 | stop-start | 1-scale up cpu/ram | 1-vm should be using scaled up service offering |
| Functional | Y | Pass |
| Pass |
| ||||||
49 39 | Reboot | 1-scale up cpu/ram | 1-vm should be using scaled up service offering |
| Functional | Y | Pass |
| Pass |
| ||||||
50 40 | expunge and restore and start | 1-scale up cpu/ram | 1-vm should be using scaled up service offering |
| Functional | Y | Pass |
| Pass |
| ||||||
| Global Settings |
| Settings |
|
|
|
|
|
|
|
|
| ||||
41 | cluster.cpu.allocated.capacity.disablethreshold |
| should not be allowed to scale up cpu beyond cpu threshold |
|
|
|
| hold | Global parameter is in dev process |
|
| |||||
42 51 | cluster.cpumemery.allocated.capacity.disablethreshold desablethreshould |
| scaleup should not be allowed to scale up cpu beyond cpu after memory threshold |
| Function | Y | hold | Global parameter is in dev process dev process |
|
| ||||||
| Vcpus |
|
|
|
|
|
|
|
|
| 52 | cluster.memery.allocated.capacity.desablethreshould | ||||
43 | Vcpus | Scaleup number of vcpus | only scaling up number of vcpus should be allowed |
| scaleup should not be allowed after memory threshold |
| Function | Y | hold | Global parameter is in dev process | Fail | Pass |
| |||
Vcpus | Memory actual |
|
|
|
|
|
|
|
|
| ||||||
44 | memory-actual | after scaling up check memery actual of vms | 1-For system vms and user vms memory actual should get changed to new values |
| Functional | 53 | Vcpus | Scaleup number of vcpus | only scaling up number of vcpus should be allowed |
| Function | Y | Fail | Pass |
| |
| Memory actual
|
|
|
|
|
|
|
|
|
| ||||||
45 | CPU cap | scale up vm to a SO which have cpu cap enabled | cpu limit should be set for vm | 54 | memory-actual | after scaling up check memery actual of vms | 1-For system vms and user vms memory actual should get changed to new values |
| Functional |
| Fail | Fail | https://issues.apache.org/jira/browse/CLOUDSTACK-2454/jira/browse/CLOUDSTACK-2939 | |||
|
|
|
|
|
|
|
|
|
|
| ||||||
46 55 | CPU cap | scale up vm to a SO wich have cpu cap enabled | cpu limit should be set for vm |
| Gust OS | 1-Scale up a vm form small to medium instance | vm should have 1 GB memory and 1GHz CPU |
| Functional | Y | Pass Functional |
| Fail | Fail | ||
47 | Guest OS (window-8) | Scale up a windows 8 vm | memory and ram should get registered |
| Functoinal | Y | -- |
| Pass |