Bug 1955690

Summary:	[RFE] Support live migration from an host without pinset information to one without
Product:	Red Hat OpenStack	Reporter:	Stephen Finucane <stephenfin>
Component:	openstack-nova	Assignee:	Sylvain Bauza <sbauza>
Status:	CLOSED DUPLICATE	QA Contact:	OSP DFG:Compute <osp-dfg-compute>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	alifshit, dasmith, eglynn, jhakimra, kchamart, sbauza, sgordon, vromanso
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-11-18 18:01: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:	Xena
Embargoed:

Description Stephen Finucane 2021-04-30 16:42:01 UTC

Description of problem:

During the Train release, we added support for live migration of pinned instances [1]. However, pinned instances - that is, instances with the 'hw:cpu_policy=dedicated' flavor extra spec or equivalent image metadata property - are not the only instances that are "pinned". If the '[compute] cpu_shared_set' config option or deprecated '[DEFAULT] vcpu_pin_set' config options are set on a host, then standard unpinned, non-NUMA instances will be "pinned" to the range of cores specified in this list. We do not currently account for this fact when live migrating an instance, meaning an instance moving from a host with neither of these options set to one with it set will not be updated. This RFE tracks the resolution of this oversight.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1222414

Comment 1 Artom Lifshitz 2021-11-18 18:01:21 UTC


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