openstack/glance
Code Issues Proposed changes

Updating image status docs

Browse Source 
Fixes lp bug#844932

Change-Id: Iee4571a2ebdd295f4324e02cde65a96fb53aceb9
This commit is contained in:
Brian Waldon 2011-09-09 16:41:46 -04:00
parent 3595cf7500
commit ee8c8ba8f5
1 changed files with 19 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
doc/source/statuses.rst
View File

@ -17,32 +17,38 @@
Image Statuses Image Statuses
============== ==============
Images in Glance can be in one of four statuses: Images in Glance can be in one the following statuses:
* ``queued`` * ``queued``
Denotes an image identifier has been reserved for an image in Glance (or The image identifier has been reserved for an image in the Glance
more specifically, reserved in the registries Glance uses) and that no registry. No image data has been uploaded to Glance.
actual image data has yet to be uploaded to Glance
* ``saving`` * ``saving``
Denotes that an image's raw image data is currently being uploaded to Denotes that an image's raw data is currently being uploaded to Glance.
Glance When an image is registered with a call to `POST /images` and there
is an `x-image-meta-location` header present, that image will never be in
the `saving` status (as the image data is already available in some other
location).
* ``active`` * ``active``
Denotes an image that is fully available in Glance Denotes an image that is fully available in Glance.
* ``killed`` * ``killed``
Denotes that an error occurred during the uploading of an image's data, Denotes that an error occurred during the uploading of an image's data,
and that the image is not readable and that the image is not readable.
* ``deleted``
.. note:: Glance has retained the information about the image, but it is no longer
available to use. An image in this state will be removed automatically
at a later date.
* ``pending_delete``
This is similiar to `deleted`, however, Glance has not yet removed the
image data. An image in this state is recoverable.
When an image is registered with a call to `POST /images` and there
is an `x-image-meta-location` header present, that image will never be in
the `saving` status (as the image data is already available in some other
location)