Apply service name conventions for Compute

There are several instances of "Compute Service" and "compute service"
in the upstream documentation. As was recently clarified in the docs
mailing list, these should be "Compute service/s". This patch corrects
all untagged instances inside normal <para> blocks.

Change-Id: Idcd7aafa0ce463e70635cb1c883a2476c1d97b5e
Partial-Bug: #1217503

doc/common/section_cli_nova_quotas.xml

@@ -13,7 +13,7 @@
   <title>Manage Compute service quotas</title>
   <para>As an administrative user, you can use the <command>nova quota-*</command>
     commands, which are provided by the <literal>python-novaclient</literal>
-    package, to update the Compute Service quotas for a specific tenant or
+    package, to update the Compute service quotas for a specific tenant or
     tenant user, as well as update the quota defaults for a new tenant.</para>
       <table rules="all">
       <caption>Compute quota descriptions</caption>

doc/common/section_getstart_compute.xml

@@ -14,7 +14,7 @@
     example, the number of instances). The Compute service scales
     horizontally on standard hardware, and downloads images to launch
     instances as required.</para>
-  <para>The Compute Service is made up of the following functional
+  <para>The Compute service is made up of the following functional
     areas and their underlying components:</para>
   <itemizedlist>
     <title>API</title>
@@ -198,7 +198,7 @@
         and development work), MySQL, and PostgreSQL.</para>
     </listitem>
   </itemizedlist>
-  <para>The Compute Service interacts with other OpenStack services:
+  <para>The Compute service interacts with other OpenStack services:
     Identity Service for authentication, Image Service for images, and
     the OpenStack dashboard for a web interface.</para>
 </section>

doc/common/section_using-vnc-console.xml

@@ -13,7 +13,7 @@
     xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
     xml:id="getting-an-access-url">
     <title>Get an access URL</title>
-    <para>The Compute Service  enables you to create access_urls
+    <para>The Compute service  enables you to create access_urls
       through the os-consoles extension. Support for accessing this
       URL is provided by the nova client:</para>
     <screen><prompt>$</prompt> <userinput>nova get-vnc-console <replaceable>[server_id]</replaceable> <replaceable>[novnc|xvpvnc]</replaceable></userinput></screen>

doc/config-reference/block-storage/drivers/xen-sm-driver.xml

@@ -125,7 +125,7 @@
                 <listitem>
                     <para>Ensure all <emphasis role="bold"
                             >hosts</emphasis> running volume and
-                        compute services have connectivity to the
+                        Compute services have connectivity to the
                         storage system.</para>
                 </listitem>
             </orderedlist>

doc/config-reference/compute/section_compute-conductor.xml

@@ -30,7 +30,7 @@
         currently in <systemitem class="service"
             >nova-compute</systemitem> up to the <systemitem
             class="service">nova-conductor</systemitem> layer. The
-        compute service will start to look like a less intelligent
+        Compute service will start to look like a less intelligent
         slave service to <systemitem class="service"
             >nova-conductor</systemitem>. The conductor service will
         implement long running complex operations, ensuring forward

doc/config-reference/compute/section_compute-configure-service-groups.xml

@@ -12,7 +12,7 @@
          xmlns:ns3="http://www.w3.org/1998/Math/MathML"
          xmlns:ns="http://docbook.org/ns/docbook"
          version="5.0">
-  <title>Configuring Compute Service Groups</title>
+  <title>Configuring Compute service groups</title>
   <para>To effectively manage and utilize compute nodes, the Compute service must know their statuses. For example, when a user launches a
   new VM, the Compute scheduler should send the request to a live node
   (with enough capacity too, of course). From the Grizzly release

doc/config-reference/compute/section_compute-sample-configuration-files.xml

@@ -5,7 +5,7 @@
     <para>Files in this section can be found in <systemitem>/etc/nova</systemitem>.</para>
     <section xml:id="section_nova-api-paste.ini">
         <title>api-paste.ini</title>
-        <para>The Compute Service stores its API configuration settings in the
+        <para>The Compute service stores its API configuration settings in the
             <filename>api-paste.ini</filename> file.</para>
         <programlisting language="ini">
                 <xi:include parse="text" href="http://git.openstack.org/cgit/openstack/nova/plain/etc/nova/api-paste.ini"/>
@@ -13,7 +13,7 @@
     </section>
     <section xml:id="section_nova-policy.json">
         <title>policy.json</title>
-        <para>The <filename>policy.json</filename> file defines additional access controls that apply to the Compute Service.</para>
+        <para>The <filename>policy.json</filename> file defines additional access controls that apply to the Compute service.</para>
         <programlisting language="json">
                 <xi:include parse="text" href="http://git.openstack.org/cgit/openstack/nova/plain/etc/nova/policy.json"/>
         </programlisting>
@@ -21,7 +21,7 @@
     <section xml:id="section_nova-rootwrap.conf">
         <title>rootwrap.conf</title>
         <para>The <filename>rootwrap.conf</filename> file defines configuration
-            values used by the rootwrap script when the Compute Service
+            values used by the rootwrap script when the Compute service
             needs to escalate its privileges to those of the root user.</para>
         <programlisting language="ini">
                 <xi:include parse="text" href="http://git.openstack.org/cgit/openstack/nova/plain/etc/nova/rootwrap.conf"/>

doc/glossary/glossary-terms.xml

@@ -114,7 +114,7 @@
         <glossentry>
             <glossterm>accounting</glossterm>
             <glossdef>
-                <para>The Compute Service provides accounting information
+                <para>The Compute service provides accounting information
                     through the event notification and system usage data
                     facilities.</para>
             </glossdef>
@@ -200,7 +200,7 @@
         <glossentry>
             <glossterm>alert</glossterm>
             <glossdef>
-                <para>The Compute Service can send alerts through its
+                <para>The Compute service can send alerts through its
                     notification system, which includes a facility to
                     create custom notification drivers. Alerts can be
                     sent to and displayed on the horizon dashboard.</para>
@@ -1036,7 +1036,7 @@
           <glossterm>Compute</glossterm>
           <glossdef>
             <para>The OpenStack core project that provides compute
-            services. The project name of the Compute Service is nova.
+            services. The project name of the Compute service is nova.
             </para>
           </glossdef>
         </glossentry>
@@ -1076,7 +1076,7 @@
             </glossdef>
         </glossentry>
         <glossentry>
-            <glossterm>compute service</glossterm>
+            <glossterm>Compute service</glossterm>
             <glossdef>
                 <para>Name for the Compute component that
                     manages VMs.</para>

doc/install-guide/section_neutron-network-node.xml

@@ -363,7 +363,7 @@ local_ip = DATA_INTERFACE_IP</programlisting>
           Compute metadata service.</para>
         <para>On the controller, edit the
           <filename>/etc/nova/nova.conf</filename> file to define a
-          secret key that will be shared between the Compute Service
+          secret key that will be shared between the Compute service
           and the Networking metadata agent.</para>
         <para os="debian;ubuntu">Add to the
           <literal>[DEFAULT]</literal> section:</para>

doc/install-guide/section_nova-compute.xml

@@ -138,19 +138,19 @@ admin_user = nova
 admin_password = <replaceable>NOVA_PASS</replaceable></programlisting>
     </step>
     <step os="fedora;rhel;centos;ubuntu;opensuse;sles">
-      <para os="fedora;rhel;centos">Configure the Compute Service to use the
+      <para os="fedora;rhel;centos">Configure the Compute service to use the
         Qpid message broker by setting these configuration keys:</para>
       <screen os="fedora;rhel;centos"><prompt>#</prompt> <userinput>openstack-config --set /etc/nova/nova.conf \
   DEFAULT rpc_backend nova.openstack.common.rpc.impl_qpid</userinput>
 <prompt>#</prompt> <userinput>openstack-config --set /etc/nova/nova.conf DEFAULT qpid_hostname <replaceable>controller</replaceable></userinput></screen>
-      <para os="ubuntu">Configure the Compute Service to use
+      <para os="ubuntu">Configure the Compute service to use
         the RabbitMQ message broker by setting these configuration
         keys in the <literal>[DEFAULT]</literal> configuration group of
         the <filename>/etc/nova/nova.conf</filename> file:</para>
       <programlisting os="ubuntu" language="ini">rpc_backend = nova.rpc.impl_kombu
 rabbit_host = controller
 rabbit_password = <replaceable>RABBIT_PASS</replaceable></programlisting>
-      <para os="opensuse;sles">Configure the Compute Service to use the RabbitMQ message broker
+      <para os="opensuse;sles">Configure the Compute service to use the RabbitMQ message broker
         by setting these configuration keys:</para>
       <screen os="opensuse;sles"><prompt>#</prompt> <userinput>openstack-config --set /etc/nova/nova.conf \
   DEFAULT rpc_backend nova.rpc.impl_kombu</userinput>

doc/install-guide/section_nova-controller.xml

@@ -58,7 +58,7 @@ connection = mysql://nova:<replaceable>NOVA_DBPASS</replaceable>@controller/nova
 <prompt>#</prompt> <userinput>openstack-config --set /etc/nova/nova.conf DEFAULT qpid_hostname <replaceable>controller</replaceable></userinput></screen>
     </step>
     <step os="ubuntu">
-      <para>Configure the Compute Service to use the RabbitMQ message broker by
+      <para>Configure the Compute service to use the RabbitMQ message broker by
         setting these configuration keys in the <literal>[DEFAULT]</literal>
         configuration group of the <filename>/etc/nova/nova.conf</filename>
         file:</para>

doc/security-guide/ch004_book-introduction.xml

@@ -120,12 +120,12 @@
       </inlinemediaobject></para>
     <section xml:id="ch004_book-introduction-idp134736">
       <title>Compute</title>
-      <para>OpenStack Compute Service (Nova) provides services to
+      <para>OpenStack Compute service (nova) provides services to
         support the management of virtual machine instances at scale,
         instances that host multi-tiered applications, dev/test
         environments, "Big Data" crunching Hadoop clusters, and/or
         high performance computing.</para>
-      <para>The Compute Service facilitates this management through an
+      <para>The Compute service facilitates this management through an
         abstraction layer that interfaces with supported hypervisors,
         which we address later on in more detail.</para>
       <para>Later in the guide, we focus generically on the
@@ -206,8 +206,8 @@
       <title>Image Service</title>
       <para>The OpenStack Image Service (Glance) provides disk image
         management services. The Image Service provides image
-        discovery, registration, and delivery services to Compute, the
+        discovery, registration, and delivery services to the
-        compute service, as needed.</para>
+        Compute service, as needed.</para>
       <para>Trusted processes for managing the life cycle of disk
         images are required, as are all the previously mentioned
         issues with respect to data security.</para>

doc/security-guide/ch005_security-domains.xml

@@ -107,7 +107,7 @@
       </section>
       <section xml:id="ch005_security-domains-idp116736">
         <title>Outbound attacks and reputational risk</title>
-        <para>Careful consideration should be given to potential outbound abuse from a cloud deployment.  Whether public or private, clouds tend to have lots of resource available. An attacker who has established a point of presence within the cloud, either through hacking in or via entitled access (rogue employee), can bring these resources to bear against the internet at large. Clouds with compute services make for ideal DDoS and brute force engines. This is perhaps a more pressing issue for public clouds as their users are largely unaccountable, and can quickly spin up numerous disposable instances for outbound attacks.  Major damage can be inflicted upon a company's reputation if it becomes known for hosting malicious software or launching attacks on other networks. Methods of prevention include egress security groups, outbound traffic inspection, customer education and awareness, and fraud and abuse mitigation strategies.</para>
+        <para>Careful consideration should be given to potential outbound abuse from a cloud deployment.  Whether public or private, clouds tend to have lots of resource available. An attacker who has established a point of presence within the cloud, either through hacking in or via entitled access (rogue employee), can bring these resources to bear against the internet at large. Clouds with Compute services make for ideal DDoS and brute force engines. This is perhaps a more pressing issue for public clouds as their users are largely unaccountable, and can quickly spin up numerous disposable instances for outbound attacks.  Major damage can be inflicted upon a company's reputation if it becomes known for hosting malicious software or launching attacks on other networks. Methods of prevention include egress security groups, outbound traffic inspection, customer education and awareness, and fraud and abuse mitigation strategies.</para>
       </section>
       <section xml:id="ch005_security-domains-idp120000">
         <title>Attack Types</title>

doc/security-guide/ch024_authentication.xml

@@ -264,7 +264,7 @@
       taken as some internal services will need sufficient time to
       complete their work. The cloud may not provide services if
       tokens expire too early. An example of this would be the time
-      needed by the Compute Service to transfer a disk image onto the
+      needed by the Compute service to transfer a disk image onto the
       hypervisor for local caching.</para>
     <para>The following example shows a PKI token. Note that, in
       practice, the token id value is about 3500 bytes. We shorten it

doc/security-guide/ch026_compute.xml

@@ -1,11 +1,11 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <chapter xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://docbook.org/ns/docbook" xmlns:db="http://docbook.org/ns/docbook" version="5.0" xml:id="ch026_compute"><?dbhtml stop-chunking?>
     <title>Compute</title>
-    <para>The Compute Service (Nova) is one of the more complex OpenStack services.  It runs in many locations throughout the cloud and interacts with a variety of internal services.  For this reason, most of our recommendations regarding best practices for Compute Service configuration are distributed throughout this book. We provide specific details in the sections on Management, API Endpoints, Messaging, and Database.</para>
+    <para>The Compute service (nova) is one of the more complex OpenStack services.  It runs in many locations throughout the cloud and interacts with a variety of internal services.  For this reason, most of our recommendations regarding best practices for Compute service configuration are distributed throughout this book. We provide specific details in the sections on Management, API Endpoints, Messaging, and Database.</para>
     <section xml:id="ch026_compute-idp45072">
       <title>Virtual Console Selection</title>
       <para>One decision a cloud architect will need to make regarding
-      Compute Service configuration is whether to use <glossterm
+      Compute service configuration is whether to use <glossterm
       baseform="Virtual Network Computing (VNC)">VNC</glossterm> or
       <glossterm>SPICE</glossterm>. Below we provide some details on
       the differences between these options.</para>

doc/training-guides/module001-ch005-vm-provisioning-walk-through.xml

@@ -137,7 +137,7 @@
       for the storage and management of images within
       OpenStack.</para>
     <para>Instances are the individual virtual machines running on
-      physical compute nodes. The OpenStack Compute Service manages
+      physical compute nodes. The OpenStack Compute service manages
       instances. Any number of instances maybe started from the same
       image. Each instance is run from a copy of the base image so
       runtime changes made by an instance do not change the image it

doc/training-guides/module001-ch009-vm-placement.xml

@@ -9,8 +9,9 @@
     dispatch compute and volume requests. For example, the
     nova-scheduler service determines which host a VM should launch
     on. The term host in the context of filters means a physical node
-    that has a nova-compute service running on it. You can configure
+    that has a <systemitem class="service">nova-compute</systemitem>
-    the scheduler through a variety of options.</para>
+    service running on it. You can configure the scheduler through a
+    variety of options.</para>
   <figure>
     <title>Nova</title>
     <mediaobject>
@@ -91,7 +92,7 @@
         </listitem>
         <listitem>
           <para>ComputeCapabilitiesFilter - checks that the
-            capabilities provided by the host compute service satisfy
+            capabilities provided by the host Compute service satisfy
             any extra specifications associated with the instance
             type. It passes hosts that can create the specified
             instance type.</para>
@@ -140,7 +141,7 @@
       <para>Next standard filter to describe is AvailabilityZoneFilter
         and it isn’t difficult too. This filter just looks at the
         availability zone of compute node and availability zone from
-        the properties of the request. Each compute service has its
+        the properties of the request. Each Compute service has its
         own availability zone. So deployment engineers have an option
         to run scheduler with availability zones support and can
         configure availability zones on each compute host. This
@@ -169,7 +170,7 @@
         capabilities satisfy the requested specifications. All hosts
         are passed if no extra_specs are specified.</para>
       <para>ComputeFilter is quite simple and passes any host whose
-        compute service is enabled and operational.</para>
+        Compute service is enabled and operational.</para>
       <para>Now we are going to IsolatedHostsFilter. There can be some
         special hosts reserved for specific images. These hosts are
         called isolated. So the images to run on the isolated hosts

doc/user-guide-admin/section_cli_keystone_set_quotas.xml

@@ -19,8 +19,8 @@
     Quotas can be enforced at both the tenant (or project)
     and the tenant-user level.</para>
   <para>Using the command-line interface, you can manage quotas for
-    the OpenStack Compute Service, the OpenStack Block Storage Service,
+    the OpenStack Compute service, the OpenStack Block Storage service,
-    and the OpenStack Networking Service.</para>
+    and the OpenStack Networking service.</para>
   <para>Typically, default values are changed because a tenant
     requires more than 10 volumes, or more than 1 TB on a compute node.</para>
   <note>

doc/user-guide-admin/section_dashboard_admin_set_quotas.xml

@@ -23,8 +23,8 @@
     quotas for new tenants, as well as update quotas for existing tenants.</para>
   <note>
     <para>Using the command-line interface, you can manage quotas for the
-      OpenStack Compute Service, the OpenStack Block Storage Service, and
+      OpenStack Compute service, the OpenStack Block Storage service, and
-      the OpenStack Networking Service (see <xref linkend="cli_set_quotas"/>).
+      the OpenStack Networking service (see <xref linkend="cli_set_quotas"/>).
       Additionally, you can update Compute service quotas for
       tenant users.</para>
   </note>