
When the InstanceNUMATopology OVO has changed in I901fbd7df00e45196395ff4c69e7b8aa3359edf6 to separately track pcpus from vcpus a data migration was added. This data migration is triggered when the InstanceNUMATopology object is loaded from the instance_extra table. However that patch is missed the fact that the InstanceNUMATopology object can be loaded from the request_spec table as well. So InstanceNUMATopology object in RequestSpec are not migrated. This could lead to errors in the scheduler when such RequestSpec object is used for scheduling (e.g. during a migration of a pre Victoria instance with cpu pinning) This patch adds the missing data migration. Change-Id: I812d720555bdf008c83cae3d81541a37bd99e594 Closes-Bug: #1952941
OpenStack Nova
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, OpenStack Ironic and PowerVM.
Use the following resources to learn more.
API
To learn how to use Nova's API, consult the documentation available online at:
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst.
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests.
Further developer focused documentation is available at:
Other Information
During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for nova can be found at: