openstack/openstack-manuals
Code Issues Proposed changes

[glossary] update the service names

Browse Source 
To follow the latest official names:
https://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml

Change-Id: I13be910682ee30a91fadb5d78fb68e8a3ae78128
This commit is contained in:
KATO Tomoyuki 2016-03-08 10:02:51 +09:00
parent 1bb5545ca4
commit 6c20b215f4
5 changed files with 48 additions and 52 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/arch-design/source/compute-focus-technical-considerations.rst
View File

@ -176,29 +176,29 @@ Due to the nature of the workloads in this scenario, a number of
components are highly beneficial for a Compute-focused cloud. This components are highly beneficial for a Compute-focused cloud. This
includes the typical OpenStack components: includes the typical OpenStack components:
* OpenStack Compute (nova) * :term:`Compute service` (nova)
* OpenStack Image service (glance) * :term:`Image service` (glance)
* OpenStack Identity (keystone) * :term:`Identity service` (keystone)
Also consider several specialized components: Also consider several specialized components:
* :term:`Orchestration` (heat) * :term:`Orchestration service` (heat)
Given the nature of the applications involved in this scenario, these Given the nature of the applications involved in this scenario, these
are heavily automated deployments. Making use of Orchestration is are heavily automated deployments. Making use of Orchestration is
highly beneficial in this case. You can script the deployment of a highly beneficial in this case. You can script the deployment of a
batch of instances and the running of tests, but it makes sense to batch of instances and the running of tests, but it makes sense to
use the Orchestration service to handle all these actions. use the Orchestration service to handle all these actions.
* :term:`Telemetry` (ceilometer) * :term:`Telemetry service` (ceilometer)
Telemetry and the alarms it generates support autoscaling of Telemetry and the alarms it generates support autoscaling of
instances using Orchestration. Users that are not using the instances using Orchestration. Users that are not using the
Orchestration service do not need to deploy the Telemetry service and Orchestration service do not need to deploy the Telemetry service and
may choose to use external solutions to fulfill their metering and may choose to use external solutions to fulfill their metering and
monitoring requirements. monitoring requirements.
* OpenStack :term:`Block Storage` (cinder) * :term:`Block Storage service` (cinder)
Due to the burst-able nature of the workloads and the applications Due to the burst-able nature of the workloads and the applications
and instances that perform batch processing, this cloud mainly uses and instances that perform batch processing, this cloud mainly uses
memory or CPU, so the need for add-on storage to each instance is not memory or CPU, so the need for add-on storage to each instance is not
@ -206,7 +206,7 @@ Also consider several specialized components:
OpenStack Block Storage (cinder) in the infrastructure, but typically OpenStack Block Storage (cinder) in the infrastructure, but typically
it is not a central component. it is not a central component.
* :term:`Networking` (neutron) * :term:`Networking service` (neutron)
When choosing a networking platform, ensure that it either works with When choosing a networking platform, ensure that it either works with
all desired hypervisor and container technologies and their OpenStack all desired hypervisor and container technologies and their OpenStack
drivers, or that it includes an implementation of an ML2 mechanism drivers, or that it includes an implementation of an ML2 mechanism

16
doc/arch-design/source/generalpurpose-technical-considerations.rst
View File

@ -344,21 +344,21 @@ A general purpose OpenStack cloud design should incorporate the core
OpenStack services to provide a wide range of services to end-users. The OpenStack services to provide a wide range of services to end-users. The
OpenStack core services recommended in a general purpose cloud are: OpenStack core services recommended in a general purpose cloud are:
* :term:`Compute` (:term:`nova`) * :term:`Compute service` (:term:`nova`)
* :term:`Networking` (:term:`neutron`) * :term:`Networking service` (:term:`neutron`)
* :term:`Image service` (:term:`glance`) * :term:`Image service` (:term:`glance`)
* :term:`Identity` (:term:`keystone`) * :term:`Identity service` (:term:`keystone`)
* :term:`Dashboard<dashboard>` (:term:`horizon`) * :term:`Dashboard` (:term:`horizon`)
* :term:`Telemetry` (:term:`ceilometer`) * :term:`Telemetry service` (:term:`ceilometer`)
A general purpose cloud may also include :term:`Object Storage` A general purpose cloud may also include :term:`Object Storage service`
(:term:`swift`). :term:`Block Storage` (:term:`cinder`). These may be (:term:`swift`). :term:`Block Storage service` (:term:`cinder`).
selected to provide storage to applications and instances. These may be selected to provide storage to applications and instances.
Supplemental software Supplemental software
~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~

2
doc/common/get_started_identity.rst
View File

@ -2,7 +2,7 @@
OpenStack Identity OpenStack Identity
================== ==================
The OpenStack :term:`Identity service <Identity>` provides a single point of The OpenStack :term:`Identity service` provides a single point of
integration for managing authentication, authorization, and service catalog integration for managing authentication, authorization, and service catalog
services. Other OpenStack services use the Identity service as a common services. Other OpenStack services use the Identity service as a common
unified API. Additionally, services that provide information about users unified API. Additionally, services that provide information about users

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

@ -546,9 +546,9 @@
</glossentry> </glossentry>
<glossentry> <glossentry>
<glossterm>Application catalog</glossterm> <glossterm>Application Catalog service</glossterm>
<indexterm class="singular"> <indexterm class="singular">
<primary>Application catalog</primary> <primary>Application Catalog service</primary>
<secondary>murano</secondary> <secondary>murano</secondary>
</indexterm> </indexterm>
@ -981,9 +981,9 @@
</glossentry> </glossentry>
<glossentry> <glossentry>
<glossterm>Bare metal service</glossterm> <glossterm>Bare Metal service</glossterm>
<indexterm class="singular"> <indexterm class="singular">
<primary>Bare metal service</primary> <primary>Bare Metal service</primary>
<secondary>ironic</secondary> <secondary>ironic</secondary>
</indexterm> </indexterm>
@ -1023,7 +1023,7 @@
<glossentry> <glossentry>
<glossterm>Benchmark service</glossterm> <glossterm>Benchmark service</glossterm>
<indexterm class="singular"> <indexterm class="singular">
<primary>Benchmark service </primary> <primary>Benchmark service</primary>
<secondary>rally</secondary> <secondary>rally</secondary>
</indexterm> </indexterm>
@ -1118,9 +1118,9 @@
</glossentry> </glossentry>
<glossentry> <glossentry>
<glossterm>Block Storage</glossterm> <glossterm>Block Storage service</glossterm>
<indexterm class="singular"> <indexterm class="singular">
<primary>Block Storage</primary> <primary>Block Storage service</primary>
</indexterm> </indexterm>
<glossdef> <glossdef>
@ -1783,9 +1783,9 @@
</glossentry> </glossentry>
<glossentry> <glossentry>
<glossterm>Clustering</glossterm> <glossterm>Clustering service</glossterm>
<indexterm class="singular"> <indexterm class="singular">
<primary>Clustering</primary> <primary>Clustering service</primary>
</indexterm> </indexterm>
<glossdef> <glossdef>
@ -1879,11 +1879,9 @@
</glossentry> </glossentry>
<glossentry> <glossentry>
<glossterm>Compute</glossterm> <glossterm>Compute service</glossterm>
<indexterm class="singular"> <indexterm class="singular">
<primary>Compute</primary> <primary>Compute service</primary>
<secondary>definition of</secondary>
</indexterm> </indexterm>
<glossdef> <glossdef>
@ -2319,9 +2317,9 @@
</glossentry> </glossentry>
<glossentry> <glossentry>
<glossterm>dashboard</glossterm> <glossterm>Dashboard</glossterm>
<indexterm class="singular"> <indexterm class="singular">
<primary>dashboard</primary> <primary>Dashboard</primary>
</indexterm> </indexterm>
<glossdef> <glossdef>
@ -2393,9 +2391,9 @@
</glossentry> </glossentry>
<glossentry> <glossentry>
<glossterm>Data processing service</glossterm> <glossterm>Data Processing service</glossterm>
<indexterm class="singular"> <indexterm class="singular">
<primary>Data processing service</primary> <primary>Data Processing service</primary>
<secondary>sahara</secondary> <secondary>sahara</secondary>
</indexterm> </indexterm>
@ -2542,9 +2540,9 @@
</glossentry> </glossentry>
<glossentry> <glossentry>
<glossterm>Designate</glossterm> <glossterm>designate</glossterm>
<indexterm class="singular"> <indexterm class="singular">
<primary>Designate</primary> <primary>designate</primary>
</indexterm> </indexterm>
<glossdef> <glossdef>
@ -4256,11 +4254,9 @@
</glossentry> </glossentry>
<glossentry> <glossentry>
<glossterm>Identity</glossterm> <glossterm>Identity service</glossterm>
<indexterm class="singular"> <indexterm class="singular">
<primary>Identity</primary> <primary>Identity service</primary>
<secondary>basics of</secondary>
</indexterm> </indexterm>
<glossdef> <glossdef>
@ -4969,9 +4965,9 @@
</glossentry> </glossentry>
<glossentry> <glossentry>
<glossterm>Key management service</glossterm> <glossterm>Key Manager service</glossterm>
<indexterm class="singular"> <indexterm class="singular">
<primary>Key management service</primary> <primary>Key Manager service</primary>
<secondary>barbican</secondary> <secondary>barbican</secondary>
</indexterm> </indexterm>
@ -5915,7 +5911,7 @@
</glossentry> </glossentry>
<glossentry> <glossentry>
<glossterm>Networking</glossterm> <glossterm>Networking service</glossterm>
<glossdef> <glossdef>
<para>A core OpenStack project that provides a network connectivity <para>A core OpenStack project that provides a network connectivity
@ -6225,7 +6221,7 @@
</glossentry> </glossentry>
<glossentry> <glossentry>
<glossterm>Object Storage</glossterm> <glossterm>Object Storage service</glossterm>
<glossdef> <glossdef>
<para>The OpenStack core project that provides eventually consistent <para>The OpenStack core project that provides eventually consistent
@ -6467,9 +6463,9 @@
</glossentry> </glossentry>
<glossentry> <glossentry>
<glossterm>Orchestration</glossterm> <glossterm>Orchestration service</glossterm>
<indexterm class="singular"> <indexterm class="singular">
<primary>Orchestration</primary> <primary>Orchestration service</primary>
</indexterm> </indexterm>
<glossdef> <glossdef>
@ -8656,9 +8652,9 @@
<title>T</title> <title>T</title>
<glossentry> <glossentry>
<glossterm>Telemetry</glossterm> <glossterm>Telemetry service</glossterm>
<indexterm class="singular"> <indexterm class="singular">
<primary>Telemetry</primary> <primary>Telemetry service</primary>
</indexterm> </indexterm>
<glossdef> <glossdef>

10
doc/networking-guide/source/intro-networking.rst
View File

@ -2,7 +2,7 @@
Introduction to networking Introduction to networking
========================== ==========================
The OpenStack :term:`Networking` service provides an API that allows users The OpenStack :term:`Networking service` provides an API that allows users
to set up and define network connectivity and addressing in the to set up and define network connectivity and addressing in the
cloud. The project code-name for Networking services is neutron. cloud. The project code-name for Networking services is neutron.
OpenStack Networking handles the creation and management of a virtual OpenStack Networking handles the creation and management of a virtual
@ -24,13 +24,13 @@ to that specific host instead.
OpenStack Networking integrates with various OpenStack OpenStack Networking integrates with various OpenStack
components: components:
* OpenStack :term:`Identity` (keystone) is used for authentication and * OpenStack :term:`Identity service` (keystone) is used for authentication
authorization of API requests. and authorization of API requests.
* OpenStack :term:`Compute` (nova) is used to plug each virtual * OpenStack :term:`Compute service` (nova) is used to plug each virtual
NIC on the VM into a particular network. NIC on the VM into a particular network.
* OpenStack :term:`dashboard` (horizon) is used by administrators and tenant * OpenStack :term:`Dashboard` (horizon) is used by administrators and tenant
users to create and manage network services through a web-based graphical users to create and manage network services through a web-based graphical
interface. interface.