dbf3e276ba
As seen before in bug #1913451 the nova-lvm job creates large RAW snapshots during each run due to the nature of using LVM storage for the ephemeral instance disks. Id425aa546f1a5973bae8be9c017782d18f0b4a47 recently landed capping the per teneant image size total to 1000 MiB that is far too low for this job given the RAW snapshots it's creating. This in turn resulted in 504 failures when n-cpu attempted to upload snapshots to g-api. This change simply increases the per tenant limit to 10 GiB that should be more than enough for all of the tests covered by the nova-lvm job. Closes-Bug: #1938765 Change-Id: I824655387a10ac9b813c1b7b2399e25ed95f7fc3
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: