CLOUDSTACK-8689: Verify effect of changing value of XenServer Max guest limit#638
Conversation
|
cloudstack-pull-rats #153 SUCCESS |
|
cloudstack-pull-requests #851 SUCCESS |
There was a problem hiding this comment.
If there are more than one host in a cluster, how can you make sure that all the vm deployments will go to the same host to test this functionality? IMO , it would be better to tag the host and try to deploy vms on it.
There was a problem hiding this comment.
Also we need to check if there are any vms running on a chosen host(including system vms and guest vms) and then try to deploy the vms until we reach the max supported value.
There was a problem hiding this comment.
Added the suggested changes
-Verify all VM's go to same host
-Count previously existing VM's on the selected host and then modify its "maxguestlimit"
|
cloudstack-pull-analysis #86 SUCCESS |
e2c578f to
2705232
Compare
|
cloudstack-pull-rats #161 SUCCESS |
…st limitis on previously added hosts
2705232 to
0c81b51
Compare
|
cloudstack-pull-rats #162 SUCCESS |
|
cloudstack-pull-requests #859 SUCCESS |
|
cloudstack-pull-requests #860 SUCCESS |
|
cloudstack-pull-analysis #94 SUCCESS |
|
cloudstack-pull-analysis #95 SUCCESS |
|
can you post test results ? |
|
cloudstack-pull-rats #168 SUCCESS |
|
Modified test to check for empty vmList and updating maxguestlimit accordingly. Test hypervisor max limits effect ... === TestName: test_check_hypervisor_max_limit_effect | Status : SUCCESS === Ran 1 test in 142.770s OK |
There was a problem hiding this comment.
If we assume that there are 2 SSVMs and 1 VR on the host then vmCount becomes 3. You are adding 4 to vmCount. So newValue becomes 7. That means max. guest limit on the host is 7.
There was a problem hiding this comment.
listVirtualMachines API does not list 2 SSVMs and 1 VR it only list the User deployed VM's hence I am adding 4 to vmCount.
|
Sanjeev N on dev@cloudstack.apache.org replies: |
|
cloudstack-pull-requests #866 SUCCESS |
|
cloudstack-pull-analysis #101 SUCCESS |
…t-limitis-on-previously-added-hosts -Addning check for empty list and increamenting maxguestlimit accordingly
54f6714 to
15785b3
Compare
|
cloudstack-pull-rats #170 SUCCESS |
|
Updated the testcase for: |
|
Testcase Result- Test hypervisor max limits effect ... === TestName: test_check_hypervisor_max_limit_effect | Status : SUCCESS === Ran 1 test in 159.787s OK |
|
cloudstack-pull-requests #868 SUCCESS |
|
LGTM |
|
cloudstack-pull-analysis #103 SUCCESS |
|
Sanjeev N on dev@cloudstack.apache.org replies: |
|
cloudstack-pull-rats #182 FAILURE |
…tlimits on previously added hosts -As testcase is changing maxguestlimits global setting it will affect on other testcases also hence moving it to component/maint folder
|
cloudstack-pull-requests #880 FAILURE |
20b1e4a to
d9013d1
Compare
|
cloudstack-pull-rats #183 ABORTED |
|
cloudstack-pull-requests #881 ABORTED |
|
cloudstack-pull-analysis #115 SUCCESS |
|
cloudstack-pull-analysis #116 FAILURE |
… on (#638) Remove the primary store on which the volume is currently present on from the list of possible storage pools to migrate volume. Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>
Verify effect of changing value of "Max guest limit" of XenServer on previously added hosts
-Check if it reads changed value and act accordingly