openstack/openstack-manuals
Code Issues Proposed changes

s/Image Service/Image service/g

Browse Source 
Change capitalization as discussed on openstack-docs mailing list.

Change-Id: I2ad81bffbd59bdd8b908664bb0a1ee16da1bf7ae
This commit is contained in:
Andreas Jaeger 2015-04-14 15:47:59 +02:00
parent f8a49d1dbf
commit 3ca32b8434
85 changed files with 233 additions and 233 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/admin-guide-cloud/blockstorage/section_ts_eql_volume_size.xml
View File

@ -13,10 +13,10 @@
<section xml:id="ts_eql_vol_size_problem">
<title>Problem</title>
<para>There is a discrepancy between both the actual volume size in EqualLogic (EQL)
storage and the image size in the Image Service, with what is reported
storage and the image size in the Image service, with what is reported
OpenStack database. This could lead to confusion if a user is creating
volumes from an image that was uploaded from an EQL volume (through the
Image Service). The image size is slightly larger than the target volume
Image service). The image size is slightly larger than the target volume
size; this is because EQL size reporting accounts for additional storage
used by EQL for internal volume metadata.</para>
<para>To reproduce the issue follow the steps in the following procedure.</para>
@ -95,7 +95,7 @@ ReplicationReserveSpace: 0MB</computeroutput></screen>
+---------------------+---------------------------------------+</computeroutput></screen>
</step>
<step>
<para>When you uploaded the volume in the previous step, the Image Service
<para>When you uploaded the volume in the previous step, the Image service
reported the volume's size as <literal>1</literal> (GB). However, when
using <command>glance image-list</command> to list the image, the
displayed size is 1085276160 bytes, or roughly 1.01&nbsp;GB:</para>
@ -122,7 +122,7 @@ ReplicationReserveSpace: 0MB</computeroutput></screen>
3020a21d-ba37-4495-8899-07fc201161b9</literal> in this example) as
the source. Set the target volume size to 1&nbsp;GB; this is the size reported
by the <command>cinder</command> tool when you uploaded the volume to
the Image Service:</para>
the Image service:</para>
<screen><prompt>$</prompt> <userinput>cinder create --display-name volume2 \
--image-id 3020a21d-ba37-4495-8899-07fc201161b9 1</userinput>
<computeroutput>ERROR: Invalid input received: Size of specified image 2 is larger

2
doc/admin-guide-cloud/ch_compute.xml
View File

@ -338,7 +338,7 @@
<section xml:id="section_instance-building-blocks">
<title>Building blocks</title>
<para>In OpenStack the base operating system is usually copied
from an image stored in the OpenStack Image Service. This
from an image stored in the OpenStack Image service. This
is the most common case and results in an ephemeral
instance that starts from a known template state and loses
all accumulated states on virtual machine deletion. It is

4
doc/admin-guide-cloud/ch_database.xml
View File

@ -30,8 +30,8 @@ trove_auth_url = http://<replaceable>controller</replaceable>:35357/v2.0</progra
<para>This example assumes you have created a MySQL 5.5 image called <literal>mysql-5.5.qcow2</literal>.</para>
</step>
<step>
<title>Register image with Image Service</title>
<para>You need to register your guest image with the Image Service.</para>
<title>Register image with Image service</title>
<para>You need to register your guest image with the Image service.</para>
<para>In this example, you use the glance <command>image-create</command> command to register a <literal>mysql-5.5.qcow2</literal> image.</para>
<screen>$<prompt></prompt> <userinput>glance image-create --name mysql-5.5 --disk-format qcow2 --container-format bare --is-public True &lt; mysql-5.5.qcow2</userinput>
<computeroutput>+------------------+--------------------------------------+

16
doc/admin-guide-cloud/compute/section_compute-image-mgt.xml
View File

@ -5,7 +5,7 @@
version="5.0"
xml:id="section_image-mgmt">
<title>Image management</title>
<para>The OpenStack Image Service discovers, registers, and
<para>The OpenStack Image service discovers, registers, and
retrieves virtual machine images. The service also includes a
RESTful API that allows you to query VM image metadata and
retrieve the actual image with HTTP requests. For more
@ -14,25 +14,25 @@
>OpenStack API Complete Reference</link> and the <link
xlink:href="http://docs.openstack.org/developer/python-glanceclient/"
>Python API</link>.</para>
<para>The OpenStack Image Service can be controlled using a
<para>The OpenStack Image service can be controlled using a
command-line tool. For more information about using the
OpenStack Image command-line tool, see the <link
xlink:href="http://docs.openstack.org/user-guide/content/cli_manage_images.html"
>Manage Images</link> section in the <citetitle>OpenStack
End User Guide</citetitle>.</para>
<para>Virtual images that have been made available through the
Image Service can be stored in a variety of ways. In order to
Image service can be stored in a variety of ways. In order to
use these services, you must have a working installation of
the Image Service, with a working endpoint, and users that
the Image service, with a working endpoint, and users that
have been created in OpenStack Identity. Additionally, you
must meet the environment variables required by the Compute
and Image Service clients.</para>
<para>The Image Service supports these back-end stores:</para>
and Image service clients.</para>
<para>The Image service supports these back-end stores:</para>
<variablelist>
<varlistentry>
<term>File system</term>
<listitem>
<para>The OpenStack Image Service stores virtual
<para>The OpenStack Image service stores virtual
machine images in the file system back end by
default. This simple back end writes image files
to the local file system.</para>
@ -54,7 +54,7 @@
<varlistentry>
<term>HTTP</term>
<listitem>
<para>OpenStack Image Service can read virtual machine
<para>OpenStack Image service can read virtual machine
images that are available on the Internet using
HTTP. This store is read only.</para>
</listitem>

6
doc/admin-guide-cloud/compute/section_compute-images-instances.xml
View File

@ -4,7 +4,7 @@
xml:id="section_compute-images-and-instances">
<title>Images and instances</title>
<para>Disk images provide templates for virtual machine file systems. The
Image Service controls storage and management of images.</para>
Image service controls storage and management of images.</para>
<para>Instances are the individual virtual machines that run on physical
compute nodes. Users can launch any number of instances from the same
image. Each launched instance runs from a copy of the base image so that
@ -28,7 +28,7 @@
<listitem>
<para>For more information about image configuration options,
see the <link xlink:href="http://docs.openstack.org/juno/config-reference/content/ch_configuring-openstack-image-service.html">
Image Services</link> section of the <citetitle>OpenStack
Image services</link> section of the <citetitle>OpenStack
Configuration Reference</citetitle>.</para>
</listitem>
<listitem>
@ -46,7 +46,7 @@
service, which provides persistent block storage, instead of the
ephemeral storage provided by the selected instance flavor.</para>
<para>This diagram shows the system state prior to launching an instance.
The image store, fronted by the Image Service (glance) has a number of
The image store, fronted by the Image service (glance) has a number of
predefined images. Inside the cloud, a compute node contains the
available vCPU, memory, and local disk resources. Additionally, the
<systemitem class="service">cinder-volume</systemitem> service provides

2
doc/admin-guide-cloud/compute/section_compute-instance-building-blocks.xml
View File

@ -6,7 +6,7 @@
xml:id="section_compute-instance-building-blocks">
<title>Instance building blocks</title>
<para>In OpenStack, the base operating system is usually copied from an
image stored in the OpenStack Image Service. This results in an
image stored in the OpenStack Image service. This results in an
ephemeral instance that starts from a known template state and loses all
accumulated states on shutdown.</para>
<para>You can also put an operating system on a persistent volume in

4
doc/admin-guide-cloud/compute/section_compute-system-admin.xml
View File

@ -41,7 +41,7 @@
<listitem>
<para><systemitem class="service">nova-objectstore</systemitem>: a
simple file-based storage system for images that replicates most
of the S3 API. It can be replaced with OpenStack Image Service and
of the S3 API. It can be replaced with OpenStack Image service and
either a simple image manager or OpenStack Object Storage as the
virtual machine image storage facility. It must exist on the same
node as <systemitem class="service">nova-compute</systemitem>.</para>
@ -271,7 +271,7 @@ qualname = nova</programlisting>
<systemitem>syslog</systemitem>. This is useful if you want to use
<systemitem>rsyslog</systemitem> to forward logs to a remote machine.
Separately configure the Compute service (nova), the Identity
service (keystone), the Image Service (glance), and, if you are
service (keystone), the Image service (glance), and, if you are
using it, the Block Storage service (cinder) to send log messages to
<systemitem>syslog</systemitem>. Open these configuration files:</para>
<itemizedlist>

8
doc/admin-guide-cloud/image/section_glance-nova-image-download.xml
View File

@ -13,7 +13,7 @@
Prior to starting a virtual machine, the virtual machine image
used must be transferred to the compute node from the Image
Service. How this works can change depending on the settings
chosen for the compute node and the Image Service.
chosen for the compute node and the Image service.
</para>
<para>
Typically, the Compute service will use the image identifier
@ -21,8 +21,8 @@
Image API. Though images are not stored in glance&mdash;rather in a
back end, which could be Object Storage, a filesystem or any other
supported method&mdash;the connection is made from the compute node
to the Image Service and the image is transferred over this
connection. The Image Service streams the image from the back end to the
to the Image service and the image is transferred over this
connection. The Image service streams the image from the back end to the
compute node.
</para>
<para>
@ -34,7 +34,7 @@
</para>
<para>
Certain back ends support a more direct method, where on request
the Image Service will return a URL that can be used to
the Image service will return a URL that can be used to
download the image directly from the back-end store. Currently the
only store to support the direct download approach is the
filesystem store. It can be configured using the

2
doc/admin-guide-cloud/networking/section_networking_arch.xml
View File

@ -11,7 +11,7 @@
<title>Overview</title>
<para>Networking is a standalone component in the OpenStack modular
architecture. It's positioned alongside OpenStack components such
as Compute, Image Service, Identity, or the Dashboard. Like
as Compute, Image service, Identity, or the Dashboard. Like
those components, a deployment of Networking often involves
deploying several services to a variety of hosts.</para>
<para>The Networking server uses the <systemitem class="service"

4
doc/admin-guide-cloud/telemetry/section_telemetry-data-collection.xml
View File

@ -88,7 +88,7 @@
<td></td>
</tr>
<tr>
<td>OpenStack Image Service</td>
<td>OpenStack Image service</td>
<td><para>image.update</para>
<para>image.upload</para>
<para>image.delete</para>
@ -96,7 +96,7 @@
<td>The required configuration for Image service can be found in the
<link xlink:href=
"http://docs.openstack.org/juno/install-guide/install/apt/content/ceilometer-agent-glance.html">
Configure the Image Service for Telemetry section</link> section
Configure the Image service for Telemetry section</link> section
in the <citetitle>OpenStack Installation Guide</citetitle>.</td>
</tr>
<tr>

2
doc/admin-guide-cloud/telemetry/section_telemetry-data-retrieval.xml
View File

@ -243,7 +243,7 @@
<note>
<para>The Telemetry module captures the user-visible resource usage data. Therefore
the database will not contain any data without the existence of these resources,
like VM images in the OpenStack Image Service.</para>
like VM images in the OpenStack Image service.</para>
</note>
<para>Similarly to other OpenStack command line clients, the <command>ceilometer</command>
client uses OpenStack Identity for authentication. The proper credentials and

4
doc/admin-guide-cloud/telemetry/section_telemetry-measurements.xml
View File

@ -224,8 +224,8 @@
<xi:include href="tables/ceilometer-measurements-snmp.xml"/>
</section>
<section xml:id="section_telemetry-image-meters">
<title>OpenStack Image Service</title>
<para>The following meters are collected for OpenStack Image Service:</para>
<title>OpenStack Image service</title>
<para>The following meters are collected for OpenStack Image service:</para>
<xi:include href="tables/ceilometer-measurements-glance.xml"/>
</section>
<section xml:id="section_telemetry-volume-meters">

2
doc/arch-design/compute_focus/section_architecture_compute_focus.xml
View File

@ -472,7 +472,7 @@
<title>OpenStack components</title>
<para>The selection of which OpenStack components will actually be
included in the design and deployed has significant impact. There are
certain components that will always be present, (Compute and Image Service, for
certain components that will always be present, (Compute and Image service, for
example) yet there are other services that might not need to be present.
For example, a certain design may not require the Orchestration module.
Omitting Heat would not typically have a significant impact on the

2
doc/arch-design/compute_focus/section_prescriptive_examples_compute_focus.xml
View File

@ -114,7 +114,7 @@
the addresses were assigned to.</para></section>
<section xml:id="storage-architecture">
<title>Storage architecture</title>
<para>The OpenStack Image Service is deployed in the API cell and
<para>The OpenStack Image service is deployed in the API cell and
configured to expose version 1 (V1) of the API. As a result
the image registry is also required. The storage back end in
use is a 3 PB Ceph cluster.</para>

2
doc/arch-design/compute_focus/section_tech_considerations_compute_focus.xml
View File

@ -367,7 +367,7 @@
<para>OpenStack Compute (nova)</para>
</listitem>
<listitem>
<para>OpenStack Image Service (glance)</para>
<para>OpenStack Image service (glance)</para>
</listitem>
<listitem>
<para>OpenStack Identity (keystone)</para>

2
doc/arch-design/generalpurpose/section_architecture_general_purpose.xml
View File

@ -667,7 +667,7 @@
<title>OpenStack components</title>
<para>Selecting which OpenStack components are included in the overall
design can have a significant impact. Some OpenStack components, like
compute and Image Service, are required in every architecture. Other
compute and Image service, are required in every architecture. Other
components, like Orchestration, are not always required.</para>
<para>Excluding certain OpenStack components can limit or constrain
the functionality of other components. For example, if the architecture includes

2
doc/arch-design/generalpurpose/section_prescriptive_example_general_purpose.xml
View File

@ -77,7 +77,7 @@
archiving.</para>
<para>Additional capabilities can be realized by
moving static web content to be served from OpenStack Object
Storage containers, and backing the OpenStack Image Service
Storage containers, and backing the OpenStack Image service
with OpenStack Object Storage.</para>
<note>
<para>

2
doc/arch-design/generalpurpose/section_tech_considerations_general_purpose.xml
View File

@ -517,7 +517,7 @@
(<glossterm>neutron</glossterm>)</para>
</listitem>
<listitem>
<para>OpenStack <glossterm>Image Service</glossterm>
<para>OpenStack <glossterm>Image service</glossterm>
(<glossterm>glance</glossterm>)</para>
</listitem>
<listitem>

4
doc/arch-design/multi_site/section_operational_considerations_multi_site.xml
View File

@ -85,7 +85,7 @@
(keystone).</para>
</listitem>
<listitem>
<para>Upgrade the OpenStack Image Service (glance).</para>
<para>Upgrade the OpenStack Image service (glance).</para>
</listitem>
<listitem>
<para>Upgrade OpenStack Compute (nova), including
@ -106,7 +106,7 @@
(keystone) deployment.</para>
</listitem>
<listitem>
<para>Upgrade the OpenStack Image Service (glance) at each
<para>Upgrade the OpenStack Image service (glance) at each
site.</para>
</listitem>
<listitem>

4
doc/arch-design/multi_site/section_prescriptive_examples_multi_site.xml
View File

@ -109,7 +109,7 @@
<para>OpenStack Controller services running, Networking,
dashboard, Block Storage and Compute running locally in
each of the three regions. The other services,
Identity, Orchestration, Telemetry, Image Service and
Identity, Orchestration, Telemetry, Image service and
Object Storage can be
installed centrally&mdash;with nodes in each of the region
providing a redundant OpenStack Controller plane
@ -176,7 +176,7 @@
external tools were not needed.</para>
<para>
OpenStack Object Storage is used here to serve as a back end for
the Image Service since it is the most suitable solution for a
the Image service since it is the most suitable solution for a
globally distributed storage solution&mdash;with its own
replication mechanism. Home grown solutions could also have
been used including the handling of replication&mdash;but were not

2
doc/arch-design/multi_site/section_tech_considerations_multi_site.xml
View File

@ -170,7 +170,7 @@
<para>Most OpenStack installations require a bare minimum set of
pieces to function. These include the OpenStack Identity
(keystone) for authentication, OpenStack Compute
(nova) for compute, OpenStack Image Service (glance) for image
(nova) for compute, OpenStack Image service (glance) for image
storage, OpenStack Networking (neutron) for networking, and
potentially an object store in the form of OpenStack Object
Storage (swift). Bringing multi-site into play also demands extra

2
doc/arch-design/multi_site/section_user_requirements_multi_site.xml
View File

@ -74,7 +74,7 @@
<para>It is essential that the deployment of instances is
consistent across the different sites. This needs to be built
into the infrastructure. If the OpenStack Object Storage is used as
a back end for the Image Service, it is possible to create repositories of
a back end for the Image service, it is possible to create repositories of
consistent images across multiple sites. Having central
endpoints with multiple storage nodes allows consistent centralized
storage for each and every site.</para>

2
doc/arch-design/network_focus/section_prescriptive_examples_network_focus.xml
View File

@ -67,7 +67,7 @@
</listitem>
</itemizedlist>
<para>
Beyond the normal Identity, Compute, Image Service and Object
Beyond the normal Identity, Compute, Image service and Object
Storage components, the Orchestration module is a recommended
component to handle properly scaling the workloads to adjust to
demand. Due to the requirement for auto-scaling,

4
doc/arch-design/specialized/section_hardware_specialized.xml
View File

@ -25,13 +25,13 @@
<section xml:id="solutions-specialized-hardware">
<title>Solutions</title>
<para>To provide cryptography offloading to a set of
instances, you can use Image Service configuration
instances, you can use Image service configuration
options to assign the cryptography chip to a device node in
the guest. The <citetitle>OpenStack Command Line
Reference</citetitle> contains further information on
configuring this solution in the chapter <link
xlink:href="http://docs.openstack.org/cli-reference/content/chapter_cli-glance-property.html">
Image Service property keys</link>, but it allows all
Image service property keys</link>, but it allows all
guests using the configured images to access the hypervisor
cryptography device.</para>
<para>If you require direct access to a specific device, PCI

6
doc/arch-design/specialized/section_multi_hypervisor_specialized.xml
View File

@ -30,16 +30,16 @@
workloads that must run on ESXi can target those
hypervisors, but the rest target the KVM
hypervisors.</para>
<para>Images in the OpenStack Image Service have particular
<para>Images in the OpenStack Image service have particular
hypervisor metadata attached so that when a user requests a
certain image, the instance spawns on the relevant
aggregate. Images for ESXi use the VMDK format. You can convert
QEMU disk images to VMDK, VMFS Flat Disks, which
includes thin, thick, zeroed-thick, and eager-zeroed-thick.
Note that after you export a VMFS thin disk from VMFS to a
non-VMFS location, for example the OpenStack Image Service, it
non-VMFS location, for example the OpenStack Image service, it
becomes a preallocated flat disk. This impacts the transfer
time from the OpenStack Image Service to the data store as it
time from the OpenStack Image service to the data store as it
requires moving the full preallocated flat disk rather than the
thin disk.</para>
<para>This example has the additional complication that, rather

4
doc/arch-design/storage_focus/section_architecture_storage_focus.xml
View File

@ -488,7 +488,7 @@
<title>OpenStack components</title>
<para>Which OpenStack components you choose can have a significant
impact on the overall design. While there are certain
components that are always present, Compute and Image Service, for
components that are always present, Compute and Image service, for
example, there are other services that may not need to be
present. As an example, a certain design may not require
the Orchestration module. Omitting Orchestration would not typically have a
@ -519,7 +519,7 @@
<para>OpenStack Block Storage (cinder)</para>
</listitem>
<listitem>
<para>OpenStack Image Service (glance)</para>
<para>OpenStack Image service (glance)</para>
</listitem>
<listitem>
<para>OpenStack Networking (neutron) or legacy networking (nova-network)</para>

2
doc/cli-reference/bk-cli-reference.xml
View File

@ -75,7 +75,7 @@
<para>For the Icehouse release, updated
documentation for clients, add trove
options, document neutron-debug,
document Image Service property
document Image service property
keys.</para>
</listitem>
</itemizedlist>

6
doc/cli-reference/ch_cli_glance_property_keys.xml
View File

@ -9,7 +9,7 @@
version="5.0"
xml:id="chapter_cli-glance-property">
<!-- This file is manually generated, unlike many of the other chapters. -->
<title>Image Service property keys</title>
<title>Image service property keys</title>
<para>The following keys, together with the components to which they are specific, can be used
with the <option>property</option> option for both the <command>glance
image-update</command> and <command>glance image-create</command> commands. For
@ -138,7 +138,7 @@
<tr valign="top">
<td>All</td>
<td>kernel_id</td>
<td>The ID of an image stored in the Image Service that should be used as the kernel
<td>The ID of an image stored in the Image service that should be used as the kernel
when booting an AMI-style image.</td>
<td>Valid image ID</td>
</tr>
@ -209,7 +209,7 @@
<tr valign="top">
<td>All</td>
<td>ramdisk_id</td>
<td>The ID of image stored in the Image Service that should be used as the ramdisk
<td>The ID of image stored in the Image service that should be used as the ramdisk
when booting an AMI-style image.</td>
<td>Valid image ID</td>
</tr>

2
doc/common/app_support.xml
View File

@ -263,7 +263,7 @@
<listitem>
<para><link
xlink:href="https://bugs.launchpad.net/glance"
>Bugs: OpenStack Image Service
>Bugs: OpenStack Image service
(glance)</link></para>
</listitem>
<listitem>

2
doc/common/ch_getstart.xml
View File

@ -126,7 +126,7 @@
<tr>
<td><link
xlink:href="http://www.openstack.org/software/openstack-shared-services/"
><glossterm>Image Service</glossterm></link>
><glossterm>Image service</glossterm></link>
</td>
<td><link
xlink:href="http://docs.openstack.org/developer/glance/"

8
doc/common/section_cli_glance_manage_images.xml
View File

@ -10,7 +10,7 @@
who can upload and manage images. The operator might restrict
image upload and management to only cloud administrators or
operators.</para>
<para>You can upload images through the <command>glance</command> client or the Image Service
<para>You can upload images through the <command>glance</command> client or the Image service
API. Besides, you can use the <command>nova</command> client for the image management.
The latter provides mechanisms to list and delete images, set and delete image metadata,
and create images of a running instance of snapshot and backup types.</para>
@ -101,7 +101,7 @@
</listitem>
</itemizedlist>
</para>
<para>After you restart the Image Service, you can use the following syntax to view the image's location information:</para>
<para>After you restart the Image service, you can use the following syntax to view the image's location information:</para>
<screen><prompt>$</prompt> <userinput>glance --os-image-api-version 2 image-show <replaceable>imageID</replaceable></userinput></screen>
<para>For example, using the image ID shown above, you would issue the command
as follows:</para>
@ -117,7 +117,7 @@
</para>
<para>The following table lists the optional arguments that you can use with the
<command>create</command> and <command>update</command> commands to modify image
properties. For more information, refer to Image Service chapter in the <link
properties. For more information, refer to Image service chapter in the <link
xlink:href="http://docs.openstack.org/cli-reference/content/index.html">OpenStack
Command-Line Interface Reference</link>.</para>
<informaltable>
@ -411,7 +411,7 @@
<xi:include href="section_cli_nova_manage_images.xml"/>
<section xml:id="troubleshoot">
<title>Troubleshoot image creation</title>
<para>If you encounter problems in creating an image in Image Service or Compute, the
<para>If you encounter problems in creating an image in Image service or Compute, the
following information may help you troubleshoot the creation process.</para>
<itemizedlist>
<listitem>

2
doc/common/section_cli_install.xml
View File

@ -178,7 +178,7 @@
and extensions</para>
</listitem>
<listitem>
<para><literal>glance</literal> - Image Service
<para><literal>glance</literal> - Image service
API</para>
</listitem>
<listitem>

2
doc/common/section_cli_nova_manage_images.xml
View File

@ -52,7 +52,7 @@
through the Block Storage service.</para>
</listitem>
<listitem>
<para>No data is uploaded to the Image Service.</para>
<para>No data is uploaded to the Image service.</para>
</listitem>
<listitem>
<para>You can find information about the snapshot in the properties of the

2
doc/common/section_cli_overview.xml
View File

@ -69,7 +69,7 @@
<td>Create and manage users, tenants, roles, endpoints, and credentials.</td>
</tr>
<tr>
<td>Image Service</td>
<td>Image service</td>
<td><command>glance</command></td>
<td><package>python-glanceclient</package></td>
<td>Create and manage images.</td>

4
doc/common/section_dashboard_launch_instances_from_image.xml
View File

@ -9,7 +9,7 @@
<para>Instances are virtual machines that run inside the
cloud.</para>
<para>You can launch an instance directly from one of the
available OpenStack images. The OpenStack Image Service
available OpenStack images. The OpenStack Image service
provides a pool of images that are accessible to members of
different projects. When you launch an instance from an image,
OpenStack creates a local copy of the image on the respective
@ -91,7 +91,7 @@
<para>Click the <guilabel>Images &amp; Snapshot</guilabel>
category.</para>
<para>The dashboard shows the images that have been
uploaded to OpenStack Image Service and are available
uploaded to OpenStack Image service and are available
for this project.</para>
</step>
<step>

6
doc/common/section_getstart_compute.xml
View File

@ -10,7 +10,7 @@
Infrastructure-as-a-Service (IaaS) system. The main modules are
implemented in Python.</para>
<para>OpenStack Compute interacts with OpenStack Identity for
authentication, OpenStack Image Service for disk and server
authentication, OpenStack Image service for disk and server
images, and OpenStack dashboard for the user and administrative
interface. Image access is limited by projects, and by users;
quotas are limited per project (the number of instances, for
@ -197,12 +197,12 @@
daemon</term>
<listitem>
<para>An S3 interface for registering images with the
OpenStack Image Service. Used primarily for installations
OpenStack Image service. Used primarily for installations
that must support euca2ools. The euca2ools tools talk to
<systemitem class="service">nova-objectstore</systemitem>
in <emphasis role="italic">S3 language</emphasis>, and
<systemitem class="service">nova-objectstore</systemitem>
translates S3 requests into Image Service requests.</para>
translates S3 requests into Image service requests.</para>
</listitem>
</varlistentry>
<varlistentry>

10
doc/common/section_getstart_image.xml
View File

@ -4,18 +4,18 @@
xmlns:xlink="http://www.w3.org/1999/xlink"
version="5.0"
xml:id="image-service-overview">
<title>OpenStack Image Service</title>
<para>The OpenStack Image Service is central to Infrastructure-as-a-Service (IaaS)
<title>OpenStack Image service</title>
<para>The OpenStack Image service is central to Infrastructure-as-a-Service (IaaS)
as shown in <xref linkend="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.
</para>
<para>A number of periodic processes run on the OpenStack Image Service to
<para>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.</para>
<para>The OpenStack Image Service includes the following
<para>The OpenStack Image service includes the following
components:</para>
<variablelist>
<varlistentry>
@ -29,7 +29,7 @@
images. Metadata includes items such as size and type.</para>
<note><title>Security note</title>
<para>The registry is a private internal service meant for use
by OpenStack Image Service. Do not disclose it to
by OpenStack Image service. Do not disclose it to
users.</para></note>
</listitem>
</varlistentry>

6
doc/common/section_keystone-concepts-user-management.xml
View File

@ -47,7 +47,7 @@
<screen><prompt>$</prompt> <userinput>openstack role create compute-user</userinput></screen>
<note>
<para>Individual services, such as Compute and the
Image Service, assign meaning to roles. In the
Image service, assign meaning to roles. In the
Identity Service, a role is simply a name.</para>
</note>
</listitem>
@ -87,11 +87,11 @@
<filename>/etc/nova/policy.json</filename> specifies the
access policy for the Compute service,
<filename>/etc/glance/policy.json</filename> specifies the
access policy for the Image Service, and
access policy for the Image service, and
<filename>/etc/keystone/policy.json</filename> specifies
the access policy for the Identity Service.</para>
<para>The default <filename>policy.json</filename> files in the
Compute, Identity, and Image Service recognize only the
Compute, Identity, and Image service recognize only the
<literal>admin</literal> role: all operations that do not
require the <literal>admin</literal> role are accessible by
any user that has any role in a tenant.</para>

2
doc/common/section_keystone-concepts.xml
View File

@ -88,7 +88,7 @@
<term>Service</term>
<listitem>
<para>An OpenStack service, such as Compute (nova),
Object Storage (swift), or Image Service (glance).
Object Storage (swift), or Image service (glance).
It provides one or more endpoints in which
users can access resources and perform operations.</para>
</listitem>

6
doc/common/section_objectstorage_tenant-specific-image-storage.xml
View File

@ -8,9 +8,9 @@
Storage</title>
<para>For some deployers, it is not ideal to store all images in
one place to enable all tenants and users to access them. You
can configure the Image Service to store image data in
can configure the Image service to store image data in
tenant-specific image locations. Then, only the following
tenants can use the Image Service to access the created image:<itemizedlist>
tenants can use the Image service to access the created image:<itemizedlist>
<listitem>
<para>The tenant who owns the image</para>
</listitem>
@ -41,7 +41,7 @@
Specify a list of tenant IDs that can
grant read and write access to all Object
Storage containers that are created by the
Image Service.</para>
Image service.</para>
</listitem>
</itemizedlist></para>
</step>

2
doc/common/section_storage-concepts.xml
View File

@ -71,7 +71,7 @@
easily and avoid a central point of failure.</para>
</listitem>
<listitem>
<para><emphasis>The OpenStack Image Service is used to manage
<para><emphasis>The OpenStack Image service is used to manage
the virtual machine images in an OpenStack cluster, not
store them.</emphasis> It provides an abstraction to different
methods for storage - a bridge to the storage, not the storage

2
doc/config-reference/ch_computeconfigure.xml
View File

@ -24,7 +24,7 @@
directory.</para>
</listitem>
<listitem>
<para>Related Image Service and Identity service management
<para>Related Image service and Identity service management
configuration files.</para>
</listitem>
</itemizedlist>

2
doc/config-reference/ch_config-overview.xml
View File

@ -19,7 +19,7 @@
<listitem><para>OpenStack Dashboard</para></listitem>
<listitem><para>Database service</para></listitem>
<listitem><para>OpenStack Identity</para></listitem>
<listitem><para>OpenStack Image Service</para></listitem>
<listitem><para>OpenStack Image service</para></listitem>
<listitem><para>OpenStack Networking</para></listitem>
<listitem><para>OpenStack Object Storage</para></listitem>
<listitem><para>Telemetry</para></listitem>

8
doc/config-reference/ch_imageservice.xml
View File

@ -4,11 +4,11 @@
xmlns:xlink="http://www.w3.org/1999/xlink"
version="5.0"
xml:id="ch_configuring-openstack-image-service">
<title>Image Service</title>
<title>Image service</title>
<para>Compute relies on an external image service to store virtual
machine images and maintain a catalog of available images. By
default, Compute is configured to use the OpenStack Image Service
(Glance), which is currently the only supported image
default, Compute is configured to use the OpenStack Image service
(glance), which is currently the only supported image
service.</para>
@ -21,7 +21,7 @@
settings documented in <xref linkend="config_table_nova_glance"/> and
<xref linkend="config_table_nova_s3"/>.</para>
<para>You can modify many options in the OpenStack Image Service.
<para>You can modify many options in the OpenStack Image service.
The following tables provide a comprehensive list.</para>
<xi:include href="../common/tables/glance-auth_token.xml"/>
<xi:include href="../common/tables/glance-common.xml"/>

2
doc/config-reference/compute/section_hypervisor_hyper-v.xml
View File

@ -97,7 +97,7 @@
<listitem>
<para>The target hosts checks if the image to be
migrated requires a base VHD and pulls it from the
Image Service if not already available on the target
Image service if not already available on the target
host.</para>
</listitem>
<listitem>

28
doc/config-reference/compute/section_hypervisor_vmware.xml
View File

@ -52,9 +52,9 @@
interacts with the vCenter APIs to select an appropriate ESX host within
the cluster. Internally, vCenter uses DRS for placement.</para>
<para>The VMware vCenter driver also interacts with the OpenStack
Image Service to copy VMDK images from the Image Service back
end store. The dotted line in the figure represents VMDK images
being copied from the OpenStack Image Service to the vSphere
Image service to copy VMDK images from the Image service back-end
store. The dotted line in the figure represents VMDK images
being copied from the OpenStack Image service to the vSphere
data store. VMDK images are cached in the data store so the copy
operation is only required the first time that the VMDK image is
used.</para>
@ -636,29 +636,29 @@ datastore_regex=&lt;optional datastore regex&gt;</programlisting>
environment. It is also possible to convert other formats, such
as qcow2, to the VMDK format using the <option>qemu-img</option>
utility. After a VMDK disk is available, load it into the
OpenStack Image Service. Then, you can use it with the VMware
OpenStack Image service. Then, you can use it with the VMware
vCenter driver. The following sections provide additional
details on the supported disks and the commands used for
conversion and upload.</para>
<section xml:id="VMware_supported_images">
<title>Supported image types</title>
<para>Upload images to the OpenStack Image Service in VMDK
<para>Upload images to the OpenStack Image service in VMDK
format. The following VMDK disk types are supported:</para>
<itemizedlist>
<listitem>
<para><emphasis role="italic">VMFS Flat Disks</emphasis>
(includes thin, thick, zeroedthick, and eagerzeroedthick).
Note that once a VMFS thin disk is exported from VMFS to a
non-VMFS location, like the OpenStack Image Service, it
non-VMFS location, like the OpenStack Image service, it
becomes a preallocated flat disk. This impacts the
transfer time from the OpenStack Image Service to the data
transfer time from the OpenStack Image service to the data
store when the full preallocated flat disk, rather than
the thin disk, must be transferred.</para>
</listitem>
<listitem>
<para><emphasis role="italic">Monolithic Sparse
disks</emphasis>. Sparse disks get imported from the
OpenStack Image Service into ESX as thin provisioned
OpenStack Image service into ESX as thin provisioned
disks. Monolithic Sparse disks can be obtained from VMware
Fusion or can be created by converting from other virtual
disk formats using the <code>qemu-img</code>
@ -669,7 +669,7 @@ datastore_regex=&lt;optional datastore regex&gt;</programlisting>
property that applies to each of the supported VMDK disk
types:</para>
<table rules="all">
<caption>OpenStack Image Service disk type settings</caption>
<caption>OpenStack Image service disk type settings</caption>
<thead>
<tr>
<th>vmware_disktype property</th>
@ -699,7 +699,7 @@ datastore_regex=&lt;optional datastore regex&gt;</programlisting>
</tbody>
</table>
<para>The <option>vmware_disktype</option> property is set when an
image is loaded into the OpenStack Image Service. For example,
image is loaded into the OpenStack Image service. For example,
the following command creates a Monolithic Sparse image by
setting <option>vmware_disktype</option> to
<literal>sparse</literal>:</para>
@ -794,7 +794,7 @@ trusty-server-cloudimg-amd64-disk1.vmdk</userinput></screen>
<para>To avoid the conversion step (at the cost of longer
download times) consider converting sparse disks to thin
provisioned or preallocated disks before loading them into the
OpenStack Image Service.</para>
OpenStack Image service.</para>
<para>Use one of the following tools to pre-convert sparse
disks.</para>
<variablelist>
@ -848,20 +848,20 @@ trusty-server-cloudimg-amd64-disk1.vmdk</userinput></screen>
<para>The ESX hypervisor requires a copy of the VMDK file in
order to boot up a virtual machine. As a result, the vCenter
OpenStack Compute driver must download the VMDK via HTTP from
the OpenStack Image Service to a data store that is visible to
the OpenStack Image service to a data store that is visible to
the hypervisor. To optimize this process, the first time a
VMDK file is used, it gets cached in the data store.
A cached image is stored in a folder named after the image ID.
Subsequent virtual machines that need the VMDK use the cached
version and don't have to copy the file again from the
OpenStack Image Service.</para>
OpenStack Image service.</para>
<para>Even with a cached VMDK, there is still a copy operation
from the cache location to the hypervisor file directory in
the shared data store. To avoid this copy, boot the image in
linked_clone mode. To learn how to enable this mode, see <xref linkend="VMware_config"/>.</para>
<note><para>You can also use
the <code>vmware_linked_clone</code> property in the OpenStack
Image Service to
Image service to
override the linked_clone mode on a per-image basis.</para></note>
<para>If multiple compute nodes are running on the same host,

2
doc/config-reference/compute/section_introduction-to-xen.xml
View File

@ -177,7 +177,7 @@
communication. Please note that the VM
images are downloaded by the XenAPI
plug-ins, so make sure that the OpenStack
Image Service is accessible through this
Image service is accessible through this
network. It usually means binding those
services to the management interface.
</para>

2
doc/config-reference/compute/section_nova-conf.xml
View File

@ -76,7 +76,7 @@
<term><literal>[glance]</literal></term>
<listitem>
<para>
Configures how to access the Image Service.
Configures how to access the Image service.
</para>
</listitem>
</varlistentry>

8
doc/config-reference/image-service/section_image-service-ISO-support.xml
View File

@ -5,24 +5,24 @@
version="5.0"
xml:id="iso-support">
<title>Support for ISO images</title>
<para>You can load ISO images into the Image Service. You can
<para>You can load ISO images into the Image service. You can
subsequently boot an ISO image using Compute.</para>
<procedure>
<title>To load an ISO image to an Image Service data
<title>To load an ISO image to an Image service data
store</title>
<step>
<para>Obtain the ISO image. For example,
<filename>ubuntu-13.04-server-amd64.iso</filename>.</para>
</step>
<step>
<para>In the Image Service, run the following
<para>In the Image service, run the following
command:</para>
<screen><prompt>$</prompt> <userinput>glance image-create --name ubuntu.iso \
--is-public True --container-format bare \
--disk-format iso &lt; ubuntu-13.04-server-amd64.iso</userinput></screen>
<para>In this command, <literal>ubuntu.iso</literal> is
the name for the ISO image after it is loaded to the
Image Service, and
Image service, and
<literal>ubuntu-13.04-server-amd64.iso</literal>
is the name of the source ISO image.</para>
</step>

2
doc/config-reference/image-service/section_image-service-api.xml
View File

@ -4,7 +4,7 @@
version="5.0"
xml:id="image-configuring-api">
<title>Configure the API</title>
<para>The Image Service has two APIs: the user-facing API, and
<para>The Image service has two APIs: the user-facing API, and
the registry API, which is for internal requests that require
access to the database.</para>
<para>Both of the APIs currently have two major versions, v1 and v2.

6
doc/config-reference/image-service/section_image-service-backend-vmware.xml
View File

@ -4,10 +4,10 @@
xmlns:xlink="http://www.w3.org/1999/xlink"
version="5.0"
xml:id="vmware-glance-backend">
<title>Configure vCenter data stores for the Image Service back
<title>Configure vCenter data stores for the Image service back
end</title>
<?dbhtml stop-chunking?>
<para>To use vCenter data stores for the Image Service back end,
<para>To use vCenter data stores for the Image service back end,
you must update the <filename>glance-api.conf</filename> file,
as follows:</para>
<itemizedlist>
@ -20,7 +20,7 @@
</listitem>
</itemizedlist>
<note>
<para>You must configure any configured Image Service data
<para>You must configure any configured Image service data
stores for the Compute service.</para>
</note>
<para>You can specify vCenter data stores directly by using the

2
doc/config-reference/image-service/section_image-service-backends.xml
View File

@ -5,7 +5,7 @@
version="5.0"
xml:id="configuring-image-service-backends">
<title>Configure back ends</title>
<para>The Image Service supports several back ends for storing
<para>The Image service supports several back ends for storing
virtual machine images:<itemizedlist>
<listitem>
<para>OpenStack Block Storage (cinder)</para>

2
doc/config-reference/image-service/section_image-service-rpc.xml
View File

@ -12,7 +12,7 @@
<application>Qpid</application>, and
<application>ZeroMQ</application>.</para>
<para>The following tables contain settings to configure the
messaging middleware for the Image Service:</para>
messaging middleware for the Image service:</para>
<xi:include href="../../common/tables/glance-zeromq.xml"/>
<xi:include href="../../common/tables/glance-amqp.xml"/>
<xi:include href="../../common/tables/glance-rpc.xml"/>

16
doc/config-reference/image-service/section_image-service-sample-configuration-files.xml
View File

@ -3,20 +3,20 @@
xmlns:xlink="http://www.w3.org/1999/xlink"
version="5.0"
xml:id="section_image-service-sample-configuration-files">
<title>Image Service sample configuration files</title>
<title>Image service sample configuration files</title>
<para>You can find the files that are described in this section in
the <filename class="directory">/etc/glance/</filename>
directory.</para>
<section xml:id="section_glance-api.conf">
<title>glance-api.conf</title>
<para>The configuration file for the Image Service API is found in the
<para>The configuration file for the Image service API is found in the
<filename>glance-api.conf</filename> file.</para>
<para>This file must be modified after installation.</para>
<programlisting language="ini"><xi:include parse="text" href="http://git.openstack.org/cgit/openstack/glance/plain/etc/glance-api.conf?h=stable/juno"/></programlisting>
</section>
<section xml:id="section_glance-registry.conf">
<title>glance-registry.conf</title>
<para>Configuration for the Image Service's registry, which
<para>Configuration for the Image service's registry, which
stores the metadata about images, is found in the
<filename>glance-registry.conf</filename> file.</para>
<para>This file must be modified after installation.</para>
@ -24,14 +24,14 @@
</section>
<section xml:id="section_glance-api-paste.conf">
<title>glance-api-paste.ini</title>
<para>Configuration for the Image Service's API middleware pipeline is found in the
<para>Configuration for the Image service's API middleware pipeline is found in the
<filename>glance-api-paste.ini</filename> file.</para>
<para>You should not need to modify this file.</para>
<programlisting language="ini"><xi:include parse="text" href="http://git.openstack.org/cgit/openstack/glance/plain/etc/glance-api-paste.ini?h=stable/juno"/></programlisting>
</section>
<section xml:id="section_glance-manage.conf">
<title>glance-manage.conf</title>
<para>The Image Service's custom logging options are found in the
<para>The Image service's custom logging options are found in the
<filename>glance-manage.conf</filename> file.</para>
<note><para>Options set in <filename>glance-manage.conf</filename>
will override options of the same section and name set in
@ -42,13 +42,13 @@
</section>
<section xml:id="section_glance-registry-paste.conf">
<title>glance-registry-paste.ini</title>
<para>The Image Service's middleware pipeline for its registry is found in the
<para>The Image service's middleware pipeline for its registry is found in the
<filename>glance-registry-paste.ini</filename> file.</para>
<programlisting language="ini"><xi:include parse="text" href="http://git.openstack.org/cgit/openstack/glance/plain/etc/glance-registry-paste.ini?h=stable/juno"/></programlisting>
</section>
<section xml:id="section_glance-scrubber.conf">
<title>glance-scrubber.conf</title>
<para><command>glance-scrubber</command> is a utility for the Image Service that cleans
<para><command>glance-scrubber</command> is a utility for the Image service that cleans
up images that have been deleted; its configuration is stored in the
<filename>glance-scrubber.conf</filename> file.</para>
<para>Multiple instances of <systemitem>glance-scrubber</systemitem> can be run in a single
@ -63,7 +63,7 @@
<section xml:id="section_glance-policy.json">
<title>policy.json</title>
<para>The <filename>/etc/glance/policy.json</filename> file defines additional access controls
that apply to the Image Service.</para>
that apply to the Image service.</para>
<programlisting language="json"><xi:include parse="text" href="http://git.openstack.org/cgit/openstack/glance/plain/etc/policy.json?h=stable/juno"/></programlisting>
</section>
</section>

4
doc/config-reference/table_default-ports-primary-services.xml
View File

@ -71,12 +71,12 @@
<td>publicurl</td>
</tr>
<tr>
<td>Image Service (<literal>glance</literal>) API</td>
<td>Image service (<literal>glance</literal>) API</td>
<td>9292</td>
<td>publicurl and adminurl</td>
</tr>
<tr>
<td>Image Service registry</td>
<td>Image service registry</td>
<td>9191</td>
<td/>
</tr>

98
doc/glossary/glossary-terms.xml
View File

@ -911,7 +911,7 @@
<para>The persistent data store used to save and retrieve information
for a service, such as lists of Object Storage objects, current state
of guest VMs, lists of user names, and so on. Also, the method that the
Image Service uses to get and store VM images. Options include Object
Image service uses to get and store VM images. Options include Object
Storage, local file system, S3, and HTTP.</para>
</glossdef>
</glossentry>
@ -950,7 +950,7 @@
</indexterm>
<glossdef>
<para>An Image Service container format that indicates that no
<para>An Image service container format that indicates that no
container exists for the VM image.</para>
</glossdef>
</glossentry>
@ -1256,7 +1256,7 @@
</indexterm>
<glossdef>
<para>A program that keeps the Image Service VM image cache at or
<para>A program that keeps the Image service VM image cache at or
below its configured maximum size.</para>
</glossdef>
</glossentry>
@ -1270,7 +1270,7 @@
<glossdef>
<para>An OpenStack grouped release of projects that came out in the
spring of 2011. It included Compute (nova), Object Storage (swift),
and the Image Service (glance).</para>
and the Image service (glance).</para>
<para>Cactus is a city in Texas, US and is the code name for
the third release of OpenStack. When OpenStack releases went
from three to six months long, the code name of the release
@ -1788,7 +1788,7 @@
<para>Reducing the size of files by special encoding, the file can be
decompressed again to its original content. OpenStack supports
compression at the Linux file system level but does not support
compression for things such as Object Storage objects or Image Service
compression for things such as Object Storage objects or Image service
VM images.</para>
</glossdef>
</glossentry>
@ -1959,7 +1959,7 @@
<glossdef>
<para>Organizes and stores objects in Object Storage. Similar to the
concept of a Linux directory but cannot be nested. Alternative term
for an Image Service container format.</para>
for an Image service container format.</para>
</glossdef>
</glossentry>
@ -2002,7 +2002,7 @@
</indexterm>
<glossdef>
<para>A wrapper used by the Image Service that contains a VM image and
<para>A wrapper used by the Image service that contains a VM image and
its associated metadata, such as machine state, OS disk size, and so
on.</para>
</glossdef>
@ -2073,7 +2073,7 @@
<glossdef>
<para>Depending on context, the core API is either the OpenStack API
or the main API of a specific core project, such as Compute,
Networking, Image Service, and so on.</para>
Networking, Image service, and so on.</para>
</glossdef>
</glossentry>
@ -2085,7 +2085,7 @@
<glossdef>
<para>An official OpenStack project. Currently consists of Compute
(nova), Object Storage (swift), Image Service (glance), Identity
(nova), Object Storage (swift), Image service (glance), Identity
(keystone), Dashboard (horizon), Networking (neutron), and Block
Storage (cinder). The Telemetry module (ceilometer) and Orchestration
module (heat) are integrated projects as of the Havana release. In the
@ -2240,7 +2240,7 @@
</indexterm>
<glossdef>
<para>Both Image Service and Compute support encrypted virtual machine
<para>Both Image service and Compute support encrypted virtual machine
(VM) images (but not instances). In-transit data encryption is
supported in OpenStack using technologies such as HTTPS, SSL, TLS, and
SSH. Object Storage does not support object encryption at the
@ -2388,7 +2388,7 @@
</indexterm>
<glossdef>
<para>An option within Image Service so that an image is deleted after
<para>An option within Image service so that an image is deleted after
a predefined number of seconds instead of immediately.</para>
</glossdef>
</glossentry>
@ -2630,7 +2630,7 @@
<glossdef>
<para>The underlying format that a disk image for a VM is stored as
within the Image Service back-end store. For example, AMI, ISO, QCOW2,
within the Image service back-end store. For example, AMI, ISO, QCOW2,
VMDK, and so on.</para>
</glossdef>
</glossentry>
@ -3165,7 +3165,7 @@
</indexterm>
<glossdef>
<para>VM image container format supported by Image Service.</para>
<para>VM image container format supported by Image service.</para>
</glossdef>
</glossentry>
@ -3504,7 +3504,7 @@
</indexterm>
<glossdef>
<para>UUID for each Compute or Image Service VM flavor or instance
<para>UUID for each Compute or Image service VM flavor or instance
type.</para>
</glossdef>
</glossentry>
@ -3539,7 +3539,7 @@
<para>A grouped release of projects related to OpenStack that came out
in the fall of 2012, the sixth release of OpenStack. It includes
Compute (nova), Object Storage (swift), Identity (keystone),
Networking (neutron), Image Service (glance), and Volumes or Block
Networking (neutron), Image service (glance), and Volumes or Block
Storage (cinder).</para>
<para>Folsom is the code name for the sixth release of
OpenStack. The design summit took place in
@ -3618,7 +3618,7 @@
<glossterm>glance</glossterm>
<glossdef>
<para>A core project that provides the OpenStack Image Service.</para>
<para>A core project that provides the OpenStack Image service.</para>
</glossdef>
</glossentry>
@ -3631,7 +3631,7 @@
</indexterm>
<glossdef>
<para>Processes client requests for VMs, updates Image Service
<para>Processes client requests for VMs, updates Image service
metadata on the registry server, and communicates with the store
adapter to upload VM images from the back-end store.</para>
</glossdef>
@ -3646,7 +3646,7 @@
</indexterm>
<glossdef>
<para>Alternative term for the Image Service image registry.</para>
<para>Alternative term for the Image service image registry.</para>
</glossdef>
</glossentry>
@ -4209,13 +4209,13 @@
<glossentry>
<glossterm>Image API</glossterm>
<indexterm class="singular">
<primary>Image Service</primary>
<primary>Image service</primary>
<secondary>Image Service API</secondary>
<secondary>Image service API</secondary>
</indexterm>
<glossdef>
<para>The Image Service API endpoint for management of VM
<para>The Image service API endpoint for management of VM
images.</para>
</glossdef>
</glossentry>
@ -4223,13 +4223,13 @@
<glossentry>
<glossterm>image cache</glossterm>
<indexterm class="singular">
<primary>Image Service</primary>
<primary>Image service</primary>
<secondary>image cache</secondary>
</indexterm>
<glossdef>
<para>Used by Image Service to obtain images on the local host rather
<para>Used by Image service to obtain images on the local host rather
than re-downloading them from the image server each time one is
requested.</para>
</glossdef>
@ -4244,7 +4244,7 @@
</indexterm>
<glossdef>
<para>Combination of a URI and UUID used to access Image Service VM
<para>Combination of a URI and UUID used to access Image service VM
images through the image API.</para>
</glossdef>
</glossentry>
@ -4252,7 +4252,7 @@
<glossentry>
<glossterm>image membership</glossterm>
<indexterm class="singular">
<primary>Image Service</primary>
<primary>Image service</primary>
<secondary>image membership</secondary>
</indexterm>
@ -4266,13 +4266,13 @@
<glossentry>
<glossterm>image owner</glossterm>
<indexterm class="singular">
<primary>Image Service</primary>
<primary>Image service</primary>
<secondary>image owner</secondary>
</indexterm>
<glossdef>
<para>The tenant who owns an Image Service virtual machine
<para>The tenant who owns an Image service virtual machine
image.</para>
</glossdef>
</glossentry>
@ -4280,7 +4280,7 @@
<glossentry>
<glossterm>image registry</glossterm>
<indexterm class="singular">
<primary>Image Service</primary>
<primary>Image service</primary>
<secondary>image registry</secondary>
</indexterm>
@ -4292,17 +4292,17 @@
</glossentry>
<glossentry>
<glossterm>Image Service</glossterm>
<glossterm>Image service</glossterm>
<glossdef>
<para>An OpenStack core project that provides discovery, registration,
and delivery services for disk and server images. The project name of
the Image Service is glance.</para>
the Image service is glance.</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>Image Service API</glossterm>
<glossterm>Image service API</glossterm>
<glossdef>
<para>Alternative name for the glance image API.</para>
@ -4312,13 +4312,13 @@
<glossentry>
<glossterm>image status</glossterm>
<indexterm class="singular">
<primary>Image Service</primary>
<primary>Image service</primary>
<secondary>image status</secondary>
</indexterm>
<glossdef>
<para>The current status of a VM image in Image Service, not to be
<para>The current status of a VM image in Image service, not to be
confused with the status of a running instance.</para>
</glossdef>
</glossentry>
@ -4326,13 +4326,13 @@
<glossentry>
<glossterm>image store</glossterm>
<indexterm class="singular">
<primary>Image Service</primary>
<primary>Image service</primary>
<secondary>image store</secondary>
</indexterm>
<glossdef>
<para>The back-end store used by Image Service to store VM images,
<para>The back-end store used by Image service to store VM images,
options include Object Storage, local file system, S3, or HTTP.</para>
</glossdef>
</glossentry>
@ -4340,13 +4340,13 @@
<glossentry>
<glossterm>image UUID</glossterm>
<indexterm class="singular">
<primary>Image Service</primary>
<primary>Image service</primary>
<secondary>image UUID</secondary>
</indexterm>
<glossdef>
<para>UUID used by Image Service to uniquely identify each VM
<para>UUID used by Image service to uniquely identify each VM
image.</para>
</glossdef>
</glossentry>
@ -4698,7 +4698,7 @@
<glossdef>
<para>The SCSI disk protocol tunneled within Ethernet, supported by
Compute, Object Storage, and Image Service.</para>
Compute, Object Storage, and Image service.</para>
</glossdef>
</glossentry>
@ -5237,7 +5237,7 @@
</indexterm>
<glossdef>
<para>The association between an Image Service VM image and a tenant.
<para>The association between an Image service VM image and a tenant.
Enables images to be shared with specified tenants.</para>
</glossdef>
</glossentry>
@ -6496,7 +6496,7 @@
</indexterm>
<glossdef>
<para>An Image Service VM image that is only available to specified
<para>An Image service VM image that is only available to specified
tenants.</para>
</glossdef>
</glossentry>
@ -6602,7 +6602,7 @@
</indexterm>
<glossdef>
<para>Generally, extra properties on an Image Service image to
<para>Generally, extra properties on an Image service image to
which only cloud administrators have access. Limits which user
roles can perform CRUD operations on that property. The cloud
administrator can configure any image property as
@ -6676,7 +6676,7 @@
<glossentry>
<glossterm>public image</glossterm>
<indexterm class="singular">
<primary>Image Service</primary>
<primary>Image service</primary>
<secondary>public images</secondary>
</indexterm>
@ -6685,7 +6685,7 @@
</indexterm>
<glossdef>
<para>An Image Service VM image that is available to all
<para>An Image service VM image that is available to all
tenants.</para>
</glossdef>
</glossentry>
@ -6930,7 +6930,7 @@
</indexterm>
<glossdef>
<para>One of the VM image disk formats supported by Image Service; an
<para>One of the VM image disk formats supported by Image service; an
unstructured disk image.</para>
</glossdef>
</glossentry>
@ -7062,11 +7062,11 @@
<indexterm class="singular">
<primary>registry</primary>
<see>under Image Service</see>
<see>under Image service</see>
</indexterm>
<glossdef>
<para>Alternative term for the Image Service registry.</para>
<para>Alternative term for the Image service registry.</para>
</glossdef>
</glossentry>
@ -7082,7 +7082,7 @@
</indexterm>
<glossdef>
<para>An Image Service that provides VM image metadata information to
<para>An Image service that provides VM image metadata information to
clients.</para>
</glossdef>
</glossentry>
@ -7406,7 +7406,7 @@
<glossdef>
<para>Object storage service by Amazon; similar in function to Object
Storage, it can act as a back-end store for Image Service VM <phrase
Storage, it can act as a back-end store for Image service VM <phrase
role="keep-together">images</phrase>.</para>
</glossdef>
</glossentry>
@ -8047,7 +8047,7 @@
</indexterm>
<glossdef>
<para>Specifies the authentication source used by Image Service or
<para>Specifies the authentication source used by Image service or
Identity Service.</para>
</glossdef>
</glossentry>

2
doc/image-guide/ch_modifying_images.xml
View File

@ -12,7 +12,7 @@
<?dbhtml stop-chunking?>
<para>Once you have obtained a virtual machine image, you may want
to make some changes to it before uploading it to the
OpenStack Image Service. Here we describe several tools
OpenStack Image service. Here we describe several tools
available that allow you to modify images.<warning>
<para>Do not attempt to use these tools to modify an image
that is attached to a running virtual machine. These

4
doc/image-guide/section_centos-example.xml
View File

@ -317,7 +317,7 @@ kernel <replaceable>...</replaceable> console=tty0 console=ttyS0,115200n8</progr
</simplesect>
<simplesect>
<title>Undefine the libvirt domain</title>
<para>Now that you can upload the image to the Image Service, you no longer need to have
<para>Now that you can upload the image to the Image service, you no longer need to have
this virtual machine image managed by libvirt. Use the <command>virsh undefine
<replaceable>vm-image</replaceable></command> command to inform libvirt:</para>
<screen><prompt>#</prompt> <userinput>virsh undefine centos-6.4</userinput></screen>
@ -326,6 +326,6 @@ kernel <replaceable>...</replaceable> console=tty0 console=ttyS0,115200n8</progr
<title>Image is complete</title>
<para>The underlying image file that you created with <command>qemu-img create</command> is
ready to be uploaded. For example, you can upload the
<filename>/tmp/centos-6.4.qcow2</filename> image to the Image Service.</para>
<filename>/tmp/centos-6.4.qcow2</filename> image to the Image service.</para>
</simplesect>
</section>

2
doc/image-guide/section_fedora-example.xml
View File

@ -165,5 +165,5 @@ kernel ... console=tty0 console=ttyS0,115200n8</programlisting></step>
<screen><prompt>#</prompt> <userinput>virsh undefine fedora-20</userinput></screen></step>
</procedure>
<para>The underlying image file that you created with qemu-img create is
ready to be uploaded to the Image Service.</para>
ready to be uploaded to the Image service.</para>
</section>

4
doc/image-guide/section_glance-image-metadata.xml
View File

@ -7,7 +7,7 @@
<title>Image metadata</title>
<?dbhtml stop-chunking?>
<para>Image metadata can help end users determine the nature of an image, and is used by
associated OpenStack components and drivers which interface with the Image Service.</para>
associated OpenStack components and drivers which interface with the Image service.</para>
<para>Metadata can also determine the scheduling of hosts. If the <option>property</option> option
is set on an image, and Compute is configured so that the
<systemitem>ImagePropertiesFilter</systemitem> scheduler filter is enabled (default), then the
@ -15,7 +15,7 @@
<note><para>Compute's <systemitem>ImagePropertiesFilter</systemitem> value is specified in the
<option>scheduler_default_filter</option> value in the
<filename>/etc/nova/nova.conf</filename> file.</para></note>
<para>You can add metadata to Image Service images by using the <parameter>--property
<para>You can add metadata to Image service images by using the <parameter>--property
<replaceable>key</replaceable>=<replaceable>value</replaceable></parameter> option with the
<command>glance image-create</command> or <command>glance image-update</command> command. More
than one property can be specified. For example:</para>

4
doc/image-guide/section_glance_image-formats.xml
View File

@ -6,7 +6,7 @@
xml:id="image-formats">
<title>Disk and container formats for images</title>
<?dbhtml stop-chunking?>
<para>When you add an image to the Image Service, you can specify
<para>When you add an image to the Image service, you can specify
its disk and container formats.</para>
<section xml:id="disk-format">
<title>Disk formats</title>
@ -68,7 +68,7 @@
machine image is in a file format that also contains
metadata about the actual virtual machine.</para>
<note>
<para>The Image Service and other OpenStack projects do
<para>The Image service and other OpenStack projects do
not currently support the container format. It is safe
to specify <literal>bare</literal> as the container
format if you are unsure.</para>

4
doc/image-guide/section_ubuntu-example.xml
View File

@ -192,7 +192,7 @@
</simplesect>
<simplesect>
<title>Undefine the libvirt domain</title>
<para>Now that the image is ready to be uploaded to the Image Service, you no longer need to
<para>Now that the image is ready to be uploaded to the Image service, you no longer need to
have this virtual machine image managed by libvirt. Use the <command>virsh undefine
<replaceable>vm-image</replaceable></command> command to inform libvirt:</para>
<screen><prompt>#</prompt> <userinput>virsh undefine trusty</userinput></screen>
@ -201,6 +201,6 @@
<title>Image is complete</title>
<para>The underlying image file that you created with <command>qemu-img create</command>,
such as <filename>/tmp/trusty.qcow2</filename>, is now ready for uploading to the
OpenStack Image Service.</para>
OpenStack Image service.</para>
</simplesect>
</section>

2
doc/image-guide/section_windows-example.xml
View File

@ -98,7 +98,7 @@
</step>
</procedure>
<para>Your image is ready to upload to the Image Service:</para>
<para>Your image is ready to upload to the Image service:</para>
<screen><prompt>$</prompt> <userinput>glance image-create --name WS2012 --disk-format qcow2 \
--container-format bare --is-public true \
--file ws2012.qcow2</userinput></screen>

4
doc/install-guide/ch_basic_environment.xml
View File

@ -24,13 +24,13 @@
<link linkend="example-architecture-with-neutron-networking-hw">three-node
architecture with OpenStack Networking (neutron)</link>.</para>
<note>
<para>Although most environments include Identity, Image Service,
<para>Although most environments include Identity, Image service,
Compute, at least one networking service, and the dashboard, the
Object Storage service can operate independently. If your use case
only involves Object Storage, you can skip to
<xref linkend="ch_swift"/> after configuring the appropriate nodes
for it. However, the dashboard requires at least
the Image Service and Compute.</para>
the Image service and Compute.</para>
</note>
<note>
<para>You must use an account with administrative privileges to configure

10
doc/install-guide/ch_glance.xml
View File

@ -4,18 +4,18 @@
xmlns:xlink="http://www.w3.org/1999/xlink"
version="5.0"
xml:id="ch_glance">
<title>Add the Image Service</title>
<para>The OpenStack Image Service (glance) enables users to discover,
<title>Add the Image service</title>
<para>The OpenStack Image service (glance) enables users to discover,
register, and retrieve virtual machine images. It offers a <glossterm
baseform="RESTful">REST</glossterm> API that enables you to
query virtual machine image metadata and retrieve an actual image.
You can store virtual machine images made available through the
Image Service in a variety of locations, from simple file systems
Image service in a variety of locations, from simple file systems
to object-storage systems like OpenStack Object Storage.</para>
<important>
<para>For simplicity, this guide describes configuring the Image Service to
<para>For simplicity, this guide describes configuring the Image service to
use the <literal>file</literal> back end, which uploads and stores in a
directory on the controller node hosting the Image Service. By
directory on the controller node hosting the Image service. By
default, this directory is <filename>/var/lib/glance/images/</filename>.
</para>
<para>Before you proceed, ensure that the controller node has at least

2
doc/install-guide/ch_overview.xml
View File

@ -168,7 +168,7 @@
<para>The
<glossterm baseform="cloud controller node"
>controller node</glossterm> runs the Identity service,
Image Service, management portion of Compute, and the
Image service, management portion of Compute, and the
dashboard. It also includes supporting services such as
a SQL database, <glossterm>message queue</glossterm>, and
<glossterm>Network Time Protocol (NTP)</glossterm>.</para>

4
doc/install-guide/section_basics-security.xml
View File

@ -66,11 +66,11 @@
</tr>
<tr>
<td><literal><replaceable>GLANCE_DBPASS</replaceable></literal></td>
<td>Database password for Image Service</td>
<td>Database password for Image service</td>
</tr>
<tr>
<td><literal><replaceable>GLANCE_PASS</replaceable></literal></td>
<td>Password of Image Service user <literal>glance</literal></td>
<td>Password of Image service user <literal>glance</literal></td>
</tr>
<tr>
<td><literal><replaceable>HEAT_DBPASS</replaceable></literal></td>

6
doc/install-guide/section_ceilometer-glance.xml
View File

@ -4,9 +4,9 @@
xmlns:xlink="http://www.w3.org/1999/xlink"
version="5.0"
xml:id="ceilometer-glance">
<title>Configure the Image Service</title>
<title>Configure the Image service</title>
<para>To retrieve image-oriented events and samples, configure
the Image Service to send notifications to the message bus.
the Image service to send notifications to the message bus.
Perform these steps on the controller node.</para>
<procedure>
<para>Edit the <filename>/etc/glance/glance-api.conf</filename>
@ -26,7 +26,7 @@ rabbit_password = <replaceable>RABBIT_PASS</replaceable></programlisting>
<application>RabbitMQ</application>.</para>
</step>
<step>
<para>Restart the Image Service:</para>
<para>Restart the Image service:</para>
<screen os="ubuntu;debian"><prompt>#</prompt> <userinput>service glance-registry restart</userinput>
<prompt>#</prompt> <userinput>service glance-api restart</userinput></screen>
<screen os="rhel;centos;fedora;opensuse;sles"><prompt>#</prompt> <userinput>systemctl restart openstack-glance-api.service openstack-glance-registry.service</userinput></screen>

2
doc/install-guide/section_ceilometer-verify.xml
View File

@ -31,7 +31,7 @@
</note>
</step>
<step>
<para>Download an image from the Image Service:</para>
<para>Download an image from the Image service:</para>
<screen><prompt>$</prompt> <userinput>glance image-download "cirros-0.3.3-x86_64" > cirros.img</userinput></screen>
</step>
<step>

2
doc/install-guide/section_cinder-storage-node.xml
View File

@ -200,7 +200,7 @@ my_ip = <replaceable>MANAGEMENT_INTERFACE_IP_ADDRESS</replaceable></programlisti
</step>
<step>
<para>In the <literal>[DEFAULT]</literal> section, configure the
location of the Image Service:</para>
location of the Image service:</para>
<programlisting language="ini">[DEFAULT]
...
glance_host = <replaceable>controller</replaceable></programlisting>

2
doc/install-guide/section_dashboard-install.xml
View File

@ -10,7 +10,7 @@
on the controller node.</para>
<para>Before you proceed, verify that your system meets the requirements
in <xref linkend="dashboard-system-requirements"/>. Also, the dashboard
relies on functional core services including Identity, Image Service,
relies on functional core services including Identity, Image service,
Compute, and either Networking (neutron) or legacy networking
(nova-network). Environments with stand-alone services such as Object
Storage cannot use the dashboard. For more information, see the

2
doc/install-guide/section_debconf-concepts.xml
View File

@ -61,7 +61,7 @@
files. For example, the <literal>glance-common</literal> package
installs the <filename>glance-api.conf</filename> and
<filename>glance-registry.conf</filename> files. So, for the
Image Service, you must re-configure the
Image service, you must re-configure the
<literal>glance-common</literal> package. The same applies for
<literal>cinder-common</literal>,
<literal>nova-common</literal>, and

2
doc/install-guide/section_debconf-keystone_authtoken.xml
View File

@ -22,7 +22,7 @@ admin_password = %SERVICE_PASSWORD%</programlisting>
<code>auth_uri</code>, <code>identity_uri</code>,
<code>admin_tenant_name</code>, <code>admin_user</code> and
<code>admin_password</code> options.</para>
<para>The following screens show an example Image Service
<para>The following screens show an example Image service
configuration:</para>
<informalfigure>
<mediaobject>

30
doc/install-guide/section_glance-install.xml
View File

@ -5,7 +5,7 @@
version="5.0"
xml:id="glance-install">
<title>Install and configure</title>
<para>This section describes how to install and configure the Image Service,
<para>This section describes how to install and configure the Image service,
code-named glance, on the controller node. For simplicity, this
configuration stores images on the local file system.</para>
<note>
@ -16,7 +16,7 @@
</note>
<procedure os="ubuntu;rhel;centos;fedora;sles;opensuse">
<title>To configure prerequisites</title>
<para>Before you install and configure the Image Service, you must
<para>Before you install and configure the Image service, you must
create a database, service credentials, and API endpoints.</para>
<step>
<para>To create the database, complete these steps:</para>
@ -83,11 +83,11 @@ Repeat User Password:
<step>
<para>Create the <literal>glance</literal> service entity:</para>
<screen><prompt>$</prompt> <userinput>openstack service create --type image \
--description "OpenStack Image Service" glance</userinput>
--description "OpenStack Image service" glance</userinput>
<computeroutput>+-------------+----------------------------------+
| Field | Value |
+-------------+----------------------------------+
| description | OpenStack Image Service |
| description | OpenStack Image service |
| enabled | True |
| id | 178124d6081c441b80d79972614149c6 |
| name | glance |
@ -97,7 +97,7 @@ Repeat User Password:
</substeps>
</step>
<step>
<para>Create the Image Service API endpoints:</para>
<para>Create the Image service API endpoints:</para>
<screen><prompt>$</prompt> <userinput>openstack endpoint create \
--publicurl http://<replaceable>controller</replaceable>:9292 \
--internalurl http://<replaceable>controller</replaceable>:9292 \
@ -119,7 +119,7 @@ Repeat User Password:
</step>
</procedure>
<procedure os="ubuntu;rhel;centos;fedora;sles;opensuse">
<title>To install and configure the Image Service components</title>
<title>To install and configure the Image service components</title>
<note>
<para>Default configuration files vary by distribution. You might need
to add these sections and options rather than modifying existing
@ -144,7 +144,7 @@ Repeat User Password:
...
connection = mysql://glance:<replaceable>GLANCE_DBPASS</replaceable>@<replaceable>controller</replaceable>/glance</programlisting>
<para>Replace <replaceable>GLANCE_DBPASS</replaceable> with the
password you chose for the Image Service database.</para>
password you chose for the Image service database.</para>
</step>
<step>
<para>In the <literal>[keystone_authtoken]</literal> and
@ -188,7 +188,7 @@ filesystem_store_datadir = /var/lib/glance/images/</programlisting>
<programlisting language="ini">[DEFAULT]
...
notification_driver = noop</programlisting>
<para>The Telemetry chapter provides an Image Service configuration
<para>The Telemetry chapter provides an Image service configuration
that enables notifications.</para>
</step>
<step>
@ -212,7 +212,7 @@ verbose = True</programlisting>
...
connection = mysql://glance:<replaceable>GLANCE_DBPASS</replaceable>@<replaceable>controller</replaceable>/glance</programlisting>
<para>Replace <replaceable>GLANCE_DBPASS</replaceable> with the
password you chose for the Image Service database.</para>
password you chose for the Image service database.</para>
</step>
<step>
<para>In the <literal>[keystone_authtoken]</literal> and
@ -248,7 +248,7 @@ flavor = keystone</programlisting>
<programlisting language="ini">[DEFAULT]
...
notification_driver = noop</programlisting>
<para>The Telemetry chapter provides an Image Service configuration
<para>The Telemetry chapter provides an Image service configuration
that enables notifications.</para>
</step>
<step>
@ -262,12 +262,12 @@ verbose = True</programlisting>
</substeps>
</step>
<step os="rhel;centos;fedora;ubuntu">
<para>Populate the Image Service database:</para>
<para>Populate the Image service database:</para>
<screen><prompt>#</prompt> <userinput>su -s /bin/sh -c "glance-manage db_sync" glance</userinput></screen>
</step>
</procedure>
<procedure os="debian">
<title>To install and configure the Image Service components</title>
<title>To install and configure the Image service components</title>
<step>
<para>Install the packages:</para>
<screen><prompt>#</prompt> <userinput>apt-get install glance python-glanceclient</userinput></screen>
@ -284,7 +284,7 @@ verbose = True</programlisting>
</step>
<step>
<para>Select the <literal>keystone</literal> pipeline to configure the
Image Service to use the Identity service:</para>
Image service to use the Identity service:</para>
<mediaobject>
<imageobject>
<imagedata scale="50"
@ -297,12 +297,12 @@ verbose = True</programlisting>
<procedure>
<title>To finalize installation</title>
<step os="ubuntu;debian">
<para>Restart the Image Service services:</para>
<para>Restart the Image service services:</para>
<screen><prompt>#</prompt> <userinput>service glance-registry restart</userinput>
<prompt>#</prompt> <userinput>service glance-api restart</userinput></screen>
</step>
<step os="rhel;centos;fedora;sles;opensuse">
<para>Start the Image Service services and configure them to start when
<para>Start the Image service services and configure them to start when
the system boots:</para>
<screen><prompt>#</prompt> <userinput>systemctl enable openstack-glance-api.service openstack-glance-registry.service</userinput>
<prompt>#</prompt> <userinput>systemctl start openstack-glance-api.service openstack-glance-registry.service</userinput></screen>

6
doc/install-guide/section_glance-verify.xml
View File

@ -5,7 +5,7 @@
version="5.0"
xml:id="glance-verify">
<title>Verify operation</title>
<para>Verify operation of the Image Service using
<para>Verify operation of the Image service using
<link xlink:href="http://launchpad.net/cirros">CirrOS</link>, a small
Linux image that helps you test your OpenStack deployment.</para>
<para>For more information about how to download and build images,
@ -31,7 +31,7 @@
<screen><prompt>$</prompt> <userinput>wget -P /tmp/images http://cdn.download.cirros-cloud.net/0.3.3/cirros-0.3.3-x86_64-disk.img</userinput></screen>
</step>
<step>
<para>Upload the image to the Image Service using the
<para>Upload the image to the Image service using the
<glossterm baseform="QEMU Copy On Write 2 (QCOW2)">QCOW2</glossterm>
disk format, <glossterm>bare</glossterm> container format, and
public visibility so all projects can access it:</para>
@ -61,7 +61,7 @@
<para>For information about the <command>glance image-create</command>
parameters, see <link
xlink:href="http://docs.openstack.org/cli-reference/content/glanceclient_commands.html#glanceclient_subcommand_image-create"
>Image Service command-line client</link> in the
>Image service command-line client</link> in the
<citetitle>OpenStack Command-Line Interface
Reference</citetitle>.</para>
<para>For information about disk and container formats for

2
doc/install-guide/section_nova-compute-install.xml
View File

@ -141,7 +141,7 @@ novncproxy_base_url = http://<replaceable>controller</replaceable>:6080/vnc_auto
</step>
<step>
<para>In the <literal>[glance]</literal> section, configure the
location of the Image Service:</para>
location of the Image service:</para>
<programlisting language="ini">[glance]
...
host = <replaceable>controller</replaceable></programlisting>

2
doc/install-guide/section_nova-controller-install.xml
View File

@ -207,7 +207,7 @@ vncserver_proxyclient_address = 10.0.0.11</programlisting>
</step>
<step>
<para>In the <literal>[glance]</literal> section, configure the
location of the Image Service:</para>
location of the Image service:</para>
<programlisting language="ini">[glance]
...
host = <replaceable>controller</replaceable></programlisting>

4
doc/install-guide/section_nova-verify.xml
View File

@ -123,8 +123,8 @@
+-----------+----------------------------------+</computeroutput></screen>
</step>
<step>
<para>List images in the Image Service catalog to verify connectivity
with the Image Service:</para>
<para>List images in the Image service catalog to verify connectivity
with the Image service:</para>
<screen><prompt>$</prompt> <userinput>nova image-list</userinput>
<computeroutput>+--------------------------------------+---------------------+--------+--------+
| ID | Name | Status | Server |

2
doc/install-guide/section_trove-install.xml
View File

@ -11,7 +11,7 @@
<title>Prerequisites</title>
<para>This chapter assumes that you already have a working
OpenStack environment with at least the following components
installed: Compute, Image Service, Identity.</para>
installed: Compute, Image service, Identity.</para>
</formalpara>
<itemizedlist>
<listitem>

2
doc/user-guide/app_cheat_sheet.xml
View File

@ -59,7 +59,7 @@
</table>
<table rules="all" width="100%">
<caption>Image Service (glance)</caption>
<caption>Image service (glance)</caption>
<col width="30%"/>
<col width="70%"/>
<thead>

2
doc/user-guide/section_cli_nova_boot.xml
View File

@ -95,7 +95,7 @@
linkend="boot_from_volume">volume</link>. You can launch
an instance directly from one of the available OpenStack
images or from an image that you have copied to a persistent
volume. The OpenStack Image Service provides a pool of images
volume. The OpenStack Image service provides a pool of images
that are accessible to members of different projects.</para>
<?hard-pagebreak?>
<section xml:id="gather_parms">

2
doc/user-guide/section_dashboard_launch_instances.xml
View File

@ -10,7 +10,7 @@
<para>You can <link
linkend="dashboard_launch_instances_from_image">launch an
instance</link> from the following sources:</para>
<itemizedlist><listitem><para>Images uploaded to the OpenStack Image Service, as described
<itemizedlist><listitem><para>Images uploaded to the OpenStack Image service, as described
in <xref linkend="dashboard_manage_images"/>.</para></listitem>
<listitem><para>Image that you have copied to a persistent volume. The instance
launches from the volume, which is provided by the

2
doc/user-guide/section_dashboard_launch_instances_from_image.xml
View File

@ -35,7 +35,7 @@
<para>Log in to the dashboard, choose a project, and click
<guilabel>Images</guilabel>.</para>
<para>The dashboard shows the images that have been uploaded to
OpenStack Image Service and are available for this
OpenStack Image service and are available for this
project.</para>
<para>For details on creating images, see <link
xlink:href="http://docs.openstack.org/image-guide/content/ch_creating_images_manually.html"

4
doc/user-guide/section_sdk_auth_glance.xml
View File

@ -4,8 +4,8 @@
xmlns:xlink="http://www.w3.org/1999/xlink"
version="5.0"
xml:id="sdk_auth_glance">
<title>Authenticate against an Image Service endpoint</title>
<para>To authenticate against an Image Service endpoint, instantiate
<title>Authenticate against an Image service endpoint</title>
<para>To authenticate against an Image service endpoint, instantiate
a <link
xlink:href="http://docs.openstack.org/developer/python-glanceclient/api/glanceclient.v2.client.html#glanceclient.v2.client.Client"
> glanceclient.v2.client.Client</link> object:</para>

2
doc/user-guide/section_sdk_manage_images.xml
View File

@ -87,7 +87,7 @@ image = glance.images.get(image_id)</programlisting>
</section>
<section xml:id="sdk-nova-image-find">
<title>Get image by name</title>
<para>The Image Service Python bindings do not support the
<para>The Image service Python bindings do not support the
retrieval of an image object by name. However, the Compute
Python bindings enable you to get an image object by name. To
get an image object by name, call the <methodname>