Bug 1848922 - Setting vm to high-performance doesn't automatically set high-performance features
Summary: Setting vm to high-performance doesn't automatically set high-performance fea...
Keywords:
Status: CLOSED DUPLICATE of bug 1912828
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.4
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: 4.7.0
Assignee: Liran Rotenberg
QA Contact: Lucie Leistnerova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-19 09:31 UTC by Guilherme Santos
Modified: 2021-01-21 08:56 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-21 08:56:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github oVirt terraform-provider-ovirt pull 236 0 None closed Set high performance properties on VM creation 2021-02-02 09:06:39 UTC

Description Guilherme Santos 2020-06-19 09:31:30 UTC
Description of problem:
When installing ocp using IPI through the configuration file, it's possible to set the vm_type to high performance. However, no high performance configurations are set doing it so (cpu pinning, numa, huge pages...), only the icon changes. 
This happen because the high performance type doesn't automatically set those things in rhv anyway, when choosing high-perfomance in the UI a message guiding the user to manually set the high performance settings show up:


The following recommended settings for running the High Performance type with the optimal configuration were not detected. Please consider manually changing of the following before applying:
CPU PINNING: 
Please pin virtual CPUs to specific host(s) physical CPUs. This should be done by: 
1. selecting the "Start running on: Specific Host(s)" option 
2. Setting the "CPU Pinning topology" field and verifying that the configuration fits pinned host(s)'s configuration: 
guest number of virtual sockets <= host's number of sockets. 
guest number of cores per virtual socket <= host's number of cores per socket. 
guest number of threads per core <= host's number of threads per core.
VIRTUAL NUMA AND NUMA PINNING: 
1. Please configure virtual NUMA nodes. Note that it requires a NUMA-enabled pinned host(s). 
2. Then please pin those virtual NUMA nodes to physical NUMA nodes on the pinned host(s). 
3. Verify that virtual NUMA topology fits the host's physical NUMA topology.
HUGE PAGES: 
1. Please set huge pages configuration via the "Custom Properties" tab (huge page size is required in KB). 
2. For setting the huge page size, verify that the virtual huge pages setting fits the pinned physical host(s) setting: 
virtual huge pages size equals to the huge pages size on the pinned host(s). 
virtual memory size fits into free huge pages of the given size on the pinned host(s). 
3. Consider setting huge pages size to the biggest size that is still supported by the pinned host(s).


Version-Release number of the following components:
openshift-install-linux-4.4.0-0.nightly-2020-06-15-203705

How reproducible:
always

Steps to Reproduce:
1. Deploy ocp setting vm_type for the nodes as high-performance
2.
3.

Actual results:
No high-performance settings automatically set

Comment 1 Douglas Schilling Landgraf 2020-07-09 12:22:21 UTC
due to capacity constraints we will be revisiting this bug in the upcoming sprint

Comment 2 Sandro Bonazzola 2020-09-14 09:49:56 UTC
same as comment #1

Comment 3 Sandro Bonazzola 2020-10-22 11:33:53 UTC
due to capacity constraints we will be revisiting this bug in the upcoming sprint

Comment 4 Sandro Bonazzola 2020-12-03 12:47:05 UTC
Needs to extend API on oVirt side to allow this to happen.

Comment 6 Gal Zaidman 2021-01-21 08:56:17 UTC
This bug was for the terraform provider, we had a different bug for the installer.
The work on the tf-provider is done, marking this as a duplicate of the installer bug.
THANKS LIRAN!

*** This bug has been marked as a duplicate of bug 1912828 ***


Note You need to log in before you can comment on or make changes to this bug.