| Hypervisor : XenserverAbbreviation |
|
|
|
|
|
|
|
| |||||||||||||||||
Test Case ID | Test Case Name | Steps | Expected Results | Priority | Test Case Type | Automatable(Y/N) | Xenserver | Comments | VMware | Comments Comment | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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 | 3 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 |
| 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 | 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 |
| Fail Blocked |
| ||||||||||||||||
13 | Scaling up RAM | 1-Select a running system vm | 1- SO upgrade should be successful | P0 | Functional | Y | Pass |
| Blocked Fail |
| ||||||||||||||||
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 Fail |
| ||||||||||||||||
15 | Scaling up CPU and RAM | 1-Select a running system vm | 1- SO upgrade should be successful | P0 | Functional | Y | Pass |
| Fail 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 |
| Fail 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 1-VM should live migrate | P0 P1 | Functional | Y | Pass |
| 19 | Restart VM while scaling UP RAM | Blocked |
| ||||||||||||||
| Scaling up while snapshot creation is in process |
|
|
|
|
|
|
|
|
| ||||||||||||||||
19 | Scaling up RAM while snapshot creation is in process | 1-Select a running system vm. | 1-DB should get updated with new compute offering | P0 | Functional | create snapshot. | scaling up should be successful | P2 | Functional | Y | Pass | Y | Pass |
| ||||||||||||
20 | Restart VM while scaling UP RAM | Scaling up CPU while snapshot creation is in process | 1-Select a running system vm. | 1-VM should live mirgate | P0 | Functional | Y | Fail | 21 | Restart VM while scaling UP CPU and RAM | create snapshot. | scaling up should be successful | P2 | Functional | Y | Pass |
| Pass |
| |||||||
21 | Scaling up CPU and RAM while snapshot creation is in process | 1-Select a running system vm. | 1-DB should get updated with new compute offering | create snapshot. | scaling up should be successful | P2 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 | |||||||||||||||||||
Pass |
| |||||||||||||||||||||||||
| Guest OS Support |
|
|
|
|
|
|
|
|
| ||||||||||||||||
22 | 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) |
|
|
| Restart system vms during operation( Need to repeat for SSVM,CPVM,VR ) |
|
|
|
|
|
|
| ||||||||||||||
23 | Restart VM while scaling UP Scaling up CPU | 1-Select select a running system vm VM and upgrade SO | 1-DB should get updated with new compute offering Scaleup should failed | P1 | Functional | Y | Fail | Blocked blocked |
| |||||||||||||||||
24 | Restart VM while scaling UP CPU | 1-Select select a running system vm | 1-VM should migrate Scaleup should failed | P1 | Functional | Y | VM should remain in start state | P1 | Functional | Y | Fail |
| Blocked blocked |
| ||||||||||||
25 | Restart VM while scaling UP RAM | 1-Select select a running system vm | 1-DB should get updated with new compute offering | P1 | Functional | Y | Fail |
| Blocked blocked |
| ||||||||||||||||
26 | Restart VM while scaling UP RAM | 1-Select select a running system vm | 1-VM should migrate Scaleup should failed | P1 | Functional | Y | Fail |
| blocked Blocked |
| ||||||||||||||||
27 | Restart VM while scaling UP up CPU and and RAM | 1-Select select a running system vm | 1-DB should get updated with new compute offering Scaleup should failed | P1 | Functional | Y | Fail |
| blocked Blocked |
| ||||||||||||||||
28 | Restart VM while scaling UP up CPU and RAM | 1-select a running VM and 1-Select a running system vm | 1-VM Scaleup should migrate failed | P1 | Functional | Y | blocked |
| VM should remain in start state | P1 | Functional | Y | Fail |
| Blocked |
| ||||||||||
|
|
|
|
|
|
|
|
|
| |||||||||||||||||
| Scale Down |
|
|
| Scaling up while snapshot creation is in process |
|
|
|
|
|
|
| ||||||||||||||
29 | Scale down CPU and Memory | 1- Select a running system vm. | scaling up should be successful | Upgrade vm with CO(=Compute offering) have less RAM and CPU than current CO | should get a message "scale down not supported" | P1 P2 | Functional | Y | Pass |
| ||||||||||||||||
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 |
| ||||||||||||||||||
31 | 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 |
| ||||||||||||||||||
| Guest OS Support |
|
|
|
|
|
|
| ||||||||||||||||||
Fail | Fail | |||||||||||||||||||||||||
| UPGRADE |
|
|
|
|
|
|
|
|
| ||||||||||||||||
30 | upgrade path | Pre upgrade Steps | 1-upgrade should go properly | P1 | Upgrade | N |
|
|
|
| ||||||||||||||||
| Other |
| 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) |
|
|
|
|
|
|
| 33 Scaling up CPU | 1-Scaleup should failed | P1 | Functional | Y | Fail | |
34 | scaling up CPU | 1-select a running VM and upgrade SO | 1-Scaleup should failed | P1 | Functional | Y | Fail |
| ||||||||||||||||||
35 | scaling up RAM | 1-select a running VM and upgrade SO | 1-Scaleup should failed | P1 | Functional | Y | Fail |
| ||||||||||||||||||
36 | scaling up RAM | 1-select a running VM and upgrade SO | 1-Scaleup should failed | P1 | Functional | Y | Fail |
| ||||||||||||||||||
37 | scaling up CPU and RAM | 1-select a running VM and upgrade SO | 1-Scaleup should failed | P1 | Functional | Y | Fail |
| ||||||||||||||||||
38 | scaling up CPU and RAM | 1-select a running VM and upgrade SO | 1-Scaleup should failed | P1 | Functional | Y | Fail |
| ||||||||||||||||||
31 | Change SO of a stop VM | 1-Scale up vm | step 2 should be successful |
| Functional | Y | Pass |
| Pass |
| ||||||||||||||||
| Dashboard |
|
|
|
|
|
|
|
|
| ||||||||||||||||
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 |
| ||||||||||||||||
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||
33 | Usage Event |
| Waiting for FS update |
|
|
|
|
|
|
| ||||||||||||||||
| Race condition |
|
|
|
|
|
|
|
|
| ||||||||||||||||
34 | 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 |
|
|
|
|
|
|
|
|
| Scale Down |
|
|
|
|
|
|
| ||||||||
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 | Y | Fail | |||||||||||||||||||
| UPGRADE |
|
|
|
|
|
|
| ||||||||||||||||||
|
| |||||||||||||||||||||||||
35 | Manage-Unmanage cluster | 1-Scaleup vm (cpu and RAM) | 1-step 2 should not have any effect on step 1 |
| Functional | Y |
|
| Pass |
| ||||||||||||||||
36 | 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 | Attach-Detach volumes | 1-deploy vm | all operation should go smoothly |
| Functional | Y | Pass |
| Pass |
| ||||||||||||||||
| VM Life cycle | 40 | upgrade path | Pre upgrade Steps 1-upgrade should go properly | P1 | Upgrade | N |
|
|
| Other
|
|
|
|
|
| ||||||||||
38 | stop-start | 1-scale up cpu/ram | 1-vm should be using scaled up service offering |
| Functional | Y | Pass |
| Pass |
| ||||||||||||||||
39 | Reboot | 41 | Change SO of a stop VM | 1-Scale up scale up cpu/ram | 1-Stop the vm |
| Functional | Y | Pass |
|
| Dashboard Pass |
|
|
|
|
|
|
| |||||||
40 | expunge and restore and start | 1-scale up cpu/ram | 1-vm should be using scaled up service offering | 42 | 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 Y | Pass |
| Pass |
| ||||||||||||
| Global Settings |
|
|
|
|
| 43 | Usage Event |
| Waiting for FS update |
|
|
|
| ||||||||||||
41 | cluster.cpu.allocated.capacity.disablethreshold | Race condition | should not be allowed to scale up cpu beyond cpu threshold |
|
|
|
| hold | Global parameter is in dev process |
|
| |||||||||||||||
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 |
| ||||||||||||||||||
| Manage-Unmanage/Disable-Enable |
|
|
|
|
|
|
| ||||||||||||||||||
42 | cluster.memery.allocated.capacity.desablethreshould |
| scaleup should not be allowed after memory threshold |
| Function | Y | hold | Global parameter is in dev process |
|
| ||||||||||||||||
| Vcpus |
|
|
|
|
|
|
|
|
| ||||||||||||||||
43 | Vcpus | Scaleup number of vcpus | only scaling up number of vcpus should be allowed |
| Function | Y | Fail | 45 | Manage-Unmanage cluster | 1-Scaleup vm (cpu and RAM) | 1-step 2 should not have any effect on step 1 |
| Functional | Y | Pass
| 46 | Disable-Enable cluster/pod/zone | 1-Scaleup vm | 1-step 2 should not have any effect on step 1 |
| Functional | Y | Pass |
| ||
| Memory actual | Attach-Detach Volume |
|
|
|
|
|
|
| 47 | Attach-Detach volumes | 1-deploy vm |
| |||||||||||||
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 all operation should go smoothly |
| Functional | Y | Pass |
| Fail |
| VM Life cycle |
|
| |||||||||||||
|
|
|
|
| 48 | stop-start | 1-scale up cpu/ram |
|
|
| 1-vm should be using scaled up service offering |
| Functional | Y | Pass |
| ||||||||||
45 49 | CPU cap Reboot | 1- scale up cpu/ram | cpu limit should be set for vm 1-vm should be using scaled up service offering |
| Functional | Y | Pass |
| 50 | expunge and restore and start | 1-scale up cpu/ram | 1-vm should be using scaled up service offering |
| Functional | Y | Fail | Fail | |||||||||
|
|
|
|
|
| Pass |
|
| Global Settings |
|
|
|
|
|
|
| ||||||||||
51 | cluster.cpu.allocated.capacity.disablethreshold |
| should not be allowed to scale up cpu beyond cpu threshold |
|
|
| hold | Global parameter is in dev process | ||||||||||||||||||
|
| |||||||||||||||||||||||||
46 | Gust OS | 1-Scale up a vm form small to medium instance | vm should have 1 GB memory and 1GHz CPU |
| Functional | Y | Pass |
| Fail | https://issues.apache.org/jira/browse/CLOUDSTACK-2990#comment-13682213 | ||||||||||||||||
47 | Guest OS (window-8) | Scale up a windows 8 vm | memory and ram should get registered |
| Functoinal | Y | -- |
| Pass |
| 52 | cluster.memery.allocated.capacity.desablethreshould |
| scaleup should not be allowed after memory threshold |
| Function | Y | hold | Global parameter is in dev process |