2d68fbe565
This plumbs in the new-style volume attachment support to the virt driver block device code which does the actual work of attaching the volume via the driver and completing the attachment with cinder (the thing that makes the volume status "in-use"). At this point, none of the new flow is exercised outside of tests because we are not yet setting the attachment_id when attaching volumes, that comes in a later change to the API. It's worth noting that when nova creates a volume during boot from volume for a source_type=blank/image/snapshot BDM, we won't have an attachment_id for that volume so we'll attach using the old flow. For now this is OK, but might be something we need to revisit in the future when we eventually want to remove the old flow. The structure here is to separate the old/new attach flows into separate methods, despite quite a bit of copy/paste code in both places. A single method using conditionals in different places is arguably uglier (as seen in the test code) and we could likely consolidate some of the common code into helper methods later. Note that test_refresh_connection_info_with_attachment_id is removed since it's now redundant with test_refresh_connection. Co-Authored-By: Matt Riedemann <mriedem.os@gmail.com> Part of blueprint cinder-new-attach-apis Change-Id: Ib1b6b223c9d04579828d47607006ecd98b472e5a
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: