168d34c8d1
This adds a new mandatory placement request pre-filter which is used to exclude compute node resource providers with the COMPUTE_STATUS_DISABLED trait. The trait is managed by the nova-compute service when the service's disabled status changes. Change I3005b46221ac3c0e559e1072131a7e4846c9867c makes the compute service sync the trait during the update_available_resource flow (either on start of the compute service or during the periodic task run). Change Ifabbb543aab62b917394eefe48126231df7cd503 makes the libvirt driver's _set_host_enabled callback reflect the trait when the hypervisor goes up or down out of band. Change If32bca070185937ef83f689b7163d965a89ec10a will add the final piece which is the os-services API calling the compute service to add/remove the trait when a compute service is disabled or enabled. Since this series technically functions without the API change, the docs and release note are added here. Part of blueprint pre-filter-disabled-computes Change-Id: I317cabbe49a337848325f96df79d478fd65811d9 |
||
---|---|---|
api-guide/source | ||
api-ref/source | ||
devstack | ||
doc | ||
etc/nova | ||
gate | ||
nova | ||
playbooks/legacy | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.stestr.conf | ||
.zuul.yaml | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MAINTAINERS | ||
README.rst | ||
babel.cfg | ||
bindep.txt | ||
lower-constraints.txt | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
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: