3f0605c289
This adds the os-services API change which will call the compute service when the service's disabled value changes to sync the COMPUTE_STATUS_DISABLED trait on the compute node resource providers managed by the updated compute service. If the compute service is down or not yet upgraded to the service version from change Ia95de2f23f12b002b2189c9294ec190569a628ab then the API will not call the service. In this case the change from I3005b46221ac3c0e559e1072131a7e4846c9867c will sync the trait when the compute service is restarted. Since the compute service could be running the ironic driver and managing hundreds or over 1000 compute nodes, the set_host_enabled RPC call now uses the long_rpc_timeout configuration option. A functional test is added which covers the 2.53+ PUT /os-services/{service_id} API and pre-2.53 os-services APIs for enabling/disabling and forcing down a service. The functional test also covers the sync-on-restart behavior from change I3005b46221ac3c0e559e1072131a7e4846c9867c. The scheduler pre-filter added in change I317cabbe49a337848325f96df79d478fd65811d9 is also tested as part of the functional test. Closes-Bug: #1805984 Implements blueprint pre-filter-disabled-computes Change-Id: If32bca070185937ef83f689b7163d965a89ec10a |
||
---|---|---|
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: