95fbbce8b2
This change simply bumps the version of os-brick required by Nova to version 4.2.0. This is itself required by I9ad90817648ca12f80a6b53f6ba728df15cbafab that introduces support for rbd volumes within the HyperV driver. After much back and fourth it was decided to bump the required version of os-brick ahead of that change to allow the following requirements.txt and lower-constraints.txt changes caused by direct and in-direct dependency changes to be documented clearly: os-brick 4.2.0 depends on oslo.log>=4.4.0 \_ oslo-log 4.4.0 depends on python-dateutil>=2.7.0 os-brick 4.2.0 depends on oslo.serialization>=4.0.1 os-brick 4.2.0 depends on pbr>=5.5.0 os-brick 4.2.0 depends on oslo.privsep>=2.4.0 \_ oslo.privsep 2.4.0 depends on msgpack>=0.6.0 os-brick 4.2.0 depends on oslo.service>=2.4.0 os-brick 4.2.0 depends on tenacity>=6.2.0 os-brick 4.2.0 depends on oslo.context>=3.1.1 os-brick 4.2.0 depends on oslo.concurrency>=4.3.0 os-brick 4.2.0 depends on oslo.i18n>=5.0.1 os-brick 4.2.0 depends on six>=1.15.0 os-brick 4.2.0 depends on os-win>=5.1.0 The above changes have been tested with pip 21.0.1 to ensure the new resolver is happy and that nothing has been missed. Change-Id: Ic83f3c7c955d0df89d75f700ee4fe2bd7f715794 Implements: blueprint hyperv-rbd |
||
---|---|---|
api-guide/source | ||
api-ref/source | ||
devstack | ||
doc | ||
etc/nova | ||
gate | ||
nova | ||
playbooks | ||
releasenotes | ||
roles | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.pre-commit-config.yaml | ||
.stestr.conf | ||
.zuul.yaml | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
lower-constraints.txt | ||
MAINTAINERS | ||
mypy-files.txt | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
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, 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: