DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.

DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
| Hypervisor : XenserverAbbreviation |
|
|
|
| Supported only For VMware |
|
|
|
|
| |||||||||||||
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-Login through UI | 1-Upgrade button should be present. |
| scaleVirtualMachine and return job id | P0 | Functional | Y | 2 | Scaling up CPU Pass | 1- Login through UI | 1- CS should upgrade VM with SO. | P0 | Functional | Y | |||||||||
3 | Scaling up CPU | 1-Login through UI | 1-Vm should migrate(live) to another host | P0 | Functional | Y | ||||||||||||||||||
4 | Scaling up CPU | 1-login through UI | 1-CS should not upgrade VM with SO. | P0 | Functional | Y | ||||||||||||||||||
5 | Scaling up RAM | 1-Login through UI | 1-CS should upgrade VM with SO. | P0 | Functional | Y | ||||||||||||||||||
6 | Scaling up RAM | 1-Login through UI | 1-Vm should migrate(live) to another hos | P0 | Functional | Y | ||||||||||||||||||
7 | Scaling up RAM | 1-login through UI | 1-CS should not upgrade VM with SO. | P0 | Functional | Y | ||||||||||||||||||
8 | Scaling up CPU and RAM | 1-Login through UI | 1- CS should upgrade VM with SO. | P0 | Functional | Y | ||||||||||||||||||
9 | Scaling up CPU and RAM | 1-login through UI | 1-Vm should migrate(live) to another hos | P0 | Functional | Y | ||||||||||||||||||
10 | Scaling up CPU and RAM | -Login through UI | 1-CS should not upgrade VM with SO. | P0 | Functional | Y | ||||||||||||||||||
| System VM scale up( Need to test for each of them SSVM,CPVM,VR) |
|
|
|
|
| ||||||||||||||||||
| Scaling up CPU | 1-Loginm through UI | SO should get upgrade | P0 | Functional | Y | ||||||||||||||||||
| Scaling up CPU | 1-Loginm through UI | 1-System VM should get upgrade | P0 | Functional | Y | ||||||||||||||||||
| Scaling up CPU | 1-Loginm through UI | 1-System VM |
|
|
| ||||||||||||||||||
| Scaling up RAM | 1-Loginm through UI |
|
|
|
| ||||||||||||||||||
| Pass | Pass |
| https://issues.apache.org/jira/browse/CLOUDSTACK-3713 | ||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
| 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 | 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 | https://issues.apache.org/jira/browse/CLOUDSTACK-2985 | 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 |
| Pass(boundary condition) http://bugs-ccp.citrix.com/browse/CS-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 | https://issues.apache.org/jira/browse/CLOUDSTACK-2107 | Pass | Fail | https://issues.apache.org/jira/browse/CLOUDSTACK-2985 | Fail | ||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
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 | 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 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 |
|
| 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 |
| Scaling up RAM | 1-Loginm through UI 2-Click upgrade SO 3-Required Resource are not available on host but in cluster |
|
|
|
|
| Scaling up RAM |
|
| 1-Loginm through UI |
|
|
| ||||||||
30 |
| upgrade path | Pre upgrade Steps Scaling up CPU and RAM |
|
|
|
| |||||||||||||||||
| Scaling up CPU and RAM | -Loginm through UI |
|
|
|
| ||||||||||||||||||
| Scaling up CPU and RAM | 1-Loginm through UI |
|
|
|
| ||||||||||||||||||
|
|
|
|
|
|
| ||||||||||||||||||
| Restart/power off VM during operation |
|
|
|
|
| 11 | Restart VM while scaling UP CPU | 1-Login through UI | 1-DB should get updated with new compute offering P1 | Functional | Y | ||||||||||||
create some compute offerings | 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 | ||||||||||||
|
|
| ||||||||||||||||||||||
| Restart VM while scaling UP CPU | 1-Login through UI | 1-DB should get updated with new compute offering |
| Functional |
| ||||||||||||||||||
| Restart VM while scaling UP CPU | 1-Login through UI | 1-Should not get upgraded |
| Functional |
| ||||||||||||||||||
12 | Restart VM while scaling UP RAM | 1-Login through UI | 1-DB should get updated with new compute offering | P1 | Functional | Y | ||||||||||||||||||
| Restart VM while scaling UP RAM | 1-Login through UI | 1-DB should get updated with new compute offering |
|
|
|
| Restart VM while scaling UP RAM | 1-Login through UI | 1-Should not get upgraded |
|
|
|
|
|
| ||||||||
33 | Usage Event |
|
|
|
| Restart VM while scaling UP CPU and RAM | 1-Login through UI |
| Pass |
|
|
| ||||||||||||
| Restart VM while scaling UP CPU and RAM | 1-Login through UI | Race condition |
|
|
|
|
| 1-DB should get updated with new compute offering |
|
|
|
| Restart VM while scaling UP CPU and RAM | 1-Login through UI | 1-Should not get upgraded |
| |||||||
34 | update some vms on same host | Update (5-10) vms on same host | vm should get updated without error-exception |
| Functional | Y | Pass |
|
| Pass |
|
| ||||||||||||
| Manage-Unmanage/Disable-Enable |
|
|
|
|
Restart/power off system vms during operation( Need to test for each of them SSVM,CPVM,VR,RVR |
|
|
|
|
| Restart VM while scaling UP CPU | ||||||||||||
35 | Manage-Unmanage cluster | 1-Login through UI Scaleup vm (cpu and RAM) | 1-DB should get updated with new compute offering |
|
|
| ||||||||||||||||||
| Restart VM while scaling UP CPU | 1-Login through UI | 1-DB should get updated with new compute offering |
|
|
| ||||||||||||||||||
Manage-unmanage | 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 |
| Restart VM while scaling UP CPU | 1-Login through UI | 1-Should not get upgraded |
|
|
|
| Restart VM while scaling UP RAM | 1-Login through UI |
|
| 1-DB should get updated with new compute offering |
|
|
| Restart VM while scaling UP RAM | ||||||
37 | Attach-Detach volumes | 1-Login through UI deploy vm | all operation should go smoothly |
| Functional | Y | Pass |
| Pass | Pass |
| Pass | ||||||||||||
| VM Life cycle |
|
|
|
|
|
| 1-DB should get updated with new compute offering |
|
|
| Restart VM while scaling UP RAM | ||||||||||||
38 | stop-start | 1-Login through UI scale up cpu/ram | 1-Should not get upgraded |
|
|
| ||||||||||||||||||
| Restart VM while scaling UP CPU and RAM | 1-Login through UI | 1-DB should get updated with new compute offering |
|
|
| ||||||||||||||||||
-stop-start vm | 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 |
| Functional | Y | Pass |
| Pass | Pass |
| Pass | ||||||||||||
| Global Settings |
|
|
|
| Restart VM while scaling UP CPU and RAM | 1-Login through UI | 1-DB should get updated with new compute offering |
|
|
|
| Restart VM while scaling UP CPU and RAM | 1-Login through UI | 1-Should not get upgraded |
|
|
|
|
|
|
| ||
41 | cluster.cpu.allocated.capacity.disablethreshold |
| should not be allowed to scale up cpu beyond cpu threshold |
|
|
| hold | Global parameter is in dev process |
|
| Snapshot creation while scaling up |
|
|
|
|
| ||||||||
17 | snapshot creation while scaling up RAM | 1-Login through UI | snapshot creation should fail | P2 | Functional | Y | ||||||||||||||||||
18 | snapshot creation while scaling up RAM | 1-login through UI | snapshot creation should fail | P2 | Functional | Y | ||||||||||||||||||
19 | snapshot creation while scaling up CPU | 1-Login through UI | snapshot creation should fail | P2 | Functional | Y | ||||||||||||||||||
20 | snapshot creation while scaling up CPU | 1-Login through UI | snapshot creation should fail | P2 | Functional | Y | ||||||||||||||||||
21 | snapshot creation while scaling up RAM and CPU | 1-Login through UI | snapshot creation should fail | P2 | Functional | Y | ||||||||||||||||||
22 | snapshot creation while scaling up RAM and CPU | 1-login through UI | snapshot creation should fail | P2 | Functional | Y | ||||||||||||||||||
| Guest OS Support |
|
|
|
|
| ||||||||||||||||||
23 | Guest OS does not support scaling up | 1-Login through UI | Should through a not supported exception |
| Functional | Y | ||||||||||||||||||
42 | cluster.memery.allocated.capacity.desablethreshould |
| scaleup should not be allowed beyond 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 | Pass | Pass |
| Pass | |||||||||||||
| 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 | Y | Fail |
| N/A |
| N/A | |||||||||||||
|
|
|
|
|
|
|
|
| Migration Fails(power off /service network stop Destination host) |
|
|
|
|
| ||||||||||
25 45 | Scaling up CPU | 1-in case no resources are available on current host, live migration to next host | 1-CS should try N times | P1 | Functional | Y |
| scaling up CPU | 1-in case no resources are available on current host, live migration to next host | CPU cap | scale up vm to a SO which have cpu cap enabled | cpu limit should be set for vm |
| Functional |
| Fail | Pass | Fail | Pass 1-CS should try N times | |||||
|
|
| 26 | scaling up RAM | 1-in case no resources are available on current host, live migration to next host | 1-CS should try N times | P1 | Functional | N | |||||||||||||||
| scaling up RAM | 1-in case no resources are available on current host, live migration to next host | 1-CS should try N times |
|
|
| ||||||||||||||||||
27 | scaling up CPU and RAM | 1-in case no resources are available on current host, live migration to next host | 1-CS should try N times | P1 | Functional | Y | ||||||||||||||||||
|
|
|
|
|
|
|
|
| ||||||||||||||||
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 |
| Pass | Fail | Pass | |||||||||||||
47 | Guest OS (window-8) | Scale up a windows 8 vm | memory and ram should get registered |
| Functional | Y | -- |
|
| Pass |
|
| ||||||||||||
|
|
|
| scaling up CPU and RAM | 1-in case no resources are available on current host, live migration to next host | 1-CS should try N times |
|
|
|
| Scale Down
|
|
|
|
|
| ||||||||
48 | Global parameter | 28 | 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 |
|
|
| UPGRADE |
|
| set GP "enable.dynamic.scale.vm" to false | 1-step two should failed |
| Functional | Y | -- |
| Pass |
|
| 29 Pass | upgrade path | Pre upgrade Steps
| Memory Hot Add on VMware |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||
49 |
| 1- deploy a vm with a SO having memory = 1GB | should fail since max limit is 3 GB |
| with compute offering (before upgrade) 1-upgrade should go properly | P1 | Functional |
|
|
|
| Pass |
| Pass | ||||||||||
50 |
| 31 | Usage Event | 1- deploy a vm with a SO having memory = 1GB | scaleup should be successful |
| Functional | Waiting for FS update |
|
|
| Pass |
| Regression Pass | ||||||||||
|
|
|
|
|
| Change SO of a stop VM | 1-Stop vm |
|
|
| step 2 should besuccessfully |
|
|
| ||||||||||
51 | Restore VM property "isdyanmicallyscalable" | 1- Scale up CPU/RAMset isdynamicallyscalable to false |
| try to sale up vm | step 2 should be fail |
| Fuantional Dashboard | -- | -- |
|
|
|
|
| scale up cpu /RAM | 1-Change CO of a running VM | Dashboard should display new value of CPU and RAM according to CO values. |
|
|