Contents
- Configuring Tenant-specific Storage Locations for Images with Object Storage
- Adding images with glance image-create
- Getting virtual machine images
- Tool support for creating images
- Customizing an image for OpenStack
- Creating raw or QCOW2 images
- Booting a test image
- Tearing down (deleting) Instances
- Pausing and Suspending Instances
- Select a specific host to boot instances on
- Creating Custom Images
- Creating a Windows Image
- Creating images from running instances with KVM and Xen
- Replicating images across multiple data centers
You can use OpenStack Image Services 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, or you can use a client class in your Python code to accomplish the same tasks.
VM images made available through OpenStack Image Service can be stored in a variety of locations from simple file systems to object-storage systems like the OpenStack Object Storage project, or even use S3 storage either on its own or through an OpenStack Object Storage S3 interface.
The backend stores that OpenStack Image Service can work with are as follows:
OpenStack Object Storage - OpenStack Object Storage 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.
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.
