Back to bug 1041053

Who When What Removed Added
RHOS Integration 2013-12-12 13:31:00 UTC Keywords FutureFeature
Whiteboard upstream_milestone_icehouse-2 upstream_status_not-started
Red Hat Bugzilla 2013-12-12 13:31:00 UTC Doc Type Bug Fix Enhancement
Stephen Gordon 2014-01-06 21:19:46 UTC Priority unspecified medium
Status NEW ASSIGNED
Keywords Triaged
Component RFEs openstack-nova
CC ndipanov, rbryant, sgordon
Assignee rhos-maint ndipanov
QA Contact ajeain
Severity low medium
RHOS Integration 2014-01-10 05:01:16 UTC Whiteboard upstream_milestone_icehouse-2 upstream_status_not-started upstream_milestone_icehouse-2 upstream_status_started
John Skeoch 2014-01-13 01:09:31 UTC CC hateya
RHOS Integration 2014-01-14 05:03:56 UTC Target Release 5.0 ---
Whiteboard upstream_milestone_icehouse-2 upstream_status_started upstream_milestone_icehouse-2 upstream_status_needs-code-review
RHEL Program Management 2014-01-14 05:30:41 UTC Target Release --- 5.0
RHOS Integration 2014-01-22 05:03:11 UTC Target Milestone Upstream M2 Upstream M3
Whiteboard upstream_milestone_icehouse-2 upstream_status_needs-code-review upstream_milestone_icehouse-3 upstream_status_needs-code-review
RHOS Integration 2014-02-19 21:40:43 UTC Whiteboard upstream_milestone_icehouse-3 upstream_status_needs-code-review upstream_milestone_icehouse-3 upstream_status_needs-code-review upstream_definition_approved
RHOS Integration 2014-02-20 15:52:24 UTC Target Release 5.0 ---
RHEL Program Management 2014-02-20 15:58:54 UTC Target Release --- 5.0
RHOS Integration 2014-02-20 17:50:00 UTC Status ASSIGNED POST
Target Release 5.0 ---
RHEL Program Management 2014-02-20 18:30:55 UTC Target Release --- 5.0
RHOS Integration 2014-02-20 21:41:37 UTC Target Release 5.0 ---
RHEL Program Management 2014-02-20 22:20:01 UTC Target Release --- 5.0
RHOS Integration 2014-02-21 17:08:18 UTC Severity medium low
RHOS Integration 2014-03-04 18:14:18 UTC Whiteboard upstream_milestone_icehouse-3 upstream_status_needs-code-review upstream_definition_approved upstream_milestone_icehouse-3 upstream_status_implemented upstream_definition_approved
Summer Long 2014-03-28 09:56:02 UTC CC slong
Omri Hochman 2014-04-03 11:37:24 UTC CC ohochman
Flags needinfo?(ndipanov)
Nikola Dipanov 2014-04-04 12:44:04 UTC Doc Text The API call for attaching volumes to instances in Nova (servers/<INSTANCE_UUID>/os-volume_attachments will now accept two more parameters in the body: disk_bus and device_type. If supplied - libvirt driver will attempt to honor them when attaching the volume.

disk_bus expects values: 'scsi', 'virtio'

device_type expects the following values: 'disk', 'cdrom', 'floppy', 'lun'
Flags needinfo?(ndipanov)
Omri Hochman 2014-04-06 11:54:36 UTC QA Contact ajeain ohochman
Flags needinfo?(ndipanov)
Nikola Dipanov 2014-04-07 15:14:42 UTC Depends On 1085036
Nikola Dipanov 2014-04-07 15:22:23 UTC Flags needinfo?(ndipanov) needinfo+
Nikola Dipanov 2014-04-08 07:43:15 UTC Status POST ASSIGNED
Nikola Dipanov 2014-04-08 07:43:42 UTC Status ASSIGNED POST
Vladan Popovic 2014-05-30 15:07:33 UTC Status POST MODIFIED
CC vpopovic
Fixed In Version openstack-nova-2014.1-3.el7ost
Stephen Gordon 2014-06-09 14:57:06 UTC Status MODIFIED ON_QA
Lon Hohberger 2014-06-25 16:20:43 UTC Status ON_QA MODIFIED
errata-xmlrpc 2014-06-25 16:33:59 UTC Status MODIFIED ON_QA
Summer Long 2014-06-29 23:24:15 UTC Doc Text The API call for attaching volumes to instances in Nova (servers/<INSTANCE_UUID>/os-volume_attachments will now accept two more parameters in the body: disk_bus and device_type. If supplied - libvirt driver will attempt to honor them when attaching the volume.

disk_bus expects values: 'scsi', 'virtio'

device_type expects the following values: 'disk', 'cdrom', 'floppy', 'lun'
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'
Summer Long 2014-06-30 01:05:03 UTC 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'
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'
errata-xmlrpc 2014-07-07 12:03:10 UTC Status ON_QA RELEASE_PENDING
errata-xmlrpc 2014-07-08 15:27:05 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2014-07-08 11:27:05 UTC
Don Domingo 2014-07-22 12:51:08 UTC CC ddomingo
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'
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'
Andrew Dahms 2015-04-27 04:52:27 UTC CC adahms
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'
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'
John Skeoch 2016-04-22 05:02:42 UTC CC eglynn
Russell Bryant 2019-09-09 14:44:26 UTC CC rbryant

Back to bug 1041053