openstack/glance
Code Issues Proposed changes
abcff5b5f5
glance/doc/source/statuses.rst
Eoghan Glynn 6873195cd1 Support zero-size image creation via the v1 API 
Addresses LP 1025353 for the v1 API.

Transition image status to active immediately on creation
(as opposed to leaving it queued forever) if the size is set
to zero from the get-go.

The v2 implementation is left unchanged for now, as the image
status does not appear to ever transition from queued to active
in that case.

This change allows an image to be created that simply acts as
a properties bucket, but requires no image data. For example,
an image created from a booted-from-volume instance where only
the kernel, ramdisk ID, and block device mappings are required.

Change-Id: I61e96f3fe5f5245fec791170b4a8b4c72135c3de
2012-07-16 17:29:43 +01:00

1.8 KiB
Raw Blame History

Image Statuses

Images in Glance can be in one the following statuses:

  • queued

    The image identifier has been reserved for an image in the Glance registry. No image data has been uploaded to Glance and the image size was not explicitly set to zero on creation.

  • saving

    Denotes that an image's raw data is currently being uploaded to 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

    Denotes an image that is fully available in Glance. This occurs when the image data is uploaded, or the image size is explicitly set to zero on creation.

  • killed

    Denotes that an error occurred during the uploading of an image's data, and that the image is not readable.

  • deleted

    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.