Skip to content

CLOUDSTACK-8689: Verify effect of changing value of XenServer Max guest limit#638

Closed
pritisarap12 wants to merge 3 commits into
apache:masterfrom
pritisarap12:CLOUDSTACK-8689-Verify-effect-of-changing-value-of-XenServer-Max-guest-limitis-on-previously-added-hosts
Closed

CLOUDSTACK-8689: Verify effect of changing value of XenServer Max guest limit#638
pritisarap12 wants to merge 3 commits into
apache:masterfrom
pritisarap12:CLOUDSTACK-8689-Verify-effect-of-changing-value-of-XenServer-Max-guest-limitis-on-previously-added-hosts

Conversation

@pritisarap12
Copy link
Copy Markdown

Verify effect of changing value of "Max guest limit" of XenServer on previously added hosts
-Check if it reads changed value and act accordingly

@asfbot
Copy link
Copy Markdown

asfbot commented Jul 30, 2015

cloudstack-pull-rats #153 SUCCESS
This pull request looks good

@asfbot
Copy link
Copy Markdown

asfbot commented Jul 30, 2015

cloudstack-pull-requests #851 SUCCESS
This pull request looks good

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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"

@asfbot
Copy link
Copy Markdown

asfbot commented Jul 30, 2015

cloudstack-pull-analysis #86 SUCCESS
This pull request looks good

@pritisarap12 pritisarap12 force-pushed the CLOUDSTACK-8689-Verify-effect-of-changing-value-of-XenServer-Max-guest-limitis-on-previously-added-hosts branch from e2c578f to 2705232 Compare July 30, 2015 11:39
@asfbot
Copy link
Copy Markdown

asfbot commented Jul 30, 2015

cloudstack-pull-rats #161 SUCCESS
This pull request looks good

@pritisarap12 pritisarap12 force-pushed the CLOUDSTACK-8689-Verify-effect-of-changing-value-of-XenServer-Max-guest-limitis-on-previously-added-hosts branch from 2705232 to 0c81b51 Compare July 30, 2015 11:46
@asfbot
Copy link
Copy Markdown

asfbot commented Jul 30, 2015

cloudstack-pull-rats #162 SUCCESS
This pull request looks good

@asfbot
Copy link
Copy Markdown

asfbot commented Jul 30, 2015

cloudstack-pull-requests #859 SUCCESS
This pull request looks good

@asfbot
Copy link
Copy Markdown

asfbot commented Jul 30, 2015

cloudstack-pull-requests #860 SUCCESS
This pull request looks good

@asfbot
Copy link
Copy Markdown

asfbot commented Jul 30, 2015

cloudstack-pull-analysis #94 SUCCESS
This pull request looks good

@asfbot
Copy link
Copy Markdown

asfbot commented Jul 30, 2015

cloudstack-pull-analysis #95 SUCCESS
This pull request looks good

@nitt10prashant
Copy link
Copy Markdown
Contributor

can you post test results ?

@asfbot
Copy link
Copy Markdown

asfbot commented Jul 31, 2015

cloudstack-pull-rats #168 SUCCESS
This pull request looks good

@pritisarap12
Copy link
Copy Markdown
Author

Modified test to check for empty vmList and updating maxguestlimit accordingly.
And the test result is-

Test hypervisor max limits effect ... === TestName: test_check_hypervisor_max_limit_effect | Status : SUCCESS ===
ok


Ran 1 test in 142.770s

OK

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@asfbot
Copy link
Copy Markdown

asfbot commented Jul 31, 2015

Sanjeev N on dev@cloudstack.apache.org replies:
How your logic works if there are no system vms on a host (ssvm, cpvm and
VR)? I mean if the cluster has more than one host and system vms were
deployed on another host in the cluster?

@asfbot
Copy link
Copy Markdown

asfbot commented Jul 31, 2015

cloudstack-pull-requests #866 SUCCESS
This pull request looks good

@asfbot
Copy link
Copy Markdown

asfbot commented Jul 31, 2015

cloudstack-pull-analysis #101 SUCCESS
This pull request looks good

…t-limitis-on-previously-added-hosts

	-Addning check for empty list and increamenting maxguestlimit
	accordingly
@pritisarap12 pritisarap12 force-pushed the CLOUDSTACK-8689-Verify-effect-of-changing-value-of-XenServer-Max-guest-limitis-on-previously-added-hosts branch from 54f6714 to 15785b3 Compare July 31, 2015 10:14
@asfbot
Copy link
Copy Markdown

asfbot commented Jul 31, 2015

cloudstack-pull-rats #170 SUCCESS
This pull request looks good

@pritisarap12
Copy link
Copy Markdown
Author

Updated the testcase for:
-Count SSVM's on selected host
-Count VR on the host
-Count user VM's on the host
-Then update the maxguestlimit for that host as(ssvm+vr+user_vm+1)
-Added validateList for host list

@pritisarap12
Copy link
Copy Markdown
Author

Testcase Result-

Test hypervisor max limits effect ... === TestName: test_check_hypervisor_max_limit_effect | Status : SUCCESS ===
ok

Ran 1 test in 159.787s

OK

@asfbot
Copy link
Copy Markdown

asfbot commented Jul 31, 2015

cloudstack-pull-requests #868 SUCCESS
This pull request looks good

@nitt10prashant
Copy link
Copy Markdown
Contributor

LGTM

@asfbot
Copy link
Copy Markdown

asfbot commented Jul 31, 2015

cloudstack-pull-analysis #103 SUCCESS
This pull request looks good

@asfbot
Copy link
Copy Markdown

asfbot commented Jul 31, 2015

Sanjeev N on dev@cloudstack.apache.org replies:
LGTM

@asfbot
Copy link
Copy Markdown

asfbot commented Aug 3, 2015

cloudstack-pull-rats #182 FAILURE
Looks like there's a problem with this pull request

…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
@asfbot
Copy link
Copy Markdown

asfbot commented Aug 3, 2015

cloudstack-pull-requests #880 FAILURE
Looks like there's a problem with this pull request

@pritisarap12 pritisarap12 force-pushed the CLOUDSTACK-8689-Verify-effect-of-changing-value-of-XenServer-Max-guest-limitis-on-previously-added-hosts branch from 20b1e4a to d9013d1 Compare August 3, 2015 06:34
@asfbot
Copy link
Copy Markdown

asfbot commented Aug 3, 2015

cloudstack-pull-rats #183 ABORTED

@asfbot
Copy link
Copy Markdown

asfbot commented Aug 3, 2015

cloudstack-pull-requests #881 ABORTED

@asfbot
Copy link
Copy Markdown

asfbot commented Aug 3, 2015

cloudstack-pull-analysis #115 SUCCESS
This pull request looks good

@asfbot
Copy link
Copy Markdown

asfbot commented Aug 3, 2015

cloudstack-pull-analysis #116 FAILURE
Looks like there's a problem with this pull request

@asfgit asfgit closed this in c5ebb68 Aug 3, 2015
yadvr pushed a commit that referenced this pull request Jan 20, 2021
… 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants