Mate Lakat
1dfdfcef3c
Related to blueprint xenapi-volume-drivers The connection_info parameter, that is coming from volume contains only two keys, 'driver_volume_type', and 'data'. See: https://github.com/openstack/nova/blob/master/nova/volume/manager.py#L375 parse_volume_info was checking the connection_info for 'auth_method', and authentication parameters. These informations live inside connection_data. This patch is fixing this, and covering with a test. Also rename the generic data variable to connection_data, to make it easier to read the code. parse_volume_info thus no longer depends on the whole connection_info, only on the connection_data. Also clean-up some copy-paste test setup code. Change-Id: I5289120d46176c8528c3317a650269c4f384f930
OpenStack Nova README ===================== OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of virtualization technologies, including KVM, Xen, LXC, VMWare, and more. In addition to its native API, it includes compatibility with the commonly encountered Amazon EC2 and S3 APIs. 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. Nova primarily consists of a set of Python daemons, though it requires and integrates with a number of native system components for databases, messaging and virtualization capabilities. To keep updated with new developments in the OpenStack project follow `@openstack <http://twitter.com/openstack>`_ on Twitter. To learn how to deploy OpenStack Nova, consult the documentation available online at: http://docs.openstack.org 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: http://bugs.launchpad.net/nova Developers wishing to work on the OpenStack Nova project should always base their work on the latest Nova code, available from the master GIT repository at: http://github.com/openstack/nova Developers should also join the discussion on the mailing list, at: https://lists.launchpad.net/openstack/ 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: http://nova.openstack.org/ Changes to OpenStack Nova should be submitted for review via the Gerrit tool, following the workflow documented at: http://wiki.openstack.org/GerritWorkflow -- End of broadcast