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-nova | Assignee: | Nikola Dipanov <ndipanov> |
| Status: | CLOSED ERRATA | QA Contact: | Omri Hochman <ohochman> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | unspecified | CC: | adahms, ddomingo, eglynn, markmc, ndipanov, ohochman, sgordon, slong, vpopovic, yeylon |
| Target Milestone: | Upstream M3 | Keywords: | 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
Assigning to Nikola as he is the current assignee upstream. Looks like changes are only in the API; no doc impact. 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 |