Bug 1693377

Summary:	[RFE] Add ability to use pinned and non-pinned CPUs in the same instance
Product:	Red Hat OpenStack	Reporter:	Stephen Finucane <stephenfin>
Component:	openstack-nova	Assignee:	Stephen Finucane <stephenfin>
Status:	CLOSED ERRATA	QA Contact:	James Parker <jparker>
Severity:	high	Docs Contact:
Priority:	high
Version:	17.0 (Wallaby)	CC:	alifshit, cfontain, dasmith, dhill, ealcaniz, eelena, egallen, eglynn, fherrman, igallagh, jhakimra, joflynn, jparker, kchamart, lyarwood, mariel, nlevinki, sbauza, sgordon, smooney, spower, vromanso
Target Milestone:	beta	Keywords:	FutureFeature, Triaged
Target Release:	17.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-nova-23.2.3-1.20230517181040.7e3a8a1.el9ost	Doc Type:	Enhancement
Doc Text:	With this update, an instance can have a mix of shared (floating) CPUs and dedicated (pinned) CPUs instead of only one CPU type. RHOSP administrators can use the `hw:cpu_policy=mixed` and `hw_cpu_dedicated_mask` flavor extra specs to create a flavor for instances that require a mix of shared CPUs and dedicated CPUs.	Story Points:	---
Clone Of:
Clones:	1821532 1905212 (view as bug list)		Environment:
Last Closed:	2023-08-16 01:09:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:	Victoria
Embargoed:
Bug Depends On:	1693372, 1700729, 1781356, 1782656, 2135439
Bug Blocks:	1793700, 1821532, 1905212

Description Stephen Finucane 2019-03-27 16:55:32 UTC

Description of problem:

Currently, instances can be either pinned or unpinned. It is not possible to state that N cores and unpinned while the remainder are pinned. This is suboptimal since pinned cores cannot be overcommitted. For things like realtime, where we insist on some cores being marked as non-realtime, the non-realtime cores don't necessarily have to be pinned and we could improve resource utilization by allowing some cores to be shared.

Comment 1 Stephen Finucane 2019-10-01 13:29:35 UTC

Dropping [TechPreview] tag since this didn't meet the cut for OSP16 and therefore we need to fully reassess for OSP 17.

Comment 4 Stephen Finucane 2020-07-24 13:17:50 UTC

This has landed upstream now. Need to get it into a build and transition to MODIFIED.

Comment 5 Karrar Fida 2022-01-12 11:55:13 UTC

@smooney is this feature ready and will it be present in the 17.0 compose? If so is NFV required to test this feature?

Comment 7 spower 2022-05-11 11:08:30 UTC

As announced in the OSP PgM Call , this RFE is not marked as an MVP for OSP 17.0 and so is being considered for verification in OSP 17.1.

Comment 28 errata-xmlrpc 2023-08-16 01:09:21 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2023:4577