| This feature is implemented for following hypervisor |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||||||||||
Test Case ID | Test Case Name | Steps | Expected Result | Priority | Note | Test Case Type | Automatable | XEN | Comment | KVM | Comment | VMWARE | Comment | |||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
21 | UI/API check | 1- update overcommit ratio using API updateCluster with parameter cpuovercommitratio,memoryovercommitratio. | response should contain " details of the updated cluster along with the overcommit ratios" | P1 |
| Y | Pass |
| Pass |
| Pass |
| 3 | DB check | 1-Logoin through UI | 1-There should be attribute ,name,value for each cluster . | 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 be able to change overprovisioning factors 3-List cluster response should show overprovisioning factors | P1 | pass | P1
| Y | Pass |
| Pass |
| Pass |
| ||||||||
| Deploy VM in cluster |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||||||||||
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 |
| 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 |
| ||||||||||||||||||||||||
| 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/mem).overprovisioning.factor*total actual capacity
|
1-calculate total capacity for cluster,pod,zone it should follow the same formula
| P1 | ||||||||||||||||||||||||||||||||
| Deploy VM in cluster |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||||||||||
46 | 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 )Fail | https://issues.apache.org/jira/browse/CLOUDSTACK-18223415 | ||||||||||||||||||||||||
75 | Deploy vm 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 |
| PassBlock |
| 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 | |||||||||||||||||||
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 | FunctionalFuctional | Y | Pass |
| N/APass |
| Fail | 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 | https://issues.apache.org/https://issues.apache.org/jira/browse/CLOUDSTACK-16461822 | Pass |
| Pass |
| ||||||||||
| "overcommit ratio update " effect on existing and new vms |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||||||||||
7 | Deploy vm in a cluster with a service offering( | 1 |
|
| 1-Login Through UI |
|
|
|
|
|
|
|
|
|
| 2- say total available CPU on host is z | 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 | 12 |
| 5-when y<x (for Memory) | 1-VM deployed in step-3 should not have any effect of y | P1 | Functional | Y | Pass | Block | N/A | Pass | N/A |
| ||||||||||||||||||
1311 | weight | 5-when y<x (for CPU) | 1-VM deployed in step-3 should not have any effect of y | P11-Deploy vms with different service offerings | vm with different cpu speed (cpu speed*vcp ) should get different weight | P2 | Functional | Y | Pass | Fail | Pass |
| Pass |
| ||||||||||||||||||||||
14 |
| 5-when y>x (for Memory) | 1-VM deployed in step-3 should not have any effect of y | P2 | Functional | Y | Pass |
| Block |
| Pass |
| ||||||||||||||||||||||||
| "overcommit ratio update " effect on existing and new vms and capacity calculation |
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||||||||||
|
| 1-Login Through UI | 1-VMs | 15 |
| 5-when y>x (For CPU) | 1-VM deployed in step-3 should not have any effect of y | P1 | Functional | Y | Pass |
| Pass |
| Passhave entry in user_vm_detail with overcommit x |
|
| VM Life cycle |
|
|
|
|
|
| ||||||||||||
12 |
|
|
|
| ||||||||||||||||||||||||||||||||
|
| 1-set cluster overcommit ratio x |
|
|
|
|
|
|
|
|
|
| ||||||||||||||||||||||||
5-when y<x (for Memory) |
| P1 | Functional | Y | Pass |
| Block |
| Pass |
| ||||||||||||||||||||||||||
13 |
| 5-when y<x (for CPU) |
| P1 | 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 | P2 | Functional | Y | Pass |
| Pass |
| Pass |
| |||||||||||||||||||
1714 | 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. | P2 | 5-when y>x (for Memory) |
and an entry should be created in user_vm_Detail table with memory overcommit y 2-capacity calculation should be according to test case 3 "capacity Calculation " | P2 | Functional | Y | Pass |
| PassBlock |
| Pass |
| |||||||||||||||||||||
1815 | stop/start 4-Stop and start all the vms in deployed in step 2 when x>y | 5-when y>x (For CPU) | 1-VM should use current overcommit ratio(y), 2-capacity calculation should be according to test case 3 "capacity Calculation " | P1 | 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 |
| ||||||||||||||||||||||||
| 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 , | 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 |
| Overcommit value should not get changed for the vms in user vm details table vm
| P2 | Functional | Y | Pass |
| Pass |
|
|
| |||||||||||||
17 | Reboot | 4-Reboot | 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 |
| |||||||||||||||||||||
2218 | (manage/unmanage-Disable/enable cluster) | 1-Create a cluster with overcommit ratio x | 1-Overcommit ratio should not change | P2 | Functional | Y | Pass | stop/start | 4-Stop and start all the vms in deployed in step 2 when x>y | 1-Overcommit value should be changed to y for the vms in user vm details table | P2 | Functional | Y | Pass for Memory | Pass | Fail | Pass |
| ||||||||||||||||||
19 |
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||||||||||
stop/start | 4-Stop and start all the vms in deployed in step 2 when x<y | 1-Overcommit value should be changed to y for the vms in user vm details table 2-all VM should come up without failure | 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-Overcommit value should be changed to y for the vms in user vm details table | 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-Overcommit value should be changed to y for the vms in user vm details table | P2 | Functional | Y | Pass |
| Pass |
| Pass |
| ||||||||||||||||||||||||
22 | (manage/unmanage-Disable/enable cluster) | 1-Create a cluster with overcommit ratio x | 1-Overcommit value should not get changed for the vms in user vm details table | P2 | pass | Functional | Y | Pass | Pass |
| Pass |
| ||||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||||||||||
23 | upgrade path | Pre upgrade steps 3-set cpu overcommit to x 4- set vmware.reserve.(mem/cpu) to true | 1- Upgrade should be successful 2-check cluster and global level settings it should list (cpu/mem).overcommit.factor and vmware.reserve.(cpu/mem) with same values as before upgrade |
| 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 |
| ||||||||||||||||||||||||
|
|
|
|
|
|
|
|
|
|
|
|
| ||||||||||||||||||||||||
|
|
|
| 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 for multi cluster environment | 1- Add xen , vmware, kvm clusters 2- set (cpu/meme) overpovisioning to x for xen cluster and check zone total capacity 3- set (cpu/mem)overpovisioning to x for kvm cluster and check zone total capacity 4- set (cpu/mem)overpovisioning to x for vmware cluster and check zone total capacity | 1-Total capacity should be[ x.(xen cluster capacity)+kvm cluster capacity+vmware cluster capacity] 2-In step 1-Total capacity should be[ x.(kvm cluster capacity)+xen cluster capacity+vmware cluster capacity] 3-in step 4-Total capacity should be [x.(vmware cluster capacity)+kvm cluster capacity+xen cluster capacity] | P2 | pass | 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 | pass | 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 | 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 |
| 1704Fail | 27 | overcommit ratio <1 | 1-Craete a cluster with overcommit ratio x | 1-Cs should not allow to set overcommit ratio <1 | Pass |
| Pass |
| ||||||||||
29 | cluster.cpu.allocated.capacity.notificationThreshold | set cluster.cpu.allocated.capacity.notificationThreshold | 1-should be calculated based on overcommit ratio | P2 | P3 | Functional | Y | Fail | Fail |
| Fail |
| ||||||||||||||||||||||||
2830 | cluster.cpu.allocatedoverpovisioning .capacity.disablethresholdfactor | set cluster. cpu.allocated.capacity.disablethreshold | 1-Should be calculated based on overcommit ratioExpected to be there in Global settings | P2 | pass | Functional | Y | Pass | https://issues.apache.org/jira/browse/CLOUDSTACK-1704 | Pass |
| Pass |
| |||||||||||||||||||||||
2931 | cluster.cpumemory.allocated.capacity.notificationThresholddisablethreshold | set | 1-should be calculated based on overcommit ratioovercommited memory | P2 | Functionalfunctional | Y | FailPass | FailPass |
| FailPass |
| 30 | cpu.overpovisioning .factor | set cpu.overpovisioning .factor to some value | 1-Expected to be there in Global settings | |||||||||||||||||||||
32 | cluster.memory.allocated.capacity.notificationthreshold | set cluster.memory.allocated.capacity.notificationthreshold | 1-should be calculated based on overcommited memory | P2 | P2 | Functional | Y | PassFail | PassBlock |
| PassFail | 31 | ||||||||||||||||||||||||
34 | clustervmware. | memory.allocated.capacity.disablethresholdset | 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 |
| Failreserver.cpu
| 1-set cpu.overpovisioning .factor to x>1 2- set vmware.reserver.cpu to false and deploy vm 3-set vmware.reserver.cpu to true and deploy vm | 1-In step 2 vm should get deployed and no cpu resource should get reserved for the vm 2-in step 3 vm should get deployed and cpu =cpu in so/x resource should get reserved for the vm | P1 | pass | Functional | Y | ||||||||
35 | vmware.reserver.mem | 1-set cpu.overpovisioning .factor to x>1 2- set vmware.reserver.mem to false and deploy vm 3-set vmware.reserver.memto true and deploy vm | 1-In step 2 vm should get deployed and no mem resource should get reserved for the vm 2-in step 3 vm should get deployed and mem= mem in so/x resource should get reserved for the vm | P! | pass | Functional | Y |