I've been looking into the existing task-based-upload that Doug mentions:
can anyone clarify the following?
On a default devstack install you can do this 'task' call:
http://paste.openstack.org/show/462919
Yup. That's the one.
as an alternative to the traditional image upload (the bytes are streamed
from the URL).
It's not clear to me if this is just an interesting example of the kind
of operator specific thing you can configure tasks to do, or a real
attempt to define an alternative way to upload images.
The change which added it [1] calls it a 'sample'.
Is it just an example, or is it a second 'official' upload path?
It's how you have to upload images on Rackspace.
Ok, so Rackspace have a task called image_import. But it seems to take
different json input than the devstack version. (A Swift container/object
rather than a URL.)
That seems to suggest that tasks really are operator specific, that there
is no standard task based upload ... and it should be ok to try
again with a clean slate.
If you want to see the
full fun:
https://github.com/openstack-infra/shade/blob/master/shade/__init__.py#L1335-L1510
Which is "I want to upload an image to an OpenStack Cloud"
I've listed it on this slide in CLI format too:
http://inaugust.com/talks/product-management/index.html#/27
It should be noted that once you create the task, you need to poll the
task with task-show, and then the image id will be in the completed
task-show output.
Monty
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
