Bug 1925201 - [OCPonRHV] - High Performance Mode in OCP on RHV - CPU and Numa pinning configuration
Summary: [OCPonRHV] - High Performance Mode in OCP on RHV - CPU and Numa pinning confi...
Status: CLOSED DUPLICATE of bug 1925203
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.0
Assignee: Liran Rotenberg
QA Contact: michal
Depends On: 1941334
TreeView+ depends on / blocked
Reported: 2021-02-04 15:12 UTC by michal
Modified: 2021-04-14 10:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-04-14 10:14:36 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description michal 2021-02-04 15:12:11 UTC
Description of RFE:
When installing OCP using IPI through the configuration file, it's possible to set the vm_type to high performance.
Currently, this just aligns what we do by default in the UI.
We want to also to add CPUs/NUMAs pining by default to the VM, and make this feature configurable through the install config.
CPUs/NUMAs pining has 3 options:
- Disabled.
- Existing(Default) - takes the current CPU topology and pins it (no changes made to CPU).
- Adjust - changes the CPU topology to be the maximum available.

By default when a user creates a high-performance VM the VM will be created with "Existing" CPUs/NUMAs pining.
With using the install config the user will be able to specify Disabled|Existing|Adjust.

A side effect of CPUs/NUMAs pining is Host pining, this is something that is required from the RHV engine, whenever you specify CPUs/NUMAs pining you need to select Host pining.
Host pining can be set to a specific host in the cluster or to a group of hosts in the cluster.
We will set Host pining to all the hosts in the cluster, this is to not interfere with the Affinity Groups logic, and because we need Host pining just to make CPUs/NUMAs pining work.
This will mean that when a new host is added to the RHV cluster and we want VMs to be schedulable on that host, we must add that host to the VMs - this will need to be a part of the documentation

Comment 1 Gal Zaidman 2021-03-30 14:13:32 UTC
due to capacity constraints, we will be revisiting this bug in the upcoming sprint

Comment 2 Gal Zaidman 2021-04-14 10:14:36 UTC

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

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