[network] Preparation for Liberty/Mitaka updates

Prepare the networking guide for Liberty/Mitaka updates as
follows:

1) Change "legacy" to "classic" to provide a more positive
   connotation of such scenarios. Legacy should refer to
   nova-network.
2) Replace underscore with hyphen in filenames to meet
   conventions.
3) Replace :doc: with :ref: to minimize impact of future
   file renames.

Change-Id: I95bdd84b4a01cd9cbd06cad66821ad810295394f
backport: Liberty
This commit is contained in:
Matthew Kassawara 2016-01-13 17:06:03 -07:00
parent e5e6bbd137
commit 6e74e65392
107 changed files with 116 additions and 102 deletions

View File

@ -0,0 +1,20 @@
======================
Advanced configuration
======================
.. toctree::
:maxdepth: 2
adv-config-operational.rst
adv-config-network-rbac.rst
adv-config-lbaas.rst
adv-config-fwaas.rst
adv-config-vpnaas.rst
adv-config-service-chaining.rst
adv-config-qos.rst
adv-config-group-policy.rst
adv-config-debugging.rst
adv-config-ipv6.rst
adv-config-sriov.rst
adv-config-ipam.rst
adv-config-availability-zone.rst

View File

@ -1,20 +0,0 @@
======================
Advanced configuration
======================
.. toctree::
:maxdepth: 2
adv_config_operational.rst
adv_config_network_rbac.rst
adv_config_LBaaS.rst
adv_config_FwaaS.rst
adv_config_VPNaaS.rst
adv_config_service_chaining.rst
adv_config_qos.rst
adv_config_group_policy.rst
adv_config_debugging.rst
adv_config_ipv6.rst
adv_config_sriov.rst
adv_config_ipam.rst
adv_config_availability_zone.rst

View File

@ -9,5 +9,5 @@ the `Configuration Reference
.. toctree::
:maxdepth: 2
config_server.rst
config_ml2_plug_in.rst
config-server.rst
config-ml2-plug-in.rst

View File

@ -5,10 +5,10 @@ Deployment scenarios
.. toctree::
:maxdepth: 2
scenario_legacy_ovs.rst
scenario_legacy_lb.rst
scenario_dvr_ovs.rst
scenario_l3ha_ovs.rst
scenario_l3ha_lb.rst
scenario_provider_ovs.rst
scenario_provider_lb.rst
scenario-classic-ovs.rst
scenario-classic-lb.rst
scenario-dvr-ovs.rst
scenario-l3ha-ovs.rst
scenario-l3ha-lb.rst
scenario-provider-ovs.rst
scenario-provider-lb.rst

View File

Before

Width:  |  Height:  |  Size: 104 KiB

After

Width:  |  Height:  |  Size: 104 KiB

View File

Before

Width:  |  Height:  |  Size: 40 KiB

After

Width:  |  Height:  |  Size: 40 KiB

View File

Before

Width:  |  Height:  |  Size: 60 KiB

After

Width:  |  Height:  |  Size: 60 KiB

View File

Before

Width:  |  Height:  |  Size: 26 KiB

After

Width:  |  Height:  |  Size: 26 KiB

View File

Before

Width:  |  Height:  |  Size: 67 KiB

After

Width:  |  Height:  |  Size: 67 KiB

View File

Before

Width:  |  Height:  |  Size: 21 KiB

After

Width:  |  Height:  |  Size: 21 KiB

View File

Before

Width:  |  Height:  |  Size: 76 KiB

After

Width:  |  Height:  |  Size: 76 KiB

View File

Before

Width:  |  Height:  |  Size: 25 KiB

After

Width:  |  Height:  |  Size: 25 KiB

View File

Before

Width:  |  Height:  |  Size: 140 KiB

After

Width:  |  Height:  |  Size: 140 KiB

View File

Before

Width:  |  Height:  |  Size: 47 KiB

After

Width:  |  Height:  |  Size: 47 KiB

View File

Before

Width:  |  Height:  |  Size: 73 KiB

After

Width:  |  Height:  |  Size: 73 KiB

View File

Before

Width:  |  Height:  |  Size: 26 KiB

After

Width:  |  Height:  |  Size: 26 KiB

View File

Before

Width:  |  Height:  |  Size: 167 KiB

After

Width:  |  Height:  |  Size: 167 KiB

View File

Before

Width:  |  Height:  |  Size: 53 KiB

After

Width:  |  Height:  |  Size: 53 KiB

View File

Before

Width:  |  Height:  |  Size: 162 KiB

After

Width:  |  Height:  |  Size: 162 KiB

View File

Before

Width:  |  Height:  |  Size: 53 KiB

After

Width:  |  Height:  |  Size: 53 KiB

View File

Before

Width:  |  Height:  |  Size: 88 KiB

After

Width:  |  Height:  |  Size: 88 KiB

View File

Before

Width:  |  Height:  |  Size: 30 KiB

After

Width:  |  Height:  |  Size: 30 KiB

View File

Before

Width:  |  Height:  |  Size: 115 KiB

After

Width:  |  Height:  |  Size: 115 KiB

View File

Before

Width:  |  Height:  |  Size: 38 KiB

After

Width:  |  Height:  |  Size: 38 KiB

View File

Before

Width:  |  Height:  |  Size: 65 KiB

After

Width:  |  Height:  |  Size: 65 KiB

View File

Before

Width:  |  Height:  |  Size: 21 KiB

After

Width:  |  Height:  |  Size: 21 KiB

View File

Before

Width:  |  Height:  |  Size: 71 KiB

After

Width:  |  Height:  |  Size: 71 KiB

View File

Before

Width:  |  Height:  |  Size: 24 KiB

After

Width:  |  Height:  |  Size: 24 KiB

View File

Before

Width:  |  Height:  |  Size: 65 KiB

After

Width:  |  Height:  |  Size: 65 KiB

View File

Before

Width:  |  Height:  |  Size: 21 KiB

After

Width:  |  Height:  |  Size: 21 KiB

View File

Before

Width:  |  Height:  |  Size: 90 KiB

After

Width:  |  Height:  |  Size: 90 KiB

View File

Before

Width:  |  Height:  |  Size: 30 KiB

After

Width:  |  Height:  |  Size: 30 KiB

View File

Before

Width:  |  Height:  |  Size: 242 KiB

After

Width:  |  Height:  |  Size: 242 KiB

View File

Before

Width:  |  Height:  |  Size: 83 KiB

After

Width:  |  Height:  |  Size: 83 KiB

View File

Before

Width:  |  Height:  |  Size: 166 KiB

After

Width:  |  Height:  |  Size: 166 KiB

View File

Before

Width:  |  Height:  |  Size: 56 KiB

After

Width:  |  Height:  |  Size: 56 KiB

View File

Before

Width:  |  Height:  |  Size: 195 KiB

After

Width:  |  Height:  |  Size: 195 KiB

View File

Before

Width:  |  Height:  |  Size: 66 KiB

After

Width:  |  Height:  |  Size: 66 KiB

View File

Before

Width:  |  Height:  |  Size: 200 KiB

After

Width:  |  Height:  |  Size: 200 KiB

View File

Before

Width:  |  Height:  |  Size: 65 KiB

After

Width:  |  Height:  |  Size: 65 KiB

View File

Before

Width:  |  Height:  |  Size: 84 KiB

After

Width:  |  Height:  |  Size: 84 KiB

View File

Before

Width:  |  Height:  |  Size: 28 KiB

After

Width:  |  Height:  |  Size: 28 KiB

View File

Before

Width:  |  Height:  |  Size: 124 KiB

After

Width:  |  Height:  |  Size: 124 KiB

View File

Before

Width:  |  Height:  |  Size: 42 KiB

After

Width:  |  Height:  |  Size: 42 KiB

View File

Before

Width:  |  Height:  |  Size: 65 KiB

After

Width:  |  Height:  |  Size: 65 KiB

View File

Before

Width:  |  Height:  |  Size: 21 KiB

After

Width:  |  Height:  |  Size: 21 KiB

View File

@ -26,13 +26,13 @@ Contents
:maxdepth: 2
common/conventions.rst
intro_networking.rst
intro_os_networking.rst
intro-networking.rst
intro-os-networking.rst
config.rst
deploy.rst
migration.rst
miscellaneous.rst
adv_config.rst
adv-config.rst
common/app_support.rst

View File

@ -37,8 +37,8 @@ components:
.. toctree::
:maxdepth: 2
intro_basic_networking.rst
intro_networking_components.rst
intro_tunnel_technologies.rst
intro_network_namespaces.rst
intro_network_address_translation.rst
intro-basic-networking.rst
intro-networking-components.rst
intro-tunnel-technologies.rst
intro-network-namespaces.rst
intro-network-address-translation.rst

View File

@ -5,5 +5,5 @@ Introduction to OpenStack Networking (neutron)
.. toctree::
:maxdepth: 2
intro_os_networking_overview.rst
intro_os_networking_service.rst
intro-os-networking-overview.rst
intro-os-networking-service.rst

View File

@ -2,10 +2,10 @@
Legacy to L3 HA
===============
This section describes the process of migrating from a legacy router to an L3
This section describes the process of migrating from a classic router to an L3
HA router, which is available starting from the Mitaka release.
Similar to the legacy scenario, all network traffic on a project network that
Similar to the classic scenario, all network traffic on a project network that
requires routing actively traverses only one network node regardless of the
quantity of network nodes providing HA for the router. Therefore, this
high-availability implementation primarily addresses failure situations instead
@ -13,8 +13,8 @@ of bandwidth constraints that limit performance. However, it supports random
distribution of routers on different network nodes to reduce the chances of
bandwidth constraints and to improve scaling.
This section summarizes parts of :doc:`scenario_l3ha_ovs` and
:doc:`scenario_l3ha_lb`. For details regarding needed infrastructure and
This section summarizes parts of :ref:`scenario-l3ha-ovs` and
:ref:`scenario-l3ha-lb`. For details regarding needed infrastructure and
configuration to allow actual L3 HA deployment, read the relevant guide
before continuing with the migration process.
@ -100,8 +100,8 @@ Here is the router we have used in our demonstration:
L3 HA to Legacy
~~~~~~~~~~~~~~~
To return to legacy mode, you turn down the router again, turning off L3 HA and
starting the router again
To return to classic mode, you turn down the router again, turning off L3 HA
and starting the router again
.. warning::

View File

@ -5,7 +5,7 @@ Migration
.. toctree::
:maxdepth: 2
migration_nova_network_to_neutron.rst
migration_legacy_to_dvr.rst
migration_legacy_to_L3_HA.rst
migration-nova-network-to-neutron.rst
migration-classic-to-dvr.rst
migration-classic-to-l3ha.rst

View File

@ -5,5 +5,5 @@ Miscellaneous
.. toctree::
:maxdepth: 2
misc_libvirt
misc_add_ha_for_DHCP.rst
misc-libvirt.rst
misc-add-ha-for-dhcp.rst

View File

@ -1,11 +1,13 @@
==================================
Scenario: Legacy with Linux Bridge
==================================
.. _scenario-classic-lb:
This scenario describes a legacy (basic) implementation of the
OpenStack Networking service using the ML2 plug-in with Linux bridge.
===================================
Scenario: Classic with Linux Bridge
===================================
The legacy implementation contributes the networking portion of self-service
This scenario describes a classic implementation of the OpenStack
Networking service using the ML2 plug-in with Linux bridge.
The classic implementation contributes the networking portion of self-service
virtual data center infrastructure by providing a method for regular
(non-privileged) users to manage virtual networks within a project and
includes the following components:
@ -92,13 +94,13 @@ the tunnel network uses 10.0.1.0/24, and the external network uses
203.0.113.0/24. The VLAN network does not require an IP address range
because it only handles layer-2 connectivity.
.. image:: figures/scenario-legacy-hw.png
.. image:: figures/scenario-classic-hw.png
:alt: Hardware layout
.. image:: figures/scenario-legacy-networks.png
.. image:: figures/scenario-classic-networks.png
:alt: Network layout
.. image:: figures/scenario-legacy-lb-services.png
.. image:: figures/scenario-classic-lb-services.png
:alt: Service layout
.. note::
@ -144,7 +146,7 @@ OpenStack services - compute nodes
Architecture
~~~~~~~~~~~~
The legacy architecture provides basic virtual networking components in
The classic architecture provides basic virtual networking components in
your environment. Routing among project and external networks resides
completely on the network node. Although more simple to deploy than
other architectures, performing all functions on the network node
@ -153,7 +155,7 @@ Consider deploying DVR or L3 HA architectures in production environments
to provide redundancy and increase performance. However, the DVR architecture
requires Open vSwitch.
.. image:: figures/scenario-legacy-general.png
.. image:: figures/scenario-classic-general.png
:alt: Architecture overview
The network node contains the following network components:
@ -169,10 +171,10 @@ The network node contains the following network components:
metadata agent.
#. Metadata agent handling metadata operations for instances.
.. image:: figures/scenario-legacy-lb-network1.png
.. image:: figures/scenario-classic-lb-network1.png
:alt: Network node components - overview
.. image:: figures/scenario-legacy-lb-network2.png
.. image:: figures/scenario-classic-lb-network2.png
:alt: Network node components - connectivity
The compute nodes contain the following network components:
@ -181,10 +183,10 @@ The compute nodes contain the following network components:
them, and interaction via virtual ports with other network components
such as namespaces, security groups, and underlying interfaces.
.. image:: figures/scenario-legacy-lb-compute1.png
.. image:: figures/scenario-classic-lb-compute1.png
:alt: Compute node components - overview
.. image:: figures/scenario-legacy-lb-compute2.png
.. image:: figures/scenario-classic-lb-compute2.png
:alt: Compute node components - connectivity
Packet flow
@ -291,7 +293,7 @@ The following steps involve the network node:
Return traffic follows similar steps in reverse.
.. image:: figures/scenario-legacy-lb-flowns1.png
.. image:: figures/scenario-classic-lb-flowns1.png
:alt: Network traffic flow - north/south with fixed IP address
Case 2: North-south for instances with a floating IP address
@ -384,7 +386,7 @@ The following steps involve compute node 1:
Return traffic follows similar steps in reverse.
.. image:: figures/scenario-legacy-lb-flowns2.png
.. image:: figures/scenario-classic-lb-flowns2.png
:alt: Network traffic flow - north/south with a floating IP address
Case 3: East-west for instances on different networks
@ -467,7 +469,7 @@ The following steps involve compute node 2:
Return traffic follows similar steps in reverse.
.. image:: figures/scenario-legacy-lb-flowew1.png
.. image:: figures/scenario-classic-lb-flowew1.png
:alt: Network traffic flow - east/west for instances on different networks
Case 4: East-west for instances on the same network
@ -524,7 +526,7 @@ The following steps involve compute node 2:
Return traffic follows similar steps in reverse.
.. image:: figures/scenario-legacy-lb-flowew2.png
.. image:: figures/scenario-classic-lb-flowew2.png
:alt: Network traffic flow - east/west for instances on the same network
Example configuration

Some files were not shown because too many files have changed in this diff Show More