61e6f5b1e1
This patch does 3 things really. Firstly it adds disk_bus and device_type parameters to reserve_block_device_name compute rpc method, thus laying the groundwork for the ability to specify those when calling attach. Further to that - it makes the attach volume code use new-world objects. These two changes were done in a single commit to avoid unnecessary rpc version bumps. In addition to this, attach_volume method of the compute manager has been refactored to use DriverBlockDevice objects and their method - thus getting rid of some code duplication. Finally we move block_device module utility method instance_block_mapping to use the v2 block device data format and thus also objects, and do some cleanup around how it was used elsewhere in the code. Part of the blueprint: icehouse-objects Part of the blueprint: clean-up-legacy-block-device-mapping Part of the blueprint: use-new-bdm-format-in-attach Change-Id: I3eb341efcd6397f1bfbb98a546e10e248a45460e
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 on Twitter.
To learn how to deploy OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki:
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 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:
Developers should also join the discussion on the mailing list, at:
http://lists.openstack.org/cgi-bin/mailman/listinfo/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:
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.
-- End of broadcast