Merge "[glossary] Consolodate project codenames [neutron]"

This commit is contained in:
Jenkins 2016-09-13 22:22:00 +00:00 committed by Gerrit Code Review
commit 83d3ecfe0c
5 changed files with 26 additions and 25 deletions

View File

@ -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 service` (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

View File

@ -346,7 +346,7 @@ OpenStack core services recommended in a general purpose cloud are:
* :term:`Compute service (nova)` * :term:`Compute service (nova)`
* :term:`Networking service` (:term:`neutron`) * :term:`Networking service (neutron)`
* :term:`Image service` (:term:`glance`) * :term:`Image service` (:term:`glance`)

View File

@ -2508,25 +2508,26 @@ N
services such as giving an IP address to a booting nova services such as giving an IP address to a booting nova
instance. instance.
Networking service Networking service (neutron)
A core OpenStack project that provides a network connectivity The OpenStack projects which implements services and associated
abstraction layer to OpenStack Compute. The project name of Networking libraries to provide on-demand, scalable, and technology-agnostic
is neutron. network abstraction.
Networking API Networking API (Neutron API)
API used to access OpenStack Networking. Provides an extensible API used to access OpenStack Networking. Provides an extensible
architecture to enable custom plug-in creation. architecture to enable custom plug-in creation.
neutron neutron
A core OpenStack project that provides a network connectivity Codename for OpenStack :term:`Networking service <Networking Service
abstraction layer to OpenStack Compute. (neutron)>`.
neutron API neutron API
An alternative name for Networking API. An alternative name for :term:`Networking API <Networking API
(Neutron API)>`.
neutron manager neutron manager

View File

@ -4,10 +4,10 @@
Introduction Introduction
============ ============
The OpenStack :term:`Networking service` provides an API that allows users The OpenStack :term:`Networking service <Networking service (neutron)>`
to set up and define network connectivity and addressing in the provides an API that allows users to set up and define network connectivity
cloud. The project code-name for Networking services is neutron. and addressing in the cloud. The project code-name for Networking services is
OpenStack Networking handles the creation and management of a virtual neutron. OpenStack Networking handles the creation and management of a virtual
networking infrastructure, including networks, switches, subnets, and networking infrastructure, including networks, switches, subnets, and
routers for devices managed by the OpenStack Compute service routers for devices managed by the OpenStack Compute service
(nova). Advanced services such as firewalls or :term:`virtual private (nova). Advanced services such as firewalls or :term:`virtual private

View File

@ -51,17 +51,17 @@ services, SQL is used extensively.
OpenStack Networking service OpenStack Networking service
~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Slowness in the OpenStack :term:`Networking service` can be caused by services Slowness in the OpenStack :term:`Networking service <Networking service
that it relies upon, but it can also be related to either physical or (neutron)>` can be caused by services that it relies upon, but it can
virtual networking. For example: network namespaces that do not exist or also be related to either physical or virtual networking. For example:
are not tied to interfaces correctly; DHCP daemons that have hung or are network namespaces that do not exist or are not tied to interfaces correctly;
not running; a cable being physically disconnected; a switch not being DHCP daemons that have hung or are not running; a cable being physically
configured correctly. When debugging Networking service problems, begin disconnected; a switch not being configured correctly. When debugging
by verifying all physical networking functionality (switch Networking service problems, begin by verifying all physical networking
configuration, physical cabling, etc.). After the physical networking is functionality (switch configuration, physical cabling, etc.). After the
verified, check to be sure all of the Networking services are running physical networking is verified, check to be sure all of the Networking
(neutron-server, neutron-dhcp-agent, etc.), then check on AMQP and SQL services are running (neutron-server, neutron-dhcp-agent, etc.), then check
back ends. on AMQP and SQL back ends.
AMQP broker AMQP broker
~~~~~~~~~~~ ~~~~~~~~~~~