Go to file
Matt Riedemann d9587afe16 Remove unnecessary connector stash in attachment_update
We don't need to stash the connector in the volume attachment
connection_info for new style volume attachments becaues it's
not used. This was copied from the initialize_connection method
which used it during detach of a volume, but for new style
volume attachments, we simply delete the volume attachment and
we don't need the original host connector.

Similarly, attachment_create wasn't stashing the connector either
if we created an attachment with a connector.

The two places that would use the stashed connector for an old
style attachment are:

1. DriverVolumeBlockDevice.detach
2. _get_stashed_volume_connector in the compute.API

But as noted, neither of those flows need the connector for a
new style attachment.

Change-Id: Ie028c26ea0436bfa0b613c9cffc6b6352792fc0a
2017-12-13 20:15:50 -05:00
2017-08-07 16:00:10 +01:00
2017-01-04 11:05:16 +00:00
2014-05-07 12:14:26 -07:00
2012-02-08 19:30:39 -08:00
2017-11-21 21:01:09 +01:00
2017-09-07 15:42:31 +02:00
2017-11-28 15:23:48 -05:00
2017-03-02 11:50:48 +00:00
2017-03-02 14:30:16 +08:00

Team and repository tags

image

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:

Description
OpenStack Compute (Nova)
Readme 1.7 GiB
Languages
Python 97.5%
Smarty 2.3%
Shell 0.2%