Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow setting virtual NUMA nodes without host pinning #402

Merged
merged 1 commit into from Jun 9, 2022

Conversation

liranr23
Copy link
Member

This patch will allow setting via UI and API virtual NUMA nodes to a VM
without having the VM pinned to a host. If a numa_node_pin is set, the
scheduler will filter out hosts that won't fit to the NUMA pinning.
Otherwise, the VM will start with the set amount of virtual NUMA nodes.

Change-Id: Ia35a95babf3ae6b2d4713c809052be1d6ddede38
Bug-Url: https://bugzilla.redhat.com/2081410
Signed-off-by: Liran Rotenberg lrotenbe@redhat.com

@liranr23
Copy link
Member Author

/ost

Copy link
Collaborator

@ljelinkova ljelinkova left a comment

Choose a reason for hiding this comment

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

I am a bit worried about his lines:

if (!model.getIsNew() && !model.getIsClone() && model.getNumaEnabled().getEntity() &&

Could you please test if the edit of the NUMA count works if the VM is not pinned to a host?

@liranr23
Copy link
Member Author

I am a bit worried about his lines:

if (!model.getIsNew() && !model.getIsClone() && model.getNumaEnabled().getEntity() &&

Could you please test if the edit of the NUMA count works if the VM is not pinned to a host?

Of course I did when I set the verified label on the PR :)

@ljelinkova
Copy link
Collaborator

I am a bit worried about his lines:

if (!model.getIsNew() && !model.getIsClone() && model.getNumaEnabled().getEntity() &&

Could you please test if the edit of the NUMA count works if the VM is not pinned to a host?

Of course I did when I set the verified label on the PR :)

Hmm, it probably works because of the following lines:

https://github.com/oVirt/ovirt-engine/blob/d4af9a4658b31986f1770677ca0801922cb5f85e/frontend/webadmin/modules/uicommonweb/src/main/java/org/ovirt/engine/ui/uicommonweb/models/vms/UnitVmModel.java#L3829

I am not a big fan of how the logic for NUMA is scattered throughout the code.

Anyway, sorry I've doubted you :-) (no really, there are so many different paths that can be tested in the VM dialog that it is easy to miss some of them).

This patch will allow setting via UI and API virtual NUMA nodes to a VM
without having the VM pinned to a host. If a `numa_node_pin` is set, the
scheduler will filter out hosts that won't fit to the NUMA pinning.
Otherwise, the VM will start with the set amount of virtual NUMA nodes.

Change-Id: Ia35a95babf3ae6b2d4713c809052be1d6ddede38
Bug-Url: https://bugzilla.redhat.com/2081410
Signed-off-by: Liran Rotenberg <lrotenbe@redhat.com>
@liranr23
Copy link
Member Author

liranr23 commented Jun 8, 2022

/ost

1 similar comment
@liranr23
Copy link
Member Author

liranr23 commented Jun 8, 2022

/ost

@ahadas ahadas merged commit 5d0ad35 into oVirt:master Jun 9, 2022
@liranr23 liranr23 deleted the allow_vnuma branch June 13, 2022 06:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants