Libvirt driver - enable images as disks on the hypervisor local storage

Registered by Nikola ─Éipanov on 2013-08-20

As part of the havana blueprint improve-block-device-handling we added the possibility to have glance images specified as block devices, and wa also added the field to specify the target of the block device.

The idea behind this is that we would be able to specify weather the image would be created on the hypervisor (dest=local) or will be downloaded onto a volume similar to a Cinder snapshot (dest=volume).

Implementing the 'dest: local' images will require some work:

* Since the way these block devices will be handled is different than what we currently have (for block devices) - we will need to generilize the code that does base image download in creation to be able to accept data passed as image block devices.

* We will likely want to take advantage of using base images and caching them on hypervisor nodes - so this blueprint will cover extending and generalizing the code in nova/virt/libvirt/imagecache.py to be aware of the block devices and handle them according to the system configuration.

* We will need to make sure that drivers can advertise to the manager code that they will accept these new block devices. Most of the groundwork for this is laid out in https://review.openstack.org/#/c/39086/ and it will be mostly a matter of implementing a new DriverBlockDevice subtype.

* We will likely want to add horizon support for this as well.

Blueprint information

Status:
Not started
Approver:
Russell Bryant
Priority:
Undefined
Drafter:
Nikola ─Éipanov
Direction:
Needs approval
Assignee:
None
Definition:
Review
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Given the scope of the work listed, and no assignee, I'm kicking this out of I-1 for now. This also sounds like it could be split into separate blueprints for the first three bullet points.

Deferred to icehouse-3 as the blueprint was not approved by the icehouse-2 blueprint approval deadline. --russellb

ndipanov, says this is unlikely to make icehouse, so setting to "next" instead. --russellb

Removed from next, as next is now reserved for near misses from the last milestone --johnthetubaguy

Is DriverLocalImageBlockDevice a good name for the new DriverBlockDevice subtype? --wenjianhn

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.