- Configuring Tenant-specific Storage Locations for Images with Object Storage
- Adding images with glance image-create
- Getting virtual machine images
- Booting a test image
- Tearing down (deleting) Instances
- Pausing and Suspending Instances
- Select a specific host to boot instances on
- Creating images from running instances with KVM and Xen
- Replicating images across multiple data centers
The OpenStack Image Service, code-named glance, provides functionality for discovering, registering, and retrieving virtual machine images. The service includes a RESTful API that allows users to query VM image metadata and retrieve the actual image with HTTP requests. You can also use the glance command-line tool, or the Python API to accomplish the same tasks.
VM images made available through OpenStack Image Service can be stored in a variety of locations. The OpenStack Image Service supports the following backend stores:
OpenStack Object Storage - OpenStack Object Storage (code-named swift) is the highly-available object storage project in OpenStack.
Filesystem - The default backend that OpenStack Image Service uses to store virtual machine images is the filesystem backend. This simple backend writes image files to the local filesystem.
S3 - This backend allows OpenStack Image Service to store virtual machine images in Amazon’s S3 service.
HTTP - OpenStack Image Service can read virtual machine images that are available via HTTP somewhere on the Internet. This store is readonly.
Rados Block Device (RBD) - This backend stores images inside of a Ceph storage cluster using Ceph's RBD interface.
GridFS - This backend stores images inside of MongoDB.
This chapter assumes you have a working installation of the Image Service, with a working endpoint and users created in the Identity Service, plus you have sourced the environment variables required by the nova client and glance client.
