openstack/openstack-manuals
Code Issues Proposed changes
1911452d1a
openstack-manuals/doc/common-rst/get_started_image_service.rst
daz ab45cacbb6 Getting started chapter reorganisation 
1. Split chapter file content into section files per current Cloud Admin Guide
2. Added cross-references
Change-Id: I51025b6eb4bb9b8912871837f9ce83d91dca973d
Implements: blueprint reorganise-user-guides
2015-07-21 10:50:03 +10:00

1.4 KiB
Raw Blame History

OpenStack Image service

The OpenStack Image service is central to Infrastructure-as-a-Service (IaaS) as shown in get_started_conceptual_architecture. It accepts API requests for disk or server images, and image metadata from end users or OpenStack Compute components. It also supports the storage of disk or server images on various repository types, including OpenStack Object Storage.

A number of periodic processes run on the OpenStack Image service to support caching. Replication services ensure consistency and availability through the cluster. Other periodic processes include auditors, updaters, and reapers.

The OpenStack Image service includes the following components:

glance-api

Accepts Image API calls for image discovery, retrieval, and storage.

glance-registry

Stores, processes, and retrieves metadata about images. Metadata includes items such as size and type.

Note

The registry is a private internal service meant for use by OpenStack Image service. Do not disclose it to users.

Database

Stores image metadata and you can choose your database depending on your preference. Most deployments use MySQL or SQLite.

Storage repository for image files

Various repository types are supported including normal file systems, Object Storage, RADOS block devices, HTTP, and Amazon S3. Note that some repositories will only support read-only usage.