XML

Word

Printable

Epic Name:
share-housekeeping-cpu
Activity Type:
Product / Portfolio Work
Acceptance Criteria:
Hide

(must-have) When VM runs with Guaranteed QoS, it shares a single CPU between housekeeping processes of virt-launcher and the guest.

(must-have) This functionality can be enabled cluster-wide.

(must-have) downstream automation.

(should-have) Implement a performance monitoring system to track CPU usage and response times when CPU sharing is active.

(should-have) Integrate a user feedback mechanism to gather insights on the CPU sharing feature's usability and performance.
Show
(must-have) When VM runs with Guaranteed QoS, it shares a single CPU between housekeeping processes of virt-launcher and the guest. (must-have) This functionality can be enabled cluster-wide. (must-have) downstream automation. (should-have) Implement a performance monitoring system to track CPU usage and response times when CPU sharing is active. (should-have) Integrate a user feedback mechanism to gather insights on the CPU sharing feature's usability and performance.
Epic Status:
To Do
Feature Link:
VIRTSTRAT-224 - Compute latency sensitive (Real Time) VMs

Goal

Save resource by sharing the housekeeping CPU between virt-launcher and the guest, when running a VM with Guaranteed QoS.

User Stories

As a cluster owner, I do not want VMs tweaked for real-time to waste full cores for QEMU housekeeping.

This assumes that the guest will always use the first CPU for its own housekeeping and not for tasks requiring real-time guarantees on latency.
This is a well established practice in OpenStack already. See "CPU real-time policy" in https://docs.openstack.org/nova/queens/user/flavors.html

1.	upstream roadmap issue	New	Unassigned
2.	upstream documentation	New	Unassigned
3.	upgrade consideration	New	Unassigned
4.	CEE/PX summary presentation	Closed	Unassigned
5.	test plans in polarion	New	Unassigned
6.	automated tests	New	Unassigned
7.	downstream documentation merged	New	Unassigned