Volume support for multi hypervisors

Registered by Mitsuhiro Tanino on 2015-12-01

In multi hypervisor OpenStack environment using such as KVM, VMware, Hyper-V etc, we need to provide Cinder storage
backends corresponding to these hypervisors for booting an instance from a volume. For example, VMware needs VMDK Cinder backend, Hyper-V needs Windows Cinder backend and also KVM needs supported backends such as LVM, ceph etc. KVM can't boot from VMDK backend.

However, there is no way to specify storage backend when user boot an instance from a volume. As a result, the boot volume
might be created on unrelated backend then the volume boot will fail.

To boot an instance from specific combination between hypervisor and storage backend properly, Cinder needs to know which hypervisor will handle the volume and then Cinder should schedule volume creation to proper storage backend based on the hypervisor type.

Blueprint information

Status:
Complete
Approver:
Sean McGinnis
Priority:
Undefined
Drafter:
Mitsuhiro Tanino
Direction:
Approved
Assignee:
Mitsuhiro Tanino
Definition:
Obsolete
Series goal:
Accepted for mitaka
Implementation:
Unknown
Milestone target:
None
Completed by
Mitsuhiro Tanino on 2016-02-10

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/volume-support-for-multi-hypervisors,n,z

Addressed by: https://review.openstack.org/252065
    Volume support for multi hypervisors

Solution for this problem was provided via 'Support cinder_img_volume_type in image metadata'
https://review.openstack.org/#/c/258649/ (BP less, SPEC less.)

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.