From 688f8eb4104f6629c235540f20d2bb4ddaa9d967 Mon Sep 17 00:00:00 2001 From: Ron Stone Date: Thu, 4 Nov 2021 09:44:26 -0400 Subject: [PATCH] Backport r5 fix to master Backporting some typos and formatting issues fixed during cherrypick. See: https://review.opendev.org/c/starlingx/docs/+/816651 Signed-off-by: Ron Stone Change-Id: I670bb29ade8f146af1bd68b13e3db6e2b9a75481 --- ...nterface-ip-address-provisioning-using-the-cli.rst | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/doc/source/node_management/kubernetes/node_interfaces/interface-ip-address-provisioning-using-the-cli.rst b/doc/source/node_management/kubernetes/node_interfaces/interface-ip-address-provisioning-using-the-cli.rst index 31b614ef1..9219fcfe3 100644 --- a/doc/source/node_management/kubernetes/node_interfaces/interface-ip-address-provisioning-using-the-cli.rst +++ b/doc/source/node_management/kubernetes/node_interfaces/interface-ip-address-provisioning-using-the-cli.rst @@ -35,12 +35,12 @@ The procedure for adding an IP address depends on the interface type. ~(keystone_admin)$ systemhost-if-add -V --vlan_id -c --ifclass **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.