← Back to team overview

openstack team mailing list archive

Re: Image API v2 Draft 4

 


> APPENDIX B: Outstanding issues
> ...
> 2) How do we fit the existing 'copy_from' functionality in?


Is the v2 API retaining some equivalent of the existing
x-image-meta-location header, to allow an externally-stored
image be registered with glance?

e.g. via an image field specified on create or update:

  POST /images HTTP/1.1
  {"external-location": "s3://access:secret@xxxxxxxxxxxxxxx/image", ...}

or:

  PUT /images/<IMAGE_ID> HTTP/1.1
  {"external-location": "s3://access:secret@xxxxxxxxxxxxxxx/image", ...}

If so, the most straight-forward approach for copy-from would be to
follow a similar pattern with an image field such as:

  POST /images HTTP/1.1
  {"copy-from": "s3://access:secret@xxxxxxxxxxxxxxx/image", ...}

... etc.

Cheers,
Eoghan



Follow ups

References