| 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 | https://issues.apache.org/jira/browse/CLOUDSTACK-2146#comment-136389022941 | |||||||||||||
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 |
| ||||||||||||
14 13 | Scaling up RAM | 1-Select a running system vm | 1- SO upgrade should be successful | P0 | Functional | Y | Pass blocked |
| 15 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 |
| ||||||||||||
17 15 | Scaling up CPU and RAM | 1-Select a running system vm | 1- SO upgrade should be successful | P0 | Functional | Y | Pass |
| blocked Blocked |
| ||||||||||||
18 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 | 20 | Restart VM while scaling UP CPU | 1-Use API to restart/stop VM | 1- Restart vm should not have any effect on scaling up 1-DB should get updated with new compute offering | P0 | Functional | Y | Pass |
| Pass |
| ||||||||||
21 | 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-Use API to restart/stop VM | 1-Scaling up 1-VM should live migrate | P0 P1 | Functional | Y | Pass |
| 23 | 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 |
| 24 | Restart VM while scaling UP RAM | ||||||
20 | Scaling up CPU while snapshot creation is in process | 1- -Select a running system vm. | 1-VM should live mirgate | P0 | Functional | Y | Fail | 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. | 26 | Restart VM while scaling UP CPU and RAM | -Select a running vm | 1-DB should get updated with new compute offering | P0 | create snapshot. | scaling up should be successful | P2 | Functional | Y | Pass |
| 27 | Restart VM while scaling UP CPU and RAM | Pass |
| ||||
| Guest OS Support |
|
|
|
|
|
|
|
|
| ||||||||||||
22 | Guest OS does not support scaling up | 1-Select a running vm user VM | 1-Vm should live migrate | P0 | Functional | Y | Fail | Click on upgrade SO | 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 | Scaling up CPU | 1-select a running VM and upgrade SO | 1-Scaleup should failed | 29 | 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 |
| 30 | Restart VM while scaling UP CPU | Fail | Blocked |
| |||||
24 | scaling up CPU | 1-select a running VM and upgrade SO | 1-Scaleup should failed | 1-Select a running system vm | 1-VM should migrate | P1 | Functional | Y | Fail |
| blocked Blocked |
| ||||||||||
25 33 | Restart VM while scaling UP up RAM (Capacity available on current host) | 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 |
| ||||||||||||
26 34 | Restart VM while scaling UP RAM | 1-select a running VM and 1-Select a running system vm | 1-VM should migrate Scaleup should failed | P1 | Functional | Y | blocked |
| 36 | Restart VM while scaling UP CPU and RAM | 1-Select a running system vm | VM should remain in start state | P1 | Functional | Y | Fail |
| Blocked |
| |||
27 | scaling up CPU and RAM | 1-select a running VM and upgrade SO | 1-Scaleup should failed | P1 | Functional | Y | Fail |
| Blocked blocked |
| ||||||||||||
28 37 | Restart VM while scaling UP up CPU and and RAM (Capacity not available on current host but available in current cluster) | 1-Select select a running system vm | 1-VM Scaleup should migrate failed | P1 | Functional | Y | Fail |
| Blocked | blocked | ||||||||||||
|
| Scaling up while snapshot creation is in process
|
|
|
|
|
|
|
| |||||||||||||
39 | Scaling up RAM while snapshot creation is in process | 1-Select a running system vm. | scaling up should be successful | P2 | Functional | Y | Pass |
| ||||||||||||||
40 | Scaling up CPU while snapshot creation is in process | 1-Select a running system vm. | scaling up should be successful | P2 | Functional | Y | Pass |
| ||||||||||||||
41 | 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 |
| ||||||||||||||
| Scale Down |
|
|
|
|
|
|
|
|
| ||||||||||||
29 | 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 | Fail | ||||||||||||||
| UPGRADE |
|
|
|
|
| Guest OS Support |
|
|
|
|
|
|
| 42 | 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) |
|
|
|
|
|
|
| 43 | Scaling up CPU |||||||||||||
30 | upgrade path | Pre upgrade Steps | 1-upgrade should go properly | P1 | Upgrade | N |
|
|
|
| ||||||||||||
| Other |
|
|
|
|
|
|
|
|
| ||||||||||||
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 | 1-Scaleup should failed | P1 | Functional | Y | Fail | ||||||||||||||||
44 | scaling up CPU | 1-select a running VM and upgrade SO | 1-Scaleup should failed | P1 | Functional | Y | Fail |
| ||||||||||||||
46 | scaling up RAM | 1-select a running VM and upgrade SO | 1-Scaleup should failed | P1 | Functional | Y | Fail |
| ||||||||||||||
47 | scaling up RAM | 1-select a running VM and upgrade SO | 1-Scaleup should failed | P1 | Functional | Y | Fail |
| ||||||||||||||
51 | scaling up CPU and RAM | 1-select a running VM and upgrade SO | 1-Scaleup should failed | P1 | Functional | Y | Fail |
| ||||||||||||||
52 | scaling up CPU and RAM | 1-select a running VM and upgrade SO | 1-Scaleup should failed | P1 | Functional | Y | Fail |
| ||||||||||||||
|
|
|
|
|
|
| 55 | scaling up RAM(at least two host in current cluster having capacity) | 1-select a running VM and upgrade SO | 1-CS should choose another host(having Capacity) |
|
| ||||||||||
34 | update to many vms on same host | Update too many(5-10) vms on same host | vm should get updated without error-exception | P1 | Functional | Y | Blocked Pass |
| Pass | |||||||||||||
56 | Scaling up CPU (at least two host in current cluster having capacity) | 1-select a running VM and upgrade SO | 1-CS should choose another host(having Capacity) | P1 | Functional | Y | Blocked |
| ||||||||||||||
57 | scaling up CPU and RAM (at least two host in current cluster having capacity) | 1-select a running VM and upgrade SO | 1-CS should choose another host(having Capacity) | P! | Functional | Y | Blocked |
| ||||||||||||||
| Scale Down |
|
|
|
|
|
|
| ||||||||||||||
| ||||||||||||||||||||||
| Manage-Unmanage/Disable-Enable |
|
|
|
|
|
|
|
|
| ||||||||||||
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 |
| 58 | 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 | Pass |
| |||||
| Attach-Detach Volume |
| UPGRADE |
|
|
|
|
|
|
| 59 | upgrade path | Pre upgrade Steps 1-upgrade should go properly | P1 | Upgrade | N |
|
| ||||
| Other |
|
|
|
|
|
|
| ||||||||||||||
60 | Change SO of a stop VM | 1-Scale up vm | step 2 should be successful |
| Functional | Y | Pass |
| ||||||||||||||
37 | Attach-Detach volumes | 1-deploy vm | all operation should go smoothly |
| Functional | Y | Pass |
| Pass |
| ||||||||||||
| VM Life cycle |
|
|
|
|
|
|
|
|
| ||||||||||||
38 | stop-start | 1-scale up cpu/ram | 1-vm should be using scaled up service offering |
| Functional | Y | Pass |
| Pass |
| ||||||||||||
39 | Reboot | 1-scale up cpu/ram | 1-vm should be using scaled up service offering |
| Functional | Y | Pass |
| Pass |
| ||||||||||||
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 |
|
|
|
| Dashboard |
|
|
|
|
|
| ||||||||||
41 | cluster.cpu.allocated.capacity.disablethreshold |
| 62 | should not be allowed to scale up cpu beyond cpu /RAM | 1-Change CO of a running VM | threshold |
| Dashboard should display new used and free value of CPU and RAM according to CO values. |
| Functional | N | hold | Global parameter is in dev process Pass |
|
| |||||||
42 | cluster.memery.allocated.capacity.desablethreshould |
|
|
| |
| scaleup should not be allowed after memory threshold |
| Function | Y 63 | Usage Event |
| hold | Global parameter is in dev process Waiting for FS update |
|
| ||||||
| Vcpus |
| Race condition |
|
|
|
|
|
|
| 64 | update to many vms on same host | ||||||||||
43 | Vcpus | Scaleup number of vcpus | only scaling up number of vcpus should be allowed |
| Function | Y | Fail | Update too many(5-10) vms on same host | vm should get updated without error-exception |
| Functional | Y | Pass |
| ||||||||
Manage | -Unmanage/Disable-Enable 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 | 65 | Manage-Unmanage cluster | 1-Scaleup vm (cpu and RAM) | 1-step 2 should not have any effect on step 1 |
| Functional | Y | Fail | Pass |
| 66 | Disable-Enable cluster/pod/zone | 1-Scaleup vm | 1-step 2 should not have any effect on step 1 |
| Functional | Y | ||
|
|
|
|
|
|
|
| Pass |
|
| Attach-Detach Volume |
| ||||||||||
45 | CPU cap | scale up vm to a SO which have cpu cap enabled | cpu limit should be set for vm |
| Functional |
|
|
| ||||||||||||||
67 | Attach-Detach volumes | 1-deploy vm | all operation should go smoothly |
| Functional | Y | Pass |
| ||||||||||||||
Fail | Fail | |||||||||||||||||||||
|
|
|
|
| VM Life cycle |
|
|
|
|
|
|
| ||||||||||
46 | Gust OS | 68 | stop-start | 1-scale up cpu/ram | vm should have 1 GB memory and 1GHz CPU 1-vm should be using scaled up service offering |
| Functional | Y | Pass |
| ||||||||||||
69 | Reboot | 1-scale up cpu/ram | 1-vm should be using scaled up service offering |
| 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 | -- |
| 70 | expunge and restore and start | 1-scale up cpu/ram | 1-vm should be using scaled up service offering |
| Functional | Y | Pass |
|