Matt Riedemann
6f8c2f0df5
The tempest-slow-py3 job is, well, very slow. It takes over 2.5 hours sometimes to complete. There are a few reasons beyond it just running slow tests but it runs all slow tests serially and for nova it's testing things we don't care about like network scenario tests like test_slaac_from_os. The one benefit we get from running tempest-slow-py3 is that it's multinode and there are certain slow test scenarios for multinode that are important for test coverage. This change drops the tempest-slow-py3 job from our job list and changes nova-next to be multinode. The nova-next job runs a select set of tempest compute API and scenario tests only and runs them concurrently, which in the gate is 4 workers at a time. The nova-next job will take a bit longer since we have to setup the subnode now but overall it should still be faster than the tempest-slow-py3 job and we'll save on one more node required from nodepool to run jobs against nova changes. The USE_PYTHON3 variable can be dropped from the nova-next job definition now that it extends tempest-multinode-full-py3. Depends-On: https://review.opendev.org/690469/ Change-Id: I1b7d71e833bf0743f22d7fa0241c9d1bbcd0faac
========================
Team and repository tags
========================
.. image:: https://governance.openstack.org/tc/badges/nova.svg
:target: https://governance.openstack.org/tc/reference/tags/index.html
.. Change things from this point on
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:
- `Compute API Guide <https://docs.openstack.org/api-guide/compute/>`__
- `Compute API Reference <https://docs.openstack.org/api-ref/compute/>`__
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
- `OpenStack for App Developers <https://www.openstack.org/appdev/>`__
- `Development resources for OpenStack clouds
<https://developer.openstack.org/>`__
Operators
---------
To learn how to deploy and configure OpenStack Nova, consult the documentation
available online at:
- `OpenStack Nova <https://docs.openstack.org/nova/>`__
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:
- `Bug Tracker <https://bugs.launchpad.net/nova>`__
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:
- `Official Nova Documentation <https://docs.openstack.org/nova/>`__
- `Official Client Documentation
<https://docs.openstack.org/python-novaclient/>`__
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:
- `Nova Specs <http://specs.openstack.org/openstack/nova-specs/>`__
.. _Summit: https://www.openstack.org/summit/
.. _Project Team Gathering: https://www.openstack.org/ptg/