[glossary] Consolodate project codenames [nova]
- Combine "Compute service" entry with "nova" entry - Rename "Compute service" to "Compute service (Nova)" - Link "nova" to "Compute service (nova)" - Make sure description matches project.yaml - Combine "Compute API" and "Nova API" - Resolve glossary references Change-Id: I89101e6bcf7563bc325858a0805884d33673d4d3 Implements: blueprint improve-glossary-usage
This commit is contained in:
parent
a5bf8d31a1
commit
1ea26029b6
@ -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
|
||||
|
@ -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)
|
||||
|
||||
|
@ -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 <Compute API (Nova API)>`
|
||||
|
||||
Leveraging existing monitoring systems is an effective check to ensure
|
||||
OpenStack environments can be monitored.
|
||||
|
@ -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`)
|
||||
|
||||
|
@ -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 <Compute service (nova)>`.
|
||||
|
||||
Nova API
|
||||
|
||||
Alternative term for the Compute API.
|
||||
Alternative term for the :term:`Compute API <Compute API (nova API)>`.
|
||||
|
||||
nova-network
|
||||
|
||||
|
@ -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
|
||||
|
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user