8cb6f07444
We were running the voting neutron-grenade-multinode job in the check queue on nova changes but were not running it in the gate queue. We run the nova-grenade-multinode job in both check and gate queues. The major differences between those jobs are that the neutron job runs the tempest smoke tests during the grenade run on the old and new side of the grenade environment and the nova job would not run smoke tests but ran a select few live migration and resize/cold migration tests via the post-test hook script, and would run those with an lvm/local storage/block migration and ceph/shared storage setup. This change makes the nova-grenade-multinode job run smoke tests like the neutron-grenade-multinode job was so we can drop the neutron-grenade-multinode job from running on nova changes in the check queue and save a few nodes. Note that neutron-grenade-multinode ran all smoke tests but this change makes nova-grenade-multinode run a subset of smoke tests for only the ones that involve compute. This is in order to keep the execution time of the job down by not testing non-compute API things that nova changes don't care about, e.g. keystone, swift, cinder, etc smoke tests. [1] https://zuul.opendev.org/t/openstack/build/377affdf97b04022a321087352e1cc4c/log/logs/grenade.sh.txt.gz#41965 Change-Id: Icac785eec824da5146efe0ea8ecd01383f18398e
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: