Add new metadata for image format

Registered by Jay Pipes on 2010-12-20

Images can be a variety of formats (OVF, AMI, etc). We should store the format for the image in the main images registry table and process an `x-image-meta-format` HTTP header.

Blueprint information

Status:
Complete
Approver:
Thierry Carrez
Priority:
Essential
Drafter:
Jay Pipes
Direction:
Approved
Assignee:
Jay Pipes
Definition:
Approved
Series goal:
Accepted for cactus
Implementation:
Implemented
Milestone target:
milestone icon cactus-2011-03-14
Started by
Jay Pipes on 2011-02-22
Completed by
Jay Pipes on 2011-03-07

Sprints

Whiteboard

Discussion about this occurred here: https://lists.launchpad.net/openstack/msg00205.html

Main agreements:

Adapt the Image model to store:

disk_format: choices: VHD, VDI, VMDK, raw
container_format: choices: OVF, OVA, & AMI.

Jordan: there should be the ability to associate parent and child disks, so you can save difference/cow disks and associate them with a parent disk and when pulling a child disk you get the parent with it to preserve it. If this was enabled you would need to add QCOW2 as a disk format but it would required a parent disk. VHDs have the same functionality but there is no file name difference, you just have to know what the parent is. - wishlist but worth keeping in mind.

I still don't understand how the appliance_format is used.

something like supported_hypervisor needs to be added and it should be able to store a list of hypervisors the image is known to work with.

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.