Fix link aggregation mode option
Correct AEMODE option in LAG interface config section Editorial cleanup (deleted “needs info” note, tabs changed to spaces, wrap lines @79). Closes-Bug: 1887519 Change-Id: I81d6c4eabbd4fc9c7f7e7e1678e0da970041ccc7 Signed-off-by: MCamp859 <maryx.camp@intel.com>
This commit is contained in:
parent
965e7aebe6
commit
6386d025b6
@ -2,13 +2,7 @@
|
||||
Host Interface and Network Configuration
|
||||
========================================
|
||||
|
||||
.. note::
|
||||
|
||||
This page needs additional content! See the story for additional information
|
||||
about what is needed: `Add Host Interface and Networking Configuration Guide <https://storyboard.openstack.org/#!/story/2006865>`_
|
||||
|
||||
For information about contributing to the StarlingX documentation, see the
|
||||
:doc:`/contributor/doc_contribute_guide`.
|
||||
This guide describes the following:
|
||||
|
||||
.. contents::
|
||||
:local:
|
||||
@ -134,7 +128,7 @@ command:
|
||||
Replace parameters with values suitable to your installation. Parameters are:
|
||||
|
||||
``AEMODE``
|
||||
The link aggregation mode (active-backup, balanced, 802.3ad).
|
||||
The link aggregation mode (active_standby, balanced, 802.3ad).
|
||||
|
||||
``ETH_NAME_1``, ``ETH_NAME_2``
|
||||
The names or UUIDs of the member Ethernet interfaces.
|
||||
@ -172,10 +166,11 @@ VLAN (tagged) on the same port.
|
||||
|
||||
The cluster host network is required by all deployment configurations to support
|
||||
a Kubernetes cluster. It is used for private container-to-container networking
|
||||
within a cluster. It can be used for external connectivity of container workloads.
|
||||
If the cluster host network is not used for external connectivity of container
|
||||
workloads, then either the OAM port or other configured ports on both the
|
||||
controller and worker nodes can be used for connectivity to external networks.
|
||||
within a cluster. It can be used for external connectivity of container
|
||||
workloads. If the cluster host network is not used for external connectivity of
|
||||
container workloads, then either the OAM port or other configured ports on both
|
||||
the controller and worker nodes can be used for connectivity to external
|
||||
networks.
|
||||
|
||||
The OAM network is required for external control and board management access. It
|
||||
can be used for container payload external connectivity, depending on
|
||||
@ -196,7 +191,8 @@ Replace parameters with values suitable to your installation. Parameters are:
|
||||
A name for the interface.
|
||||
|
||||
``NETWORK``
|
||||
The name or ID of the platform network to which the interface will be assigned.
|
||||
The name or ID of the platform network to which the interface will
|
||||
be assigned.
|
||||
|
||||
*************
|
||||
Data networks
|
||||
@ -257,8 +253,12 @@ Replace parameters with values suitable to your installation. Parameters are:
|
||||
A description of the data network.
|
||||
|
||||
``MTU``
|
||||
The MTU of the data network. NOTE: To attach to the data network, data
|
||||
interfaces must be configured with an equal or larger MTU.
|
||||
The MTU of the data network.
|
||||
|
||||
.. note::
|
||||
|
||||
To attach to the data network, data interfaces must be configured
|
||||
with an equal or larger MTU.
|
||||
|
||||
``PORT``
|
||||
The port of the data network.
|
||||
|
Loading…
x
Reference in New Issue
Block a user