file-like objects returned from GET and used to POST do not have the same interface

[Jay Pipes]

From Vishy's question:

"I'm a bit lost as to why the client returns an iterator for get but then expects a file like object for add. It would be great if both of these worked the same way. Then it would be possible to do something like:

from glance import client

remote = client.Client('glance.provider.com')
local = client.Client('localhost')

metadata, image = remote.get_image(42)
local.add_image(metadata, image)"

There's no reason other than it's never been noticed until now :)

[Jay Pipes (jaypipes)]

This should be addressed in early Essex, along with the 2.0 Images API changes...

[Eoghan Glynn (eglynn)]

Also maintaining tolerance for the image_data types currently supported by add_image (i.e. file-like or string) would be useful.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/3307

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/3307
Committed: http://github.com/openstack/glance/commit/7094e8926c623a59e5d5fa2b5a9cca13738a79fe
Submitter: Jenkins
Branch: master

commit 7094e8926c623a59e5d5fa2b5a9cca13738a79fe
Author: Eoghan Glynn <email address hidden>
Date: Mon Jan 23 13:22:53 2012 +0000

    Client.add_image() accepts image data as iterable.

    Fixes bug 773562

    Allow the image data to be passed to glance.Client.add_add_image()
    via an iterator, in addition to the previously accepted images types
    (file-like or string).

    Change-Id: I1f90b9875f5610d478a5ed123fbf431501f1c2b6