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
Download Patch File Download Diff File Expand all files Collapse all files

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>