38f2ce549c
The nova-status upgrade check code is intentionally written to not use versioned objects and just work with the data model directly. However, CellMapping database_connection template support was added in Rocky and the template URL is only formatted when using the object on read from the database, which means if you are using a template for the database_connection nova-status will break since the get_engine() code is getting a template string rather than a properly formatted URL. This change fixes the bug by using the CellMapping object code to pull the mappings from the database which will format the database connection URL. Note that we cannot simply update the sqlalchemy RowProxy objects we get normally since those are read-only, and because of how the mappings are used as objects with attribute access rather than as a dict we cannot just convert the RowProxy to a dict - we would have to put it in some kind of object for attribute access and if we are going to do that we might as well just use the CellMapping objects we have so that's what we do in this change. Change-Id: I5ce175517f6feb6e82ba507078a565b71427a4b0 Closes-Bug: #1818047 |
||
|---|---|---|
| api-guide/source | ||
| api-ref/source | ||
| devstack | ||
| doc | ||
| etc/nova | ||
| gate | ||
| nova | ||
| playbooks/legacy | ||
| releasenotes | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MAINTAINERS | ||
| README.rst | ||
| babel.cfg | ||
| bindep.txt | ||
| lower-constraints.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
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: