8f317f442c
With the introduction of the libvirt-default-machine-type blueprint operators are now able to change the default machine type used by an existing environment more easily. This should hopefully allow more deployments to switch to the modern q35 machine type, away from the legacy pc machine type that is currently the default. With this in mind this change aims to start testing the q35 machine type as part of the nova-next job before we eventually change the default in the future. The following changes are made to the job to allow it to pass with q35: - [libvirt]num_pcie_ports is increased to 24 This is required as more devices are now connected by default over PCIe. - [compute-feature-enabled]ide_bus is disabled The q35 machine type does not support an IDE bus so any tests using this bus are now skipped. Depends-On: https://review.opendev.org/c/openstack/devstack/+/779179 Depends-On: https://review.opendev.org/c/openstack/tempest/+/775630 blueprint: libvirt-default-machine-type Change-Id: Iad1adbc23b31dd54a96299e7a8a4b622c15eed8d
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: