90e0e874bd
This adds a failing test, which we fix in change I76448196. An earlier version of this change was previously merged as change I5619728d. This was later reverted, as it was failing in the gate. However, on inspection these failures seem to have been simply timeouts due to load. Changes from previous version: - Increase the timeouts which were previously triggering, and serialise server creation to reduce the chance of this recurring. - Add an LVM test, which highlights the requirement to flag the creation of ephemeral and swap disks. - Add an Qcow2 test, essentially the same as the Flat test but ensures coverage of the most common backends. - Each test now uses a separate instances_path allowing for cleanup without racing against other active tests. - Some nits addressed. For the time being this test does not make use of the recently improved nova.tests.functional.libvirt.base.ServersTestBase class to ease backports. Future changes should be made to use this class removing some of the common setUp logic from _LibvirtEvacuateTest. Co-Authored-By: Lee Yarwood <lyarwood@redhat.com> Related-Bug: #1550919 Change-Id: I1062b3e74382734edbb2142a09ff0073c66af8db |
||
|---|---|---|
| api-guide/source | ||
| api-ref/source | ||
| devstack | ||
| doc | ||
| etc/nova | ||
| gate | ||
| nova | ||
| playbooks | ||
| releasenotes | ||
| roles | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .pre-commit-config.yaml | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MAINTAINERS | ||
| README.rst | ||
| bindep.txt | ||
| lower-constraints.txt | ||
| mypy-files.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
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: