openstack/openstack-manuals
Code Issues Proposed changes

[glossary] Remove acronyms [O-Z]

Browse Source 
- Remove acronym-only entries starting with [O-Z].
- Consolodate duplicate entries.
- Resolve glossary references

Change-Id: I265d4fb6b8a9e8e92501dd8878d47375c3435781
Implements: blueprint improve-glossary-usage
This commit is contained in:
Emma Foley 2016-08-15 17:12:33 +01:00 committed by KATO Tomoyuki
parent 0e39378c21
commit 5be2d01514
3 changed files with 9 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
doc/common/glossary.rst
View File

@ -3517,10 +3517,9 @@ S
OpenStack project that provides a Software Development
Lifecycle Automation service.
SPICE
Simple Protocol for Independent Computing Environments (SPICE)
The Simple Protocol for Independent Computing Environments
(SPICE) provides remote desktop access to guest virtual machines. It
SPICE provides remote desktop access to guest virtual machines. It
is an alternative to VNC. SPICE is supported by OpenStack.
spread-first scheduler
@ -3815,15 +3814,6 @@ V
Unique ID assigned to each Networking VIF.
VIP
The primary load balancing configuration object.
Specifies the virtual IP address and port where client traffic
is received. Also defines other details such as the load
balancing method to be used, protocol, and so on. This entity
is sometimes known in load-balancing products as a virtual
server, vserver, or listener.
Virtual Central Processing Unit (vCPU)
Subdivides physical CPUs. Instances can then use those
@ -3834,7 +3824,7 @@ V
One of the VM image disk formats supported by Image
service.
VXLAN
Virtual Extensible LAN (VXLAN)
A network virtualization technology that attempts to reduce the
scalability problems associated with large cloud computing
@ -3846,7 +3836,7 @@ V
One of the VM image disk formats supported by Image
service.
virtual IP
virtual IP address (VIP)
An Internet Protocol (IP) address configured on the load
balancer for use by clients connecting to a service that is load

2
doc/ha-guide/source/intro-ha-concepts.rst
View File

@ -115,7 +115,7 @@ Stateful services may be configured as active/passive or active/active:
A typical active/passive installation for a stateful service maintains
a replacement resource that can be brought online when required.
Requests are handled using a :term:`virtual IP` address (VIP) that
Requests are handled using a :term:`virtual IP address (VIP)` that
facilitates returning to service with minimal reconfiguration.
A separate application (such as Pacemaker or Corosync) monitors
these services, bringing the backup online as necessary.

7
doc/install-guide/source/overview.rst
View File

@ -225,9 +225,10 @@ Networking Option 2: Self-service networks
The self-service networks option augments the provider networks option
with layer-3 (routing) services that enable
:term:`self-service` networks using overlay segmentation methods such
as :term:`VXLAN`. Essentially, it routes virtual networks to physical networks
using :term:`NAT<Network Address Translation (NAT)>`. Additionally, this option
provides the foundation for advanced services such as LBaaS and FWaaS.
as :term:`VXLAN <Virtual Extensible LAN (VXLAN)>`. Essentially, it routes
virtual networks to physical networks using :term:`NAT<Network Address
Translation (NAT)>`. Additionally, this option provides the foundation for
advanced services such as LBaaS and FWaaS.
.. _figure-network2-services: