yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #21419
[Bug 1370390] [NEW] Resize instace will not change the NUMA topology of a running instance to the one from the new flavor
Public bug reported:
When we resize (change the flavor) of an instance that has a NUMA
topology defined, the NUMA info from the new flavor will not be
considered during scheduling. The instance will get re-scheduled based
on the old NUMA information, but the claiming on the host will use the
new flavor data. Once the instane sucessfully lands on a host, we will
still use the old data when provisioning it on the new host.
We should be considering only the new flavor information in resizes.
** Affects: nova
Importance: High
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1370390
Title:
Resize instace will not change the NUMA topology of a running instance
to the one from the new flavor
Status in OpenStack Compute (Nova):
New
Bug description:
When we resize (change the flavor) of an instance that has a NUMA
topology defined, the NUMA info from the new flavor will not be
considered during scheduling. The instance will get re-scheduled based
on the old NUMA information, but the claiming on the host will use the
new flavor data. Once the instane sucessfully lands on a host, we will
still use the old data when provisioning it on the new host.
We should be considering only the new flavor information in resizes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1370390/+subscriptions
Follow ups
References