ae53c22457
This adds the support for new style volume attachments to the swap volume operation. If the existing volume attachment (old_volume) was created using the new flow, it will have attachment_id set. Based on that the API will create a new volume attachment for the volume being swapped to and then pass that attachment to the compute over RPC. Note that we do not yet create new-style volume attachments so this is all no-op code for now. And when we do start creating new-style volume attachments, that will only be allowed when Cinder is new enough (3.27 microversion) and all compute services are upgraded, so we don't perform any nova-compute service version checks here. Once on the compute, we key off the new_attachment_id being passed from the API to tell if we should use the old or new style calls to Cinder. For example, initialize_connection and terminate_connection are replaced with attachment_update and attachment_delete. Co-Authored-By: Matt Riedemann <mriedem.os@gmail.com> Co-Authored-By: John Griffith <john.griffith8@gmail.com> Depends-On: I23391300468cc5e2f45a12d5ad8617ab48c21e6a Partially Implements: blueprint cinder-new-attach-apis Change-Id: I4b8bd01f1ffe2640fe7313213bf853d2e1bef9dd |
||
|---|---|---|
| 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 | ||
| babel.cfg | ||
| bindep.txt | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MAINTAINERS | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tests-functional-py3.txt | ||
| tests-py3.txt | ||
| tox.ini | ||
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 and OpenStack Ironic.
OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.
API
To learn how to use Nova's API, consult the documentation available online at:
https://developer.openstack.org/api-guide/compute/ https://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs, please see:
https://www.openstack.org/appdev/ https://developer.openstack.org/
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, please read:
https://docs.openstack.org/developer/nova/feature_classification.html
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: