5b64a19361
Prior to Queens any attempt to swap between encrypted volumes would result in unencrypted data being written to the new volume. This unencrypted data would then be overwritten the next time the volume was attached to an instance as Nova no longer identified the volume as encrypted, resulting in the volume being reformatted. This stable only change uses limited parts of the following changes to block all swap_volume attempts with encrypted volumes prior to Queens where this was resolved by Ica323b87fa85a454fca9d46ada3677f18 and also blocked when using QEMU to decrypt LUKS volumes by Ibfa64f18bbd2fb70db7791330ed1a64fe61c1. Ica323b87fa85a454fca9d46ada3677f18fe50022 The request context is provided to swap_volume in order to look up the encryption metadata of a volume. Ibfa64f18bbd2fb70db7791330ed1a64fe61c1355 Attempts to swap from an encrypted volume are blocked with a NotImplementedError exception raised. I258127fdcd011ccec721d5ff62eb7f128f130336 Attempts to swap from an unencrypted volume to an encrypted volume are also blocked with a NotImplementedError exception raised. Ie02d298cd92d5b5ebcbbcd2b0e8be01f197bfafb The serial of a volume is used as the id if connection_info for the volume doesn't contain the volume_id key. Required to avoid bug #1746609. Closes-bug: #1739593 Change-Id: If12e7860baad2899380f06144a0270784a5466b8 |
||
|---|---|---|
| api-guide/source | ||
| api-ref/source | ||
| contrib | ||
| devstack | ||
| doc | ||
| etc/nova | ||
| gate | ||
| nova | ||
| placement-api-ref/source | ||
| plugins/xenserver | ||
| releasenotes | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .testr.conf | ||
| .zuul.yaml | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MAINTAINERS | ||
| README.rst | ||
| babel.cfg | ||
| bindep.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tests-functional-py3.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: