Difference between revisions of "Glance-new-download-workflow"
(Created page with "This is the full specification for blueprint:https://blueprints.launchpad.net/glance/+spec/new-download-workflow") |
|||
| Line 1: | Line 1: | ||
This is the full specification for blueprint:https://blueprints.launchpad.net/glance/+spec/new-download-workflow | This is the full specification for blueprint:https://blueprints.launchpad.net/glance/+spec/new-download-workflow | ||
| + | |||
| + | == Motivation == | ||
| + | Here's why we want an alternative to the "normal" Glance download workflow: | ||
| + | * want to allow a cloud provider the opportunity to "scrub" or otherwise process an image that's going to be pulled out of that provider's cloud | ||
| + | ** they don't have to, but want to make the option available | ||
| + | * want to push all efforts associated with getting images out of the cloud to the cloud periphery so the bandwidth/compute required doesn't affect normal cloud functionality | ||
| + | |||
| + | |||
| + | We propose calling this functionality "export" (to keep symmetry with the proposed new "import" functionality <ref>https://wiki.openstack.org/wiki/Glance-new-upload-workflow</ref>) | ||
| + | |||
| + | == Example Workflow (API View) == | ||
| + | |||
| + | === Initial Export Request === | ||
| + | <pre> | ||
| + | Request 1: POST /v2/images//export | ||
| + | { "some-stuff" : "whatever" } | ||
| + | </pre> | ||
| + | <pre> | ||
| + | Response 1: 201 created | ||
| + | Location: "http://glance-server/v2/image-exports/12345678-1234-1234-1234-123456789abc" | ||
| + | </pre> | ||
| + | <pre> | ||
| + | Request 2 - N: GET /v2/image-exports/12345678-1234-1234-1234-123456789abc | ||
| + | </pre> | ||
| + | <pre> | ||
| + | Response 2 - N-1: 200 OK | ||
| + | { "status" : "waiting", "image_uuid" : } | ||
| + | </pre> | ||
| + | <pre> | ||
| + | Response N: | ||
| + | </pre> | ||
| + | <pre> | ||
| + | </pre> | ||
| + | |||
| + | |||
| + | == References == | ||
| + | <references /> | ||
Revision as of 18:43, 21 May 2013
This is the full specification for blueprint:https://blueprints.launchpad.net/glance/+spec/new-download-workflow
Motivation
Here's why we want an alternative to the "normal" Glance download workflow:
- want to allow a cloud provider the opportunity to "scrub" or otherwise process an image that's going to be pulled out of that provider's cloud
- they don't have to, but want to make the option available
- want to push all efforts associated with getting images out of the cloud to the cloud periphery so the bandwidth/compute required doesn't affect normal cloud functionality
We propose calling this functionality "export" (to keep symmetry with the proposed new "import" functionality [1])
Example Workflow (API View)
Initial Export Request
Request 1: POST /v2/images//export
{ "some-stuff" : "whatever" }
Response 1: 201 created Location: "http://glance-server/v2/image-exports/12345678-1234-1234-1234-123456789abc"
Request 2 - N: GET /v2/image-exports/12345678-1234-1234-1234-123456789abc
Response 2 - N-1: 200 OK
{ "status" : "waiting", "image_uuid" : }
Response N:
