diff --git a/doc/arch-design-draft/source/design-storage/design-storage-concepts.rst b/doc/arch-design-draft/source/design-storage/design-storage-concepts.rst index 39c9d086c1..f442159226 100644 --- a/doc/arch-design-draft/source/design-storage/design-storage-concepts.rst +++ b/doc/arch-design-draft/source/design-storage/design-storage-concepts.rst @@ -11,9 +11,9 @@ your cloud. It is important to understand the distinction between Ephemeral storage ~~~~~~~~~~~~~~~~~ -If you deploy only the OpenStack :term:`Compute service` (nova), by default -your users do not have access to any form of persistent storage. The disks -associated with VMs are ephemeral, meaning that from the user's point +If you deploy only the OpenStack :term:`Compute service (nova)`, by +default your users do not have access to any form of persistent storage. The +disks associated with VMs are ephemeral, meaning that from the user's point of view they disappear when a virtual machine is terminated. Persistent storage diff --git a/doc/arch-design/source/compute-focus-technical-considerations.rst b/doc/arch-design/source/compute-focus-technical-considerations.rst index ebc858974b..0d0ab5db52 100644 --- a/doc/arch-design/source/compute-focus-technical-considerations.rst +++ b/doc/arch-design/source/compute-focus-technical-considerations.rst @@ -176,7 +176,7 @@ 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: -* :term:`Compute service` (nova) +* :term:`Compute service (nova)` * :term:`Image service` (glance) diff --git a/doc/arch-design/source/generalpurpose-operational-considerations.rst b/doc/arch-design/source/generalpurpose-operational-considerations.rst index 750f01de96..ffbb380fd2 100644 --- a/doc/arch-design/source/generalpurpose-operational-considerations.rst +++ b/doc/arch-design/source/generalpurpose-operational-considerations.rst @@ -52,7 +52,7 @@ critically important to monitor include: * Image disk utilization -* Response time to the :term:`Compute API` +* Response time to the :term:`Compute API ` Leveraging existing monitoring systems is an effective check to ensure OpenStack environments can be monitored. diff --git a/doc/arch-design/source/generalpurpose-technical-considerations.rst b/doc/arch-design/source/generalpurpose-technical-considerations.rst index 2eb58397bb..9f06eb69c7 100644 --- a/doc/arch-design/source/generalpurpose-technical-considerations.rst +++ b/doc/arch-design/source/generalpurpose-technical-considerations.rst @@ -344,7 +344,7 @@ 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 service` (:term:`nova`) +* :term:`Compute service (nova)` * :term:`Networking service` (:term:`neutron`) diff --git a/doc/common/glossary.rst b/doc/common/glossary.rst index a35b7976ef..618ef7d6cd 100644 --- a/doc/common/glossary.rst +++ b/doc/common/glossary.rst @@ -801,16 +801,16 @@ C compression for things such as Object Storage objects or Image service VM images. - Compute service + Compute service (nova) + The OpenStack core project that implements services and associated + libraries to provide massively-scalable, on-demand, self-service + access to compute resources, including bare metal, virtual machines, + and containers. - The OpenStack core project that provides compute services. The - project name of Compute service is nova. + Compute API (Nova API) - Compute API - - The nova-api daemon - provides access to nova services. Can communicate with other APIs, - such as the Amazon EC2 API. + The nova-api daemon provides access to nova services. Can communicate with + other APIs, such as the Amazon EC2 API. compute controller @@ -2576,11 +2576,11 @@ N nova - OpenStack project that provides compute services. + Codename for OpenStack :term:`Compute service `. Nova API - Alternative term for the Compute API. + Alternative term for the :term:`Compute API `. nova-network diff --git a/doc/networking-guide/source/intro.rst b/doc/networking-guide/source/intro.rst index 2fec27d3ff..74c5ade25d 100644 --- a/doc/networking-guide/source/intro.rst +++ b/doc/networking-guide/source/intro.rst @@ -29,7 +29,7 @@ components: * OpenStack :term:`Identity service` (keystone) is used for authentication and authorization of API requests. -* OpenStack :term:`Compute service` (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 diff --git a/doc/ops-guide/source/arch-storage.rst b/doc/ops-guide/source/arch-storage.rst index 1f2ac6cdf1..73af586c72 100644 --- a/doc/ops-guide/source/arch-storage.rst +++ b/doc/ops-guide/source/arch-storage.rst @@ -12,10 +12,10 @@ your cloud. It's important to understand the distinction between Ephemeral Storage ~~~~~~~~~~~~~~~~~ -If you deploy only the OpenStack :term:`Compute service` (nova), your users do -not have access to any form of persistent storage by default. The disks -associated with VMs are "ephemeral," meaning that (from the user's point -of view) they effectively disappear when a virtual machine is +If you deploy only the OpenStack :term:`Compute service (nova)`, +your users do not have access to any form of persistent storage by default. +The disks associated with VMs are "ephemeral," meaning that (from the user's +point of view) they effectively disappear when a virtual machine is terminated. Persistent Storage