1957f4d5a2
The Cinder 3.48 API provides a shared_targets and service_uuid field in the volume resource which tells the caller whether or not it should lock operations on that volume. This change adds that logic to the DriverVolumeBlockDevice attach and detach flows by first trying to get the volume at the 3.48 microversion and if that's not available, it simply falls back to get the volume the same as before. If 3.48 is available and the volume storage backend uses shared targets, we synchronize the attach/detach operations using the volume service_uuid, which is based on the storage backend and is also configurable by the deployer on the Cinder side. This is a nice to have protection for "normal" volumes but is really needed for multiattach volumes to be detached safely. See Cinder blueprint add-shared-targets-flag-to-volume for details. Part of blueprint multi-attach-volume Depends-On: I3c07cd8458d55535a71626ffaa8ca50deb3ca3dd Change-Id: I5e96602184242fb9017c0434b445a3875f3b149a |
||
|---|---|---|
| api-guide/source | ||
| api-ref/source | ||
| contrib | ||
| devstack | ||
| doc | ||
| etc/nova | ||
| gate | ||
| nova | ||
| placement-api-ref/source | ||
| releasenotes | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .stestr.conf | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MAINTAINERS | ||
| README.rst | ||
| babel.cfg | ||
| bindep.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tests-py3.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: