Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1693377

Summary: [RFE] Add ability to use pinned and non-pinned CPUs in the same instance
Product: Red Hat OpenStack Reporter: Stephen Finucane <sfinucan>
Component: openstack-novaAssignee: nova-maint
Status: NEW --- QA Contact: nova-maint
Severity: high Docs Contact:
Priority: high    
Version: 16.0 (T)CC: dansmith, eglynn, jhakimra, kchamart, lyarwood, rbryant, sbauza, sgordon, vromanso
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1693372    
Bug Blocks:    

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.