Difference between revisions of "Obsolete:GlanceAPISpec"
Line 9: | Line 9: | ||
* Nova Integration | * Nova Integration | ||
** `nova.image.service.[[GlanceImageService]]` - An adapter in Nova to use Glance for retrieving and querying for images | ** `nova.image.service.[[GlanceImageService]]` - An adapter in Nova to use Glance for retrieving and querying for images | ||
− | *** `nova.image.service.[[ParallaxClient]]` - A client tool for querying Parallax about available images | + | *** `nova.image.service.[[ParallaxClient]]` - A client tool for querying Parallax about available images |
*** `nova.image.service.[[TellerClient]]` - A client tool for the chunked retrieval of an image | *** `nova.image.service.[[TellerClient]]` - A client tool for the chunked retrieval of an image | ||
Line 16: | Line 16: | ||
== Parallax API Commands == | == Parallax API Commands == | ||
− | This section describes the Parallax REST API for creating, listing, modifying, and deleting | + | This section describes the Parallax REST API for creating, listing, modifying, and deleting image metadata. |
=== Fetch id/name basic information on all public images === | === Fetch id/name basic information on all public images === | ||
Line 117: | Line 117: | ||
=== Register/create a new image === | === Register/create a new image === | ||
− | |||
− | |||
Line 125: | Line 123: | ||
</nowiki></pre> | </nowiki></pre> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
The body of the request shall be a JSON encoded mapping of the image's metadata: | The body of the request shall be a JSON encoded mapping of the image's metadata: | ||
Line 156: | Line 131: | ||
"image": | "image": | ||
{ | { | ||
− | "name": " | + | "name": "My Image", |
− | " | + | "status": "available", |
− | " | + | "image_type": "kernel" |
+ | "is_public": true, | ||
+ | "metadata": { "mykey": "myvalue" }, | ||
+ | "files": [ { "location": "swift://user:passwd@acct/container/obj.tar.gz.0", | ||
+ | "size": 101 } ] | ||
} | } | ||
} | } | ||
Line 164: | Line 143: | ||
− | + | The returned response, is successful, will be a JSON encoded mapping of the newly-created image in Parallax, including a populated `id` column with the new image's internal identifier: | |
− | |||
− | The returned response, will be a JSON encoded mapping of | ||
<pre><nowiki> | <pre><nowiki> | ||
{ | { | ||
− | |||
− | |||
− | |||
− | |||
"image": | "image": | ||
{ | { | ||
− | "id": | + | "id": 1, |
− | "name": " | + | "name": "My Image", |
− | "status": " | + | "status": "available", |
− | " | + | "image_type": "kernel" |
+ | "is_public": true, | ||
+ | "metadata": { "mykey": "myvalue" }, | ||
+ | "files": [ { "location": "swift://user:passwd@acct/container/obj.tar.gz.0", | ||
+ | "size": 101 } ] | ||
} | } | ||
} | } | ||
Line 188: | Line 165: | ||
==== Notes ==== | ==== Notes ==== | ||
− | The ` | + | The reason the body dict and result dict contains only a single element, 'image', is for XML conversion purposes, where the root element will be `<image>` and not the root XML namespace. |
+ | |||
+ | The `metadata` element is a mapping of custom metadata the image may have saved with it. | ||
+ | |||
+ | The `files` element is a list of mappings containing the chunks comprising an image along with the chunk's size | ||
=== Update an existing image's metadata === | === Update an existing image's metadata === | ||
Line 281: | Line 262: | ||
404:: Image was not found | 404:: Image was not found | ||
+ | |||
+ | === TODO -- Store an Image === | ||
+ | |||
+ | |||
+ | <pre><nowiki> | ||
+ | POST /images?uri=<Parallax URI for Image> | ||
+ | </nowiki></pre> | ||
+ | |||
+ | |||
+ | Immediately returns a mapping of image information indicating status of the image: | ||
+ | |||
+ | |||
+ | <pre><nowiki> | ||
+ | { | ||
+ | 'image': | ||
+ | { | ||
+ | 'id': identifier for image, | ||
+ | 'status': 'pending', | ||
+ | 'job_id': an identifier for the asynchronous job that is storing the image? | ||
+ | } | ||
+ | } | ||
+ | </nowiki></pre> |
Revision as of 20:38, 18 November 2010
Glance API Specification
Glance <=> Nova Integration requires these components:
- Glance - VM Image Management Service
- Parallax - Image Registry service
- Teller - Image Delivery service
- Nova Integration
- `nova.image.service.GlanceImageService` - An adapter in Nova to use Glance for retrieving and querying for images
- `nova.image.service.ParallaxClient` - A client tool for querying Parallax about available images
- `nova.image.service.TellerClient` - A client tool for the chunked retrieval of an image
- `nova.image.service.GlanceImageService` - An adapter in Nova to use Glance for retrieving and querying for images
<<TableOfContents()>>
Parallax API Commands
This section describes the Parallax REST API for creating, listing, modifying, and deleting image metadata.
Fetch id/name basic information on all public images
GET http://parallax.openstack.org/images
Returns a mapping containing a list of mappings containing details information about the public images encoded in JSON:
{ "images": [ {"id": 1, "name": "My Image 1"}, {"id": 2, "name": "My Image 2"}, ] }
Fetch detailed information on all public images
GET http://parallax.openstack.org/images/detail
Returns a mapping containing a list of mappings containing details information about the public images encoded in JSON:
{ "images": [ { "id": 1, "name": "My Image", "status": "available", "image_type": "kernel" "is_public": true, "metadata": { "mykey": "myvalue" }, "files": [ { "location": "swift://user:passwd@acct/container/obj.tar.gz.0", "size": 101 } ] } ] }
Notes
The `metadata` element is a mapping of custom metadata the image may have saved with it.
The `files` element is a list of mappings containing the chunks comprising an image along with the chunk's size
Fetch a single image's metadata
GET http://parallax.openstack.org/images/<ID>
Returns the image's metadata encoded in JSON:
{ "image": { "id": 1, "name": "My Image", "status": "available", "image_type": "kernel" "is_public": true, "metadata": { "mykey": "myvalue" }, "files": [ { "location": "swift://user:passwd@acct/container/obj.tar.gz.0", "size": 101 } ] } }
Notes
The reason the returned dict contains only a single element, 'image', is for XML conversion purposes, where the root element will be `<image>` and not the root XML namespace.
The `metadata` element is a mapping of custom metadata the image may have saved with it.
The `files` element is a list of mappings containing the chunks comprising an image along with the chunk's size
Exceptions
404:: Image was not found
Register/create a new image
POST http://parallax.openstack.org/images
The body of the request shall be a JSON encoded mapping of the image's metadata:
{ "image": { "name": "My Image", "status": "available", "image_type": "kernel" "is_public": true, "metadata": { "mykey": "myvalue" }, "files": [ { "location": "swift://user:passwd@acct/container/obj.tar.gz.0", "size": 101 } ] } }
The returned response, is successful, will be a JSON encoded mapping of the newly-created image in Parallax, including a populated `id` column with the new image's internal identifier:
{ "image": { "id": 1, "name": "My Image", "status": "available", "image_type": "kernel" "is_public": true, "metadata": { "mykey": "myvalue" }, "files": [ { "location": "swift://user:passwd@acct/container/obj.tar.gz.0", "size": 101 } ] } }
Notes
The reason the body dict and result dict contains only a single element, 'image', is for XML conversion purposes, where the root element will be `<image>` and not the root XML namespace.
The `metadata` element is a mapping of custom metadata the image may have saved with it.
The `files` element is a list of mappings containing the chunks comprising an image along with the chunk's size
Update an existing image's metadata
PUT http://parallax.openstack.org/images/<ID>
The body of the request shall be a JSON encoded mapping of the image's metadata:
{ "image": { "id": 2349823, "name": "My Image", "status": "disabled", "image_type": "kernel" "is_public": true, "metadata": { "mykey": "myvalue" }, "files": [ { "location": "swift://user:passwd@acct/container/obj.tar.gz.0", "size": 101 } ] } }
The returned response, if successful, will be a JSON encoded mapping of the updated image metadata in Parallax:
{ "image": { "id": 2349823, "name": "My Image", "status": "disabled", "image_type": "kernel" "is_public": true, "metadata": { "mykey": "myvalue" }, "files": [ { "location": "swift://user:passwd@acct/container/obj.tar.gz.0", "size": 101 } ] } }
Notes
The reason the body dict and result dict contains only a single element, 'image', is for XML conversion purposes, where the root element will be `<image>` and not the root XML namespace.
The `metadata` element is a mapping of custom metadata the image may have saved with it.
The `files` element is a list of mappings containing the chunks comprising an image along with the chunk's size
Exceptions
404:: Image was not found
Delete an existing image from the registry
DELETE http://parallax.openstack.org/images/<ID>
The body of the request will be ignored.
Exceptions
404:: Image was not found
Teller API Commands
This section describes the Teller REST API.
Fetch an Image
GET /images?uri=<Parallax URI for Image>
Returns the virtual machine image data as response body.
Exceptions
404:: Image was not found
TODO -- Store an Image
POST /images?uri=<Parallax URI for Image>
Immediately returns a mapping of image information indicating status of the image:
{ 'image': { 'id': identifier for image, 'status': 'pending', 'job_id': an identifier for the asynchronous job that is storing the image? } }