5d5e7be8cb
Since change I81301eeecc7669a169deeb1e2c5d298a595aab94 in devstack, nova-cpu.conf is a copy of nova.conf minus database access. Grenade jobs also run nova-compute with nova-cpu.conf anyway so we can just drop the conditional which was otherwise messing up the config file that the ceph script would write rbd configuration which is why live block migration tests with ceph were failing. NOTE(mriedem): This is not a pure backport since this change in queens just disables running the job with ceph because of a mess of changes to devstack queens related to change https://review.openstack.org/625131/ and change https://review.openstack.org/632100/. As a result, the pike node runs with nova.conf (because of grenade singleconductor mode makes it so) but the queens node runs with nova-cpu.conf and then the _ceph_configure_nova function does not configure the nodes for rbd auth properly which makes rbd-backed live migration in the job fail. Rather than try to sort that all out with a one-off change in queens (which is pretty old at this point anyway), this change just skips the ceph portion of the job. An alternative is just not running the job in queens, but we can easily still get block migrate live migration coverage so we might as well keep that running. Change-Id: I902e459093af9b82f9033d58cffcb2a628f5ec39 Closes-Bug: #1813216 (cherry picked from commit |
||
|---|---|---|
| api-guide/source | ||
| api-ref/source | ||
| contrib | ||
| devstack | ||
| doc | ||
| etc/nova | ||
| gate | ||
| nova | ||
| placement-api-ref/source | ||
| playbooks/legacy | ||
| releasenotes | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MAINTAINERS | ||
| README.rst | ||
| babel.cfg | ||
| bindep.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tests-py3.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: