The LibvirtNetVolumeDriver is handling both rbd and sheepdog (iscsi) connections. The auth config logic is mingling both backends which is really confusing. For example, the iscsi protocol only defines auth_method, auth_username and auth_password. It does not set an auth_enabled value in the connection_info['data'] dict. This change simplifies the logic involved for setting the auth config by decoupling the rbd/iscsi handlers. A follow-up change will build on this to fix the rbd auth config to prefer the cinder volume connection_info auth data over the local config for nova in the case that different cinder backends are used for ephemeral and block storage. Change-Id: I8a55d87f75ecad757ce81b1f5f77c3a551154a17 Partial-Bug: #1635008
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:
http://developer.openstack.org/api-guide/compute/ http://developer.openstack.org/api-ref/compute/
For more information on OpenStack APIs, SDKs and CLIs, please see:
http://www.openstack.org/appdev/ http://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:
http://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: