e73f828057
We can't easily add a blocker db sync migration to make sure the migrate_instances_add_request_spec online data migration has been run since we have to iterate both cells (for instances) and the API DB (for request specs) and that's not something we should do during a db sync call. But we want to eventually drop the online data migration and the accompanying compat code found in the api and conductor services. This adds a nova-status upgrade check for missing request specs and fails if any existing non-deleted instances are found which don't have a matching request spec. Related to blueprint request-spec-use-by-compute Change-Id: I1fb63765f0b0e8f35d6a66dccf9d12cc20e9c661
Team and repository tags
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, XenServer, 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: