| Hypervisor : Xenserver,VMwareAbbreviation |
|
|
|
|
|
|
|
|
|
| |||||||||||||||||
Test Case ID | Test Case Name | Steps | Expected Results | Priority | Test Case Type | Automatable(Y/N) | Xenserver | Comments | 2nd Cycle | VMware | Comments | 2nd Cycle | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | UI and API | 1-Check for upgrade button | 1-Upgrade button should be present. | P0 | Functional | Y | Pass | 1- | Pass | Pass |
|
|
| User VM CPU/ RAM scale up https://issues.apache.org/jira/browse/CLOUDSTACK-3713 | ||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||
| User VM CPU/ RAM scale up |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||
2 | 2 | Scaling up CPU | 1-Select a running user vm | 1- SO upgrade should be successful | P0 | Functional | Y | Passed with workaround | Pass | Pass |
| 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 |
| as per Nitin comment above will get solved if https://issues.apache.org/jira/browse/CLOUDSTACK-1809 will be solved | Fail | |||||||||||||||
4 | Scaling up CPU | 1-Select a running user vm | 1-SO upgrade should fail. | P0 | Functional | Y | Pass |
| Pass | Pass |
| Pass | ||||||||||||||||
5 | Scaling up RAM | 1-Select a running user vm | 1-SO upgrade should be successful | P0 | Functional | Y | Pass |
| Pass | pass |
| Fail | Pass(boundary condition) httphttps://issuesbugs-ccp.apachecitrix.orgcom/jira/browse/CLOUDSTACKCS-2985 18112 | |||||||||||||||
6 | Scaling up RAM | 1-Select a running user vm | 1-Vm should migrate(live) to another host (having Capacity). | P0 | Functional | Y | Fail |
|
|
|
| Pass | Fail | https://issues.apache.org/jira/browse/CLOUDSTACK-2985 | Fail | |||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||
7 | Scaling | 7 | Scaling up RAM | 1-Select a running user vm | 1-SO upgrade should fail.. | P0 | Functional | Y | Pass |
| Pass | Pass |
| Pass | ||||||||||||||
8 | Scaling up CPU and RAM | 1-Select a running user vm | 1- SO upgrade should be successful | P0 | Functional | Y | Pass |
| Pass | 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 | Pass | Fail | https://issues.apache.org/jira/browse/CLOUDSTACK-2985 | Fail | |||||||||||||||
10 | Scaling up CPU and RAM | 1-Select a running user vm | 1-SO upgrade should fail.. | P0 | Functional | Y | Pass |
| Pass | Pass |
| Pass | ||||||||||||||||
| System VM CPU/RAM scale up(Not supported in XEN) |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||
11 | Scaling up CPU | 1-Select a running system vm | 1- SO upgrade should be successful | P0 | Functional | Y | Pass | N/A | Fail | Pass | ||||||||||||||||||
12 | Scaling up CPU | 1-Select a running system vm | 1-Vm should migrate(live) to another host (having Capacity). | P1 | Functional | Y | blocked |
| N/A | Blocked |
|
| ||||||||||||||||
13 | Scaling up RAM | 1-Select a running system vm | 1- SO upgrade should be successful | P0 | Functional | Y | Pass |
| N/A | Blocked |
| Pass | ||||||||||||||||
14 | Scaling up RAM | 1-Select a running system vm | 1-Vm should migrate(live) to another host (having Capacity). | P1 | Functional | Y | blocked |
| N/A | Blocked |
|
| ||||||||||||||||
15 | Scaling up CPU and RAM | 1-Select a running system vm | 1- SO upgrade should be successful | P0 | Functional | Y | Pass |
| N/A | Blocked |
| pass | ||||||||||||||||
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 |
| N/A | Blocked |
|
| ||||||||||||||||
| Scale up vm while Restart/power off VM is in process |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||
17 | 1-Restart/stop VM | 1-Use API to restart/stop VM | 1- Restart vm should not have any effect on scaling up | P0 | Functional | Y | Pass |
|
| Pass |
|
| ||||||||||||||||
| Scale up system vm while Restart/power off VM is in processis in process(not supported in xen) |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||
18 | 1-Restart/stop VM | 1-Use API to restart/stop VM | 1-Scaling up vm should fail | P1 | Functional | Y | Pass |
|
| Blocked pass |
|
| ||||||||||||||||
| Scaling up while snapshot creation is in process |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||
19 | 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 | 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 |
|
| ||||||||||||||||
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 | 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 | Scaling up CPU | 1-select a running VM and upgrade SO | 1-Scaleup should failed | P1 | Functional | Y | Fail |
| Blocked |
|
| |||||||||||||||||
24 | scaling up CPU | 1-select a running VM and upgrade SO | 1-Scaleup should failed | P1 | Functional | Y | Fail |
|
| Blocked |
|
| ||||||||||||||||
25 | scaling up RAM | 1-select a running VM and upgrade SO | 1-Scaleup should failed | P1 | Functional | Y | Fail |
|
| Blocked |
|
| ||||||||||||||||
26 | scaling up RAM | 1-select a running VM and upgrade SO | 1-Scaleup should failed | 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 |
|
| ||||||||||||||||
28 | 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 | 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 | Pass | Fail | Pass | ||||||||||||||||||
| UPGRADE |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||
30 | upgrade path | Pre upgrade Steps | 1-upgrade should go properly | P1 | Upgrade | N |
|
| Pass |
|
| Pass | ||||||||||||||||
| Other |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||
31 | Change SO of a stop VM | 1-Scale up vm | step 2 should be successful |
| Functional | Y | Pass |
| Pass | Pass |
| fail | 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 | Pass |
| Pass | ||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||
33 | Usage Event |
| Waiting for FS update |
|
|
| -- |
| Pass |
|
|
|
| |||||||||||||||
| Race condition |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||
34 | update to many some vms on same host | Update too manyUpdate (5-10) vms on same host | vm should get updated without error-exception |
| Functional | Y | Pass |
|
| Pass |
|
| ||||||||||||||||
| 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 | Pass |
| 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 | Pass |
| Pass | ||||||||||||||||
| Attach-Detach Volume |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||
37 | Attach-Detach volumes | 1-deploy vm | all operation should go smoothly |
| Functional | Y | Pass |
| Pass | 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 | Pass |
| Pass | ||||||||||||||||
39 | Reboot | 1-scale up cpu/ram | 1-vm should be using scaled up service offering |
| Functional | Y | Pass |
| Pass | Pass |
| Pass | ||||||||||||||||
40 | expunge and restore and start | 1-scale up cpu/ram | 1-vm should be using scaled up service offering up service offering |
| Functional | Y | Pass |
| Pass | Pass |
| Pass | ||||||||||||||||
Functional | Global Settings | Y | Pass |
|
| Pass |
|
|
| Global 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 | 41 | cluster.cpumemery.allocated.capacity.disablethreshold desablethreshould |
| scaleup should not be allowed to scale up cpu beyond cpu memory threshold |
| Function | Y | hold | Global parameter is in dev process dev process |
|
|
| ||||||||||||||||
| Vcpus |
|
|
|
|
|
|
|
|
|
|
| 42 | 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 | Pass |
| Pass | ||||||||||||
Vcpus | Memory actual |
|
|
|
|
|
|
|
|
|
| 43 | ||||||||||||||||
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 | Vcpus | Scaleup number of vcpus | only scaling up number of vcpus should be allowed |
| Function | Y | Fail | Pass Pass | N/A |
| N/A | ||||||||||||
|
| Memory actual |
|
|
|
|
|
|
|
|
|
|
| |||||||||||||||
45 | CPU cap | scale up vm to a SO which have cpu cap enabled | cpu limit should be set for 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 |
| Functional | Y | Fail | Pass |
|
| Fail | Pass | ||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||
46 | 45 | CPU cap | scale up vm to a SO which have cpu cap enabled | Gust OS | 1-Scale up a vm form small to medium instance | vm should have 1 GB memory and 1GHz CPU cpu limit should be set for vm |
| Functional | Y | Fail | Pass | Pass | Fail |
| Pass | |||||||||||||
47 | Guest OS (window-8) | Scale up a windows 8 vm | memory and ram should get registered |
| Functoinal | Y | -- |
|
| Pass |
|
| ||||||||||||||||
|
|
| 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 |
| |
48 | Global parameter | 1-set GP "enable.dynamic.scale.vm" to false | 1-step two should failed |
| Functional Functoinal | Y | -- |
| Pass |
|
| Pass | ||||||||||||||||
| Memory Hot Add on VMware |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||
49 |
|
| ||||||||||||||||||||||||||
48 | Global parameter | 1-set GP "enable.dynamic.scale.vm" to false | 1-step two should failed |
| Functional | Y | - | Pass |
|
|
|
| ||||||||||||||||
1- deploy a vm with a SO having memory = 1GB | should fail since max limit is 3 GB |
| Functional |
|
|
|
| Pass |
| Pass | ||||||||||||||||||
50 |
| 1- deploy a vm with a SO having memory = 1GB | scaleup should be successful |
| Functional |
|
|
|
|
|
|
| Pass |
| Pass | |||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
51 | VM property "isdyanmicallyscalable" | 1-set isdynamicallyscalable to false | step 2 should be fail |
| Fuantional | -- | -- |
|
|
|
|
|
|