starlingx/docs
Code Issues Proposed changes

Backport r5 fix to master

Browse Source 
Backporting some typos and formatting issues fixed during cherrypick.
See: https://review.opendev.org/c/starlingx/docs/+/816651

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: I670bb29ade8f146af1bd68b13e3db6e2b9a75481
This commit is contained in:
Ron Stone 2021-11-04 09:44:26 -04:00
parent e7690205f0
commit 688f8eb410
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/source/node_management/kubernetes/node_interfaces/interface-ip-address-provisioning-using-the-cli.rst
View File

@ -35,12 +35,12 @@ The procedure for adding an IP address depends on the interface type.
~(keystone_admin)$ systemhost-if-add <hostname> -V --vlan_id -c --ifclass <interfacename> <ethname>
**Virtual Function interfaces**
You can create an SROIV VF interface on top of an existing SROIV VF
You can create an |SRIOV| |VF| interface on top of an existing |SRIOV| |VF|
interface in order to configure a subset of virtual functions with
different drivers. For example, if the ethernet SR-IOV interface is
configured with the kernel VF driver, you can create a VF interface to
different drivers. For example, if the ethernet |SRIOV| interface is
configured with the kernel VF driver, you can create a |VF| interface to
configure a subset of virtual functions with the vfio driver that can be
used with userspace libraries such as DPDK.
used with userspace libraries such as |DPDK|.
.. code-block:: none
@ -57,6 +57,7 @@ They can only be modified to use different physical ports when required.
On the second worker and storage nodes, the Ethernet interface for the
internal management network is attached automatically to support
installation using |PXE| booting.
On the initial controller node, the interface for the internal management
network is attached according to the settings specified during the
Ansible bootstrapping of the system.
@ -77,7 +78,7 @@ They can only be modified to use different physical ports when required.
where the following options are available:
``node``
The name or UUID of the worker node.
The name or |UUID| of the worker node.
``ifname``
The name of the interface.