Bug 1955690 - [RFE] Support live migration from an host without pinset information to one without
Summary: [RFE] Support live migration from an host without pinset information to one w...
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: nova-maint
QA Contact: nova-maint
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-04-30 16:42 UTC by Stephen Finucane
Modified: 2021-05-01 05:03 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version: Xena

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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
Note You need to log in before you can comment on or make changes to this bug.