openstack
/
openstack-manuals
Code Issues Proposed changes

Apply service name conventions for Image Service 

There are several instances of "Image service" in the upstream
documentation. As was recently clarified in the docs mailing list,
these should be "Image Service". This patch applies the fix.

Change-Id: Iefb63673162ae97b2c0fe1c3ff3fb1ac05e95d83
Partial-Bug: #1217503
This commit is contained in:
Don Domingo 2014-03-19 13:30:24 +10:00
parent 4e26cc9667
commit 98e7068e48
11 changed files with 18 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -372,7 +372,7 @@
</section>
<section 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.
@ -381,14 +381,14 @@
> OpenStack API</link> or 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 the
OpenStack Image command-line tool, see the <link
xlink:href="http://docs.openstack.org/user-guide/content/cli_manage_images.html"
> Image Management</link> section in the
<citetitle>OpenStack 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
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 have been created in the Identity
@ -559,7 +559,7 @@ header: Date: Thu, 13 Sep 2012 20:27:36 GMT
<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 shutdown. It is also possible to

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

@ -9,7 +9,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 service, 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/common/section_keystone-concepts-user-management.xml
View File

@ -82,11 +82,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/image-guide/ch_modifying_images.xml
View File

@ -7,7 +7,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

@ -369,7 +369,7 @@ kernel <replaceable>...</replaceable> console=tty0 console=ttyS0,115200n8</progr
<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 have this virtual machine
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
@ -380,6 +380,6 @@ kernel <replaceable>...</replaceable> console=tty0 console=ttyS0,115200n8</progr
<para>The underlying image file you created with
<command>qemu-img create</command>. For example,
<filename>/tmp/centos-6.4.qcow2</filename> is now
ready for uploading to the OpenStack Image service.</para>
ready for uploading to the OpenStack Image Service.</para>
</simplesect>
</section>

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

@ -233,7 +233,7 @@
<simplesect>
<title>Undefine the libvirt domain</title>
<para>Now that the image is ready to be uploaded to the Image
service, we no longer need to have this virtual machine
Service, we 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
@ -244,6 +244,6 @@
<para>The underlying image file that you created with
<command>qemu-img create</command>, such as
<filename>/tmp/precise.qcow2</filename>, is now ready
for uploading to the OpenStack Image service.</para>
for uploading to the OpenStack Image Service.</para>
</simplesect>
</section>

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

@ -28,7 +28,7 @@ rabbit_password = <replaceable>RABBIT_PASS</replaceable></programlisting>
</step>
<step>
<para>Restart the Image services with their new
<para>Restart the Image Services with their new
settings:</para>
<screen os="ubuntu;debian"><prompt>#</prompt> <userinput>service glance-registry restart</userinput>
<prompt>#</prompt> <userinput>service glance-api restart</userinput></screen>

2
doc/training-guides/bk001-ch002-associate-getting-started-quiz.xml
View File

@ -129,7 +129,7 @@
</listitem>
<listitem>
<formalpara>
<title>The Image service (Glance) in OpenStack provides: (Choose all that apply)</title>
<title>The Image Service (Glance) in OpenStack provides: (Choose all that apply)</title>
<para>
<orderedlist>
<listitem>

2
doc/training-guides/card127-glance.xml
View File

@ -5,7 +5,7 @@
version="5.0"
xml:id="configure-image">
<title>Install Glance</title>
<!-- this maps to user story "Card127 - As an associate trainee I need to be able to install OpenStack the Image service (Glance) on the controller node -->
<!-- this maps to user story "Card127 - As an associate trainee I need to be able to install OpenStack the Image Service (Glance) on the controller node -->
<!-- The basic install guide no longer exists. A new include needs to be found -->
<!--<xi:include href="../install-guide/basic-install-files/basic-install_controller-glance.xml"
xpointer="xmlns(db=http://docbook.org/ns/docbook) xpath(/*/*[not(self::db:title)])">

4
doc/training-guides/module001-ch007-keystone-arch.xml
View File

@ -183,11 +183,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
the 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 policy.json files in the Compute,
Identity, and Image service recognize only the admin role:
Identity, and Image Service recognize only the admin role:
all operations that do not require the admin role will be
accessible by any user that has any role in a
tenant.</para>

2
doc/training-guides/module002-ch001-networking-in-openstack.xml
View File

@ -141,7 +141,7 @@
OpenStack services.</para>
<para>OpenStack Networking is a standalone service, just like
other OpenStack services such as OpenStack Compute, OpenStack
Image service, OpenStack Identity service, and the OpenStack
Image Service, OpenStack Identity service, and the OpenStack
Dashboard. Like those services, a deployment of OpenStack
Networking often involves deploying several processes on a
variety of hosts.</para>