We now have the machinery in place to parse QEMU's firmware metadata files, which means we no longer need to store a hardcoded list of possible firmware locations nor build upon this to include additional information like "does this support secure boot". Start using this and cut out the legacy stuff. Eventually all of this will be changed yet again in favour of libvirt's firmware auto-selection functionality, but that needs a little more work before it's suitable for us [1]. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1906500 Blueprint: allow-secure-boot-for-qemu-kvm-guests Change-Id: Ie99e43cb0408eae4034d410b9dd204cd39984fd1 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
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: