The sample of block_device_mapping_v2 contains uuid as a parameter but there is not any explanation of the parameter. This patch adds it to api-ref. The following is for explaining the parameter from the code. As the following code, source_type is "image" and api_dict["image_id"] can be glance image-id on the sample case. https://github.com/openstack/nova/blob/master/nova/block_device.py#L197 api_dict[source_type + '_id'] = device_uuid The "image_id" is used for getting image metadata from Glance: https://github.com/openstack/nova/blob/master/nova/compute/api.py#L1072 image_id = bdm['image_id'] image_meta = self.image_api.get(context, image_id) Change-Id: I83badab07446c2b1e55cc3b29a3ba9476efc179d
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: