From 6c20b215f452f83016f641513c26a99297bc325f Mon Sep 17 00:00:00 2001 From: KATO Tomoyuki Date: Tue, 8 Mar 2016 10:02:51 +0900 Subject: [PATCH] [glossary] update the service names To follow the latest official names: https://git.openstack.org/cgit/openstack/governance/tree/reference/projects.yaml Change-Id: I13be910682ee30a91fadb5d78fb68e8a3ae78128 --- ...compute-focus-technical-considerations.rst | 14 ++--- ...eneralpurpose-technical-considerations.rst | 16 ++--- doc/common/get_started_identity.rst | 2 +- doc/glossary/glossary-terms.xml | 58 +++++++++---------- .../source/intro-networking.rst | 10 ++-- 5 files changed, 48 insertions(+), 52 deletions(-) diff --git a/doc/arch-design/source/compute-focus-technical-considerations.rst b/doc/arch-design/source/compute-focus-technical-considerations.rst index 1d88996008..341d18354f 100644 --- a/doc/arch-design/source/compute-focus-technical-considerations.rst +++ b/doc/arch-design/source/compute-focus-technical-considerations.rst @@ -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 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: -* :term:`Orchestration` (heat) +* :term:`Orchestration service` (heat) Given the nature of the applications involved in this scenario, these are heavily automated deployments. Making use of Orchestration is 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 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 instances using Orchestration. Users that are not using the Orchestration service do not need to deploy the Telemetry service and may choose to use external solutions to fulfill their metering and monitoring requirements. -* OpenStack :term:`Block Storage` (cinder) +* :term:`Block Storage service` (cinder) Due to the burst-able nature of the workloads and the applications 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 @@ -206,7 +206,7 @@ Also consider several specialized components: OpenStack Block Storage (cinder) in the infrastructure, but typically it is not a central component. -* :term:`Networking` (neutron) +* :term:`Networking service` (neutron) When choosing a networking platform, ensure that it either works with all desired hypervisor and container technologies and their OpenStack drivers, or that it includes an implementation of an ML2 mechanism diff --git a/doc/arch-design/source/generalpurpose-technical-considerations.rst b/doc/arch-design/source/generalpurpose-technical-considerations.rst index 7309884015..c0cc60cf2c 100644 --- a/doc/arch-design/source/generalpurpose-technical-considerations.rst +++ b/doc/arch-design/source/generalpurpose-technical-considerations.rst @@ -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 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:`Identity` (:term:`keystone`) +* :term:`Identity service` (:term:`keystone`) -* :term:`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` -(:term:`swift`). :term:`Block Storage` (:term:`cinder`). These may be -selected to provide storage to applications and instances. +A general purpose cloud may also include :term:`Object Storage service` +(:term:`swift`). :term:`Block Storage service` (:term:`cinder`). +These may be selected to provide storage to applications and instances. Supplemental software ~~~~~~~~~~~~~~~~~~~~~ diff --git a/doc/common/get_started_identity.rst b/doc/common/get_started_identity.rst index 3f230e5740..4ad4ba7abe 100644 --- a/doc/common/get_started_identity.rst +++ b/doc/common/get_started_identity.rst @@ -2,7 +2,7 @@ OpenStack Identity ================== -The OpenStack :term:`Identity service ` provides a single point of +The OpenStack :term:`Identity service` provides a single point of integration for managing authentication, authorization, and service catalog services. Other OpenStack services use the Identity service as a common unified API. Additionally, services that provide information about users diff --git a/doc/glossary/glossary-terms.xml b/doc/glossary/glossary-terms.xml index 588398ad3d..b24755c783 100644 --- a/doc/glossary/glossary-terms.xml +++ b/doc/glossary/glossary-terms.xml @@ -546,9 +546,9 @@ - Application catalog + Application Catalog service - Application catalog + Application Catalog service murano @@ -981,9 +981,9 @@ - Bare metal service + Bare Metal service - Bare metal service + Bare Metal service ironic @@ -1023,7 +1023,7 @@ Benchmark service - Benchmark service + Benchmark service rally @@ -1118,9 +1118,9 @@ - Block Storage + Block Storage service - Block Storage + Block Storage service @@ -1783,9 +1783,9 @@ - Clustering + Clustering service - Clustering + Clustering service @@ -1879,11 +1879,9 @@ - Compute + Compute service - Compute - - definition of + Compute service @@ -2319,9 +2317,9 @@ - dashboard + Dashboard - dashboard + Dashboard @@ -2393,9 +2391,9 @@ - Data processing service + Data Processing service - Data processing service + Data Processing service sahara @@ -2542,9 +2540,9 @@ - Designate + designate - Designate + designate @@ -4256,11 +4254,9 @@ - Identity + Identity service - Identity - - basics of + Identity service @@ -4969,9 +4965,9 @@ - Key management service + Key Manager service - Key management service + Key Manager service barbican @@ -5915,7 +5911,7 @@ - Networking + Networking service A core OpenStack project that provides a network connectivity @@ -6225,7 +6221,7 @@ - Object Storage + Object Storage service The OpenStack core project that provides eventually consistent @@ -6467,9 +6463,9 @@ - Orchestration + Orchestration service - Orchestration + Orchestration service @@ -8656,9 +8652,9 @@ T - Telemetry + Telemetry service - Telemetry + Telemetry service diff --git a/doc/networking-guide/source/intro-networking.rst b/doc/networking-guide/source/intro-networking.rst index 29f3b4545f..9ad2e60017 100644 --- a/doc/networking-guide/source/intro-networking.rst +++ b/doc/networking-guide/source/intro-networking.rst @@ -2,7 +2,7 @@ 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 cloud. The project code-name for Networking services is neutron. 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 components: -* OpenStack :term:`Identity` (keystone) is used for authentication and - authorization of API requests. +* OpenStack :term:`Identity service` (keystone) is used for authentication + 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. -* 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 interface.