| This feature is implemented for following hypervisor |
|
|
|
|
|
|
|
|
|
|
|
Test Case ID | Test Case Name | Steps | Expected Result | Priority | Test Case Type | Automatable | XEN | Comment | KVM | Comment | VMWARE | Comment |
---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | UI/API check | 1-check cluster level settings for cpu.overprovisioning.factor mem.overprovisioning.factor
2- update overprovisioning ratio using following API for cpu name=cpu.overprovisioning.factor for memory name=mem=cpu.overprovisioning.factor 3-List cluster | 1-cluster level setting should have both settings 2-using api mentioned 2 you shoul dbe able to change overprovisioning factors 3-List cluster response should show overprovisioning factors | P1 |
| Y | Pass |
| Pass |
| Pass |
|
2 | DB check | 1-Logoin through UI 5-check user_vm_details table | 1-There should be attribute ,memoryOvercommitRatio and value for each cluster . 2-user_vm_details table should have entry for every vm with cpu/mem.overprovisioning.factor | P1 |
| Y | Pass |
| Pass |
| Pass |
|
3 | Capacity calculation | used capacity ===========service offering of vm / overcommit it got deployed with) * new overcommit (service offering of vm/overcommit value in user_vm_details table for that vm )*overCommit value in cluster details table for vm cluster Total capacity =========== (cpu/meme).overprovisioning.factor*total actual capacity
|
1-calculate total capacity for cluster,pod,zone it should follow the same formula
| P1 | ||||||||
| Deploy VM in cluster |
|
|
|
|
|
|
|
|
|
|
|
4 | Deploy vm in a cluster with a service offering( | 1-Create a cluster with overcommit factor x | 1- VM in step 3 should get deployed | P1 | Functional | Y | Pass |
| Pass | Pass(need some discussion ) | https://issues.apache.org/jira/browse/CLOUDSTACK-3415 | |
5 | Deploy VM in cluster with service offering(ram =y) | 1-Create a cluster with overcommit factor x | 1- Deployment of vm in step 3 should fail. | P1 | Functional | Y | Pass |
| Block |
| Pass |
|
6 | Deploy vm in a cluster with a service offering( | 1-Create a cluster with overcommit factor x | 1- VM in step 3 should get deployed | P1 | Functional | Y | Pass |
| Pass |
| Fail | |
7 | Deploy vm in a cluster with a service offering( | 1-Create a cluster with overcommit factor x | 1- Deployment of vm in step 3 should fail. | P1 | Functional | Y | Pass |
| Pass |
| Pass |
|
9 | Addition of host to cluster | 1- add host which have overcommit capacity (having licence) | 1-Should fail xen does not support mixed licensing | P2 | Fuctional | Y | Pass |
| N/A |
| N/A |
|
11 | weight | 1-Deploy vms with different service offerings | vm with different cpu speed (cpu speed*vcp ) should get different weight | P2 | Functional | Y | Fail | Pass |
| Pass |
| |
| "overcommit ratio update " effect on existing and new vms and capacity calculation |
|
|
|
|
|
|
|
|
|
|
|
|
| 1-Login Through UI | 1-VMs deployed in step-3 should have entry in user_vm_detail with overcommit x |
|
|
|
|
|
|
|
|
|
12 |
| 5-when y<x (for Memory) |
| P1 | Functional | Y | Pass |
| Block |
| Pass |
|
13 |
| 5-when y<x (for CPU) |
| P1 | Functional | Y | Pass |
| Pass |
| Pass |
|
14 |
| 5-when y>x (for Memory) |
and an entry should be created in user_vm_Detail table with memory overcommit y 2-step 6 capacity calculation should be successfulaccording to test case 3 "capacity Calculation " | P2 | Functional | Y | Pass |
| Block |
| Pass |
|
15 |
| 5-when y>x (For CPU) | 1-VM deployed in step -3 should not have any effect of 6 should be successfuland an entry should be created in user_vm_Detail table with cpu overcommit y 2-step 6 capacity calculation should be successfulaccording to test case 3 "capacity Calculation " | P1 | Functional | Y | Pass |
| Pass |
| Pass |
|
| VM Life cycle |
|
|
|
|
|
|
|
|
|
|
|
|
| 1-set cluster overcommit ratio x | 1-VMs deployed in step-3 should have entry in user_vm_detail with overcommit x |
|
|
|
|
|
|
|
|
|
16 | Reboot | 4-Reboot all the vms , deployed in step 2 when x>y | 1-VM should use previous overcommit ratio(x),should come up without failure Overcommit value should not get change for the vm in user vm details table vm
| P2 | Functional | Y | Pass |
| Pass |
|
|
|
17 | Reboot | 4-Reboot all the vms in deployed in step 2 when x<y | 1-VM should use previous overcommit ratio(x),should come up without failure.Overcommit value should not get change for the vm in user vm details table vm | P2 | Functional | Y | Pass |
| Pass |
| Pass |
|
18 | stop/start | 4-Stop and start all the vms in deployed in step 2 when x>y | 1-VM should use current overcommit ratio(y), | P2 | Functional | Y | Pass for Memory | Fail | Pass |
| ||
19 | stop/start | 4-Stop and start all the vms in deployed in step 2 when x<y | 1-VM should use current overcommit ratio(y). | P2 | Functional | Y | Pass |
| Pass |
| Pass |
|
20 | destroy/restore ->start | 4-Destroy and restore and start all the vms in deployed in step 2 when x>y | 1-VM should use current overcommit ratio(y), | P2 | Functional | Y | Pass for memory | Fail | Pass |
| ||
21 | destroy/restore ->start | 1-destroy/restore->start all the vms in deployed in step 2 when x<y | 1-VM should use current overcommit ratio(y). | P2 | Functional | Y | Pass |
| Pass |
| Pass |
|
22 | (manage/unmanage-Disable/enable cluster) | 1-Create a cluster with overcommit ratio x | 1-Overcommit ratio should not change | P2 | Functional | Y | Pass | Pass |
| Pass |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
23 | upgrade path | Pre upgrade steps | 1- Upgrade should be successful . |
| Upgrade | Y | Pass (RAM) | CPU testing is blocked because of issue https://issues.apache.org/jira/browse/CLOUDSTACK-1695 |
|
| Block | Waiting for new system vm template. |
|
|
|
|
|
|
|
|
|
|
|
|
|
24 | Number of max VM can be deployed (CPU overcommit factor x, actual cpu C) in case enough RAM available. | 1- Deploy a vm with a SO where cpu=y . | number of vm must be limited by n*y*vcpu/x<C (nummber of vm *lower value of ram*vcpu < total cpu in cluster) | P2 | Functional | Y | Pass |
| Pass |
| *Pass |
|
25 | Number of max VM can be deployed (RAM overcommit factor x, actual ram M) if enough CPUs are available. | 1- Deploy vms with a SO where ram=y , | number of vm must be limited by n*y/x<M (nummber of vm *lower value of ram < total available memory on current host) | P2 | Functional | Y | Pass |
| Block |
| Pass |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
26 | Dash board display | 1-set overcommit ratio to x | 1-Overcommited values should get displayed at zone/pod/cluster level with % of use based on overcommited values | P2 | Functional | Y | Fail | Fail |
| Fail | ||
27 | overcommit ratio <1 | 1-Craete a cluster with overcommit ratio x | 1-Cs should not allow to set overcommit ratio <1 | P3 | Functional | Y | Fail | Fail |
| Fail |
| |
28 | cluster.cpu.allocated.capacity.disablethreshold | set cluster.cpu.allocated.capacity.disablethreshold | 1-Should be calculated based on overcommit ratio | P2 | Functional | Y | Pass | https://issues.apache.org/jira/browse/CLOUDSTACK-1704 | Pass |
| Pass |
|
29 | cluster.cpu.allocated.capacity.notificationThreshold | set cluster.cpu.allocated.capacity.notificationThreshold | 1-should be calculated based on overcommit ratio | P2 | Functional | Y | Fail | Fail |
| Fail |
| |
30 | cpu.overpovisioning .factor | set cpu.overpovisioning .factor to some value | 1-Expected to be there in Global settings | P2 | Functional | Y | Pass | Pass |
| Pass |
| |
31 | cluster.memory.allocated.capacity.disablethreshold | set | 1-should be calculated based on overcommited memory | P2 | functional | Y | Pass | Pass |
| Pass |
| |
32 | cluster.memory.allocated.capacity.notificationthreshold | set cluster.memory.allocated.capacity.notificationthreshold | 1-should be calculated based on overcommited memory | P2 | Functional | Y | Fail | Block |
| Fail |
|