[XenServer/XCP-ng] Sync the 'platform' setting according to the 'cpu.corespersocket' setting#5892
Conversation
|
@blueorangutan package |
|
@nvazquez a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
2cents - could this VM property/setting bypass what an admin/operator may not intend? For example, if this setting is set on a template (vs global setting if any) and then bypassed by the user - could user benefit from this setting in a way that admin wouldn't intend to be used? |
|
@rohityadavcloud the 'cores-per-socket' value could be bypassed or modified but it is restricted by the offering, since a VM won't start if the number of CPUs is not a multiple of the cores per socket number. I think perhaps the 'platform' setting could lead to unintended situations as it includes more information, for example: I've checked both settings are visible and editable for users, do you think the 'platform' should be hidden for non-admins? |
|
Packaging result: ✖️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 2289 |
|
@blueorangutan package |
|
@nvazquez a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 2291 |
|
@blueorangutan test centos7 xcpng82 |
|
@nvazquez a Trillian-Jenkins test job (centos7 mgmt + xcpng82) has been kicked to run smoke tests |
|
Trillian Build Failed (tid-2979) |
|
@blueorangutan test centos7 xcpng82 |
|
@nvazquez a Trillian-Jenkins test job (centos7 mgmt + xcpng82) has been kicked to run smoke tests |
|
Trillian test result (tid-2994)
|
|
Packaging result: ✖️ el7 ✔️ el8 ✖️ debian ✔️ suse15. SL-JID 2348 |
|
@blueorangutan package |
|
@sureshanaparti a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✖️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 2351 |
|
@blueorangutan package |
|
@nvazquez a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✖️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 2353 |
|
@blueorangutan package |
|
@sureshanaparti a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 2356 |
|
@blueorangutan test centos7 xcpng82 |
|
@sureshanaparti a Trillian-Jenkins test job (centos7 mgmt + xcpng82) has been kicked to run smoke tests |
|
@blueorangutan package |
|
@sureshanaparti a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 2403 |
|
@blueorangutan test centos7 xcpng82 |
|
@nvazquez a Trillian-Jenkins test job (centos7 mgmt + xcpng82) has been kicked to run smoke tests |
|
Trillian test result (tid-3075)
|
|
@blueorangutan test centos7 xcpng82 |
|
@sureshanaparti a Trillian-Jenkins test job (centos7 mgmt + xcpng82) has been kicked to run smoke tests |
|
@blueorangutan test centos7 xcpng82 |
|
@sureshanaparti a Trillian-Jenkins test job (centos7 mgmt + xcpng82) has been kicked to run smoke tests |
|
Trillian test result (tid-3108)
|
The failed test ^^^ is unrelated to this PR. It is intermittent and seems to be environment issue (unable to connect to hosts). Noticed this failure in other PR test results (in xcpng82) as well. |
|
Merging this based on the approvals, smoke test results and tests covered by @nvazquez. |
Description
The 'platform' setting is retrieved after a VM is stopped with the platform parameters obtained from Xen/XCP for a certain VM. If a user added the setting 'cpu.corespersocket', it was ignored and the setting was never applied as it was mutually exclusive with the platform 'setting'.
This PR fixes the previous behavior, in the following way:
Fixes: #5695
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?