openstack
/
openstack-manuals
Code Issues Proposed changes

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
parent f9099a1b77 a93f57edf4
commit 83d3ecfe0c
5 changed files with 26 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/arch-design/source/compute-focus-technical-considerations.rst
View File

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

2
doc/arch-design/source/generalpurpose-technical-considerations.rst
View File

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

17
doc/common/glossary.rst
View File

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

8
doc/networking-guide/source/intro.rst
View File

@ -4,10 +4,10 @@
Introduction
============
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
The OpenStack :term:`Networking service <Networking service (neutron)>`
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
networking infrastructure, including networks, switches, subnets, and
routers for devices managed by the OpenStack Compute service
(nova). Advanced services such as firewalls or :term:`virtual private

22
doc/ops-guide/source/ops-maintenance-slow.rst
View File

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