OpenStack Image Registry and Delivery Service (Glance)

Allow images to be uploaded to glance from an external location

Registered by Eoghan Glynn on 2012-02-08

External HTTP, S3 or Swift locations can be referenced when adding a new image, via the X-Image-Meta-Location header. The result is that the image content is not uploaded to glance, instead the external location is relied upon when serving out the image (modulo caching).

The Horizon team have a requirement to allow an image be added based on content from a pre-existing location, and for glance to actually upload from that external store. This could be acheived by adding support for a new header:

  X-Image-Meta-Copy-From: URI

where URI is a HTTP, S3, or Swift location that's accessible to the glance API service. The result would be that the image content is uploaded to the backend store currently configured for the glance API service.

Blueprint information

Status:
Complete
Approver:
Eoghan Glynn
Priority:
Medium
Drafter:
Eoghan Glynn
Direction:
Approved
Assignee:
Eoghan Glynn
Definition:
Approved
Series goal:
Accepted for essex
Implementation:
Implemented
Milestone target:
milestone icon 2012.1
Started by
Eoghan Glynn on 2012-02-14
Completed by
Eoghan Glynn on 2012-02-22

Related branches

Sprints

Whiteboard

Changed from X-Image-Meta-Retrieve-From to X-Image-Meta-Copy-From to avoid any ambiguity around whether the retrieval from external store ever recurs after the initial upload. The copy verb is clearer in that repect.

It also has the advantage of similarity to the Swift X-Copy-From header.

Addressed by: https://review.openstack.org/4096
    Support new image copied from external storage.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.