Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1041053

Summary: [RFE][nova]: Take advantage of the new BDM format when attaching volumes
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: openstack-novaAssignee: Nikola Dipanov <ndipanov>
Status: CLOSED ERRATA QA Contact: Omri Hochman <ohochman>
Severity: low Docs Contact:
Priority: medium    
Version: unspecifiedCC: adahms, ddomingo, eglynn, markmc, ndipanov, ohochman, sgordon, slong, vpopovic, yeylon
Target Milestone: Upstream M3Keywords: FutureFeature, Triaged
Target Release: 5.0 (RHEL 7)Flags: ndipanov: needinfo+
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/nova/+spec/use-new-bdm-format-in-attach
Whiteboard: upstream_milestone_icehouse-3 upstream_status_implemented upstream_definition_approved
Fixed In Version: openstack-nova-2014.1-3.el7ost Doc Type: Enhancement
Doc Text:
With this update, the API call for attaching volumes to instances in Compute (servers/[INSTANCE_UUID]/os-volume_attachments) now accepts two additional parameters in the body: disk_bus and device_type. If these parameters are specified, the libvirt driver attempts to honor them when attaching the volume. The following values are accepted: * disk_bus: 'scsi' and 'virtio' * device_type: 'disk', 'cdrom', 'floppy', and 'lun'
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-08 15:27:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1085036    
Bug Blocks:    

Description RHOS Integration 2013-12-12 13:30:54 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/use-new-bdm-format-in-attach.

Description:

As part of the havana blueprint improve-block-device-handling we added some data that can be associated with the volume. We can now use this data when attaching volumes (not only when booting). Several things will need to be done.

* Add the needed options to the volume-attach API calls in the v3 API
* Make all the attach code paths use the new-format of block devices and not rely on the legacy data format
* Implement the new use of the new format in the libvirt driver.

Specification URL (additional information):

None

Comment 2 Stephen Gordon 2014-01-06 21:19:46 UTC
Assigning to Nikola as he is the current assignee upstream.

Comment 4 Summer Long 2014-03-28 09:56:02 UTC
Looks like changes are only in the API; no doc impact.

Comment 14 errata-xmlrpc 2014-07-08 15:27:05 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-0853.html