Merge "Remove VLAN splinters"
This commit is contained in:
@@ -20,7 +20,5 @@ Some specific considerations:
|
||||
- In particular, the CentOS version used for OpenStack
|
||||
does not include native support for VLANs
|
||||
while the Ubuntu version does.
|
||||
In order to use VLANs on CentOS based nodes,
|
||||
you must configure :ref:`vlan-splinters-ug`.
|
||||
- CentOS supports .rpm packages; Ubuntu supports .deb packages.
|
||||
|
||||
|
||||
@@ -53,8 +53,6 @@ have no effect on the Operating System role:
|
||||
that connect this node to the rest of the environment
|
||||
need to be defined.
|
||||
|
||||
- :ref:`VLAN splinters<vlan-splinters-ug>`
|
||||
|
||||
- :ref:`Debug logging<debug-level-ug>`
|
||||
|
||||
- :ref:`Syslog<syslog-ug>`
|
||||
|
||||
@@ -26,7 +26,7 @@ closer look at this substructure. The value of the 'network_scheme' key is a has
|
||||
the following keys:
|
||||
|
||||
* **interfaces** - A hash of NICs and their low-level/physical parameters.
|
||||
You can set an MTU and the 'VLAN splinters' feature here.
|
||||
You can set an MTU feature here.
|
||||
* **provider** - Set to 'ovs' for Neutron.
|
||||
* **endpoints** - A hash of network ports (OVS ports or NICs) and their IP
|
||||
settings.
|
||||
|
||||
@@ -41,8 +41,6 @@ Here are the the available options:
|
||||
# OVS port properties to modify them in OVS DB
|
||||
"interface_properties": [], # [optional; default: []] a list of additional
|
||||
# OVS interface properties to modify them in OVS DB
|
||||
"vlan_splinters": false, # [optional; default: false] enable 'vlan splinters'
|
||||
# feature for this interface
|
||||
},
|
||||
{
|
||||
"action": "add-bond", # type of primitive
|
||||
|
||||
@@ -17,12 +17,6 @@ Neutron with VLAN segmentation,
|
||||
and Neutron GRE has VLAN tags
|
||||
on the management, storage, and public networks.
|
||||
|
||||
The version of CentOS that Fuel deploys
|
||||
has poor support for VLAN tagged packets
|
||||
so work-aronds are provided to improve the VLAN support
|
||||
when using CentOS;
|
||||
see :ref:`vlan-splinters-ug`.
|
||||
|
||||
For more information:
|
||||
|
||||
- :ref:`neutron-vlan-ovs-arch` describes the Neutron VLAN topology.
|
||||
@@ -32,8 +26,3 @@ For more information:
|
||||
- :ref:`nova-vlan-arch` describes the Nova-network VLAN topology.
|
||||
:ref:`nova-config-vlan` provides examples
|
||||
to help you plan your NIC assignment for this topology.
|
||||
|
||||
- :ref:`vlan-splinters-ug` gives instructions for setting up
|
||||
VLAN splinters, which improve the performance of VLANs
|
||||
when using the CentOS operating system
|
||||
for your OpenStack nodes.
|
||||
|
||||
@@ -32,10 +32,6 @@ The "Settings" tab provides configuration access to:
|
||||
and which scheduler to use to determine how to dispatch
|
||||
compute and volume requests.
|
||||
|
||||
* Configure VLAN Splinters for environments
|
||||
running CentOS on the target nodes
|
||||
with the Neutron VLAN network topology.
|
||||
|
||||
After you modify values on the "Settings" screen,
|
||||
click the "Load Settings" button at the bottom of the screen.
|
||||
If you want to go back to the Fuel default values,
|
||||
@@ -49,7 +45,6 @@ you can click on the "Load Defaults" button at the bottom of the screen.
|
||||
.. include:: /pages/user-guide/config-environment/settings/3300-scheduler.rst
|
||||
.. include:: /pages/user-guide/config-environment/settings/3400-qcow.rst
|
||||
.. include:: /pages/user-guide/config-environment/settings/2590-public-key.rst
|
||||
.. include:: /pages/user-guide/config-environment/settings/3500-vlan-splinters.rst
|
||||
.. include:: /pages/user-guide/config-environment/settings/3525-kernel-parameters.rst
|
||||
.. include:: /pages/user-guide/config-environment/settings/3550-syslog.rst
|
||||
.. include:: /pages/user-guide/config-environment/settings/3600-mellanox-neutron.rst
|
||||
|
||||
@@ -1,54 +0,0 @@
|
||||
|
||||
.. raw:: pdf
|
||||
|
||||
PageBreak
|
||||
|
||||
.. _vlan-splinters-ug:
|
||||
|
||||
VLAN splinters
|
||||
++++++++++++++
|
||||
|
||||
VLAN splinters are provided so that CentOS deployments
|
||||
can support Neutron VLANS or GRE
|
||||
(with VLAN tags on the management, storage, or public networks).
|
||||
The kernel used for the CentOS version used with OpenStack
|
||||
is based on a pre-3.3 kernel
|
||||
and so has poor support for VLAN tagged packets
|
||||
moving through :ref:`ovs-term` bridges.
|
||||
Without VLAN splinters,
|
||||
CentOS deployments may experience poor performance issues,
|
||||
intermittent connectivity problems,
|
||||
situations where one VLAN is working but others are not,
|
||||
or a total failure to pass traffic.
|
||||
Ubuntu deployments use a kernel that includes strong VLAN support
|
||||
and so are not affected by these issues.
|
||||
|
||||
|
||||
.. image:: /_images/user_screen_shots/settings-vlan-splinters.png
|
||||
:width: 90%
|
||||
|
||||
You can select either the soft trunks or hard trunks mode:
|
||||
|
||||
* The **soft trunks mode** configures OVS to enable splinters
|
||||
and attempts to automatically detect in-use VLANs.
|
||||
This provides the least amount of performance overhead
|
||||
but the traffic may not be passed onto the OVS bridge in some edge cases.
|
||||
|
||||
* The **hard trunks mode** also configures OVS to enable splinters
|
||||
but uses an explicitly defined list of all VLANs across all interfaces.
|
||||
This should prevent the occasional failures associated with the soft mode
|
||||
but requires that corresponding tags be created on all of the interfaces.
|
||||
This introduces additional performance overhead.
|
||||
You should use fewer than 50 VLANs
|
||||
if you run the Neutron VLAN mode and use the hard trunks mode.
|
||||
|
||||
Fuel also provides the option
|
||||
of using the experimental Fedora long-term support 3.10 kernel.
|
||||
Using this kernel may allow you to use VLAN tagged packets
|
||||
without using VLAN splinters,
|
||||
which can provide significant performance advantages.
|
||||
However, this option has had minimal testing
|
||||
and may invalidate your agreements with your hardware vendor.
|
||||
See :ref:`ovs-arch`
|
||||
for more information about using Open vSwitch.
|
||||
|
||||
Reference in New Issue
Block a user