ca9c7bbe27
Users could be confused into thinking the glance registry is an external-facing service. It is not, and is designed with a security model such that it should be protected for internal use only. This patch adds a note to the introduction in the common section so it will be included in multiple guides. Change-Id: Ic540353d82c829475ac6f3455ccccdea32977a4b Closes-Bug: 1252931
45 lines
2.1 KiB
XML
45 lines
2.1 KiB
XML
<section xmlns="http://docbook.org/ns/docbook"
|
|
xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
|
|
xml:id="image-service-overview">
|
|
<title>Image Service overview</title>
|
|
<para>The Image Service includes the following
|
|
components:</para>
|
|
<itemizedlist>
|
|
<listitem>
|
|
<para><systemitem class="service">glance-api</systemitem>.
|
|
Accepts Image API calls for image discovery, retrieval,
|
|
and storage.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para><systemitem class="service"
|
|
>glance-registry</systemitem>. Stores, processes, and
|
|
retrieves metadata about images. Metadata includes items such
|
|
as size and type.</para>
|
|
<note><title>Security note</title>
|
|
<para>The registry is a private internal service meant only for use
|
|
by the Image Service itself. Do not expose it to users.</para></note>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Database. Stores image metadata. You can choose your
|
|
database depending on your preference. Most deployments
|
|
use MySQL or SQlite.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Storage repository for image files. The Image Service
|
|
supports a variety of repositories including normal file systems,
|
|
Object Storage, RADOS block devices, HTTP, and Amazon S3. Some
|
|
types of repositories support only read-only usage.</para>
|
|
</listitem>
|
|
</itemizedlist>
|
|
<para>A number of periodic processes run on the Image Service to
|
|
support caching. Replication services ensures consistency and
|
|
availability through the cluster. Other periodic processes
|
|
include auditors, updaters, and reapers.</para>
|
|
<para>As shown in <xref linkend="conceptual-architecture"/>, the Image
|
|
Service is central to the overall IaaS picture. It accepts API
|
|
requests for images or image metadata from end users or
|
|
Compute components and can store its disk files in the Object
|
|
Storage Service.</para>
|
|
</section>
|