Eric Fried
a79d3d546b
We have at least one use case [1] for identifying resource providers which represent compute nodes. There are a few ways we could do that hackishly (e.g. [2], [3]) but the clean way is to have nova-compute mark the provider with a trait, since nova-compute knows which one it is anyway. This commit uses the COMPUTE_NODE trait for this purpose, and bumps the os-traits requirement to 1.1.0 where it is introduced. Arguably this is a no-op until something starts using it, but a release note is added anyway warning that all compute nodes should be upgraded to ussuri (or the trait added manually) for the trait to be useful. [1] https://review.opendev.org/#/c/670112/7/nova/cmd/manage.py@2921 [2] Assume a provider with a certain resource class, like MEMORY_MB, is always a compute node. This is not necessarily future-proof (maybe all MEMORY_MB will someday reside on NUMA node providers; similar for other resource classes) and isn't necessarily true in all cases today anyway (ironic nodes don't have MEMORY_MB inventory) and there's also currently no easy way to query for that (GET /resource_providers?MEMORY_MB:1 won't return "full" providers, and you can't ask for :0). [3] Assume a root provider without the MISC_SHARES_VIA_AGGREGATE trait is a compute node. This assumes you're only using placement for nova-ish things. Change-Id: I4cb9cbe1e02c3f6c6148f73a38d10e8db7e61b1a
========================
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/