Node Management and Distributed cloud Guide updates

Global Pass Upgrades

Added content from emails attached to ticket and sharepoint

Pacth 01: inputs from email by Greg

Patch 03: Created new section for subcloud group
          updated table 1 shared system configurations

Patch 04: corrected typos (Mary's comments)

Patch 05: solved merged conflict

patch 06: removed broken link

Story: TBD
Task: TBD



Signed-off-by: Adil <mohamed.adilassakkali@windriver.com>
Change-Id: I60b0a40a60a44d30429cd3a4dd8374c16345951a

doc/source/node_management/kubernetes/node_interfaces/configuring-aggregated-ethernet-interfaces-using-the-cli.rst

@@ -115,17 +115,3 @@ Settings <link-aggregation-settings>`.
         ~(keystone_admin)$ system host-if-add controller-0 -a balanced -x layer2 ae0 ae enp0s9 enp0s10
         ~(keystone_admin)$ system interface-datanetwork-assign controller-0 ae0 providernet-net-a
         ~(keystone_admin)$ system interface-datanetwork-assign controller-0 ae0 providernet-net-b
-
-    For example, to attach an aggregated Ethernet interface named **bond0** to
-    the platform management network, using member interfaces **enp0s8**
-    and **enp0s11** on **controller-0**:
-
-    .. code-block:: none
-
-        ~(keystone_admin)$ system host-if-add controller-0 -c platform -a active_standby --primary-reselect failure bond0 ae enp0s8 enp0s11
-        ~(keystone_admin)$ system interface-network-assign controller-0 bond0 mgmt
-
-
-.. only:: partner
-
-    ../../../_includes/configuring-aggregated-ethernet-interfaces-using-the-cli.rest

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

@@ -9,9 +9,9 @@ Interface IP Address Provisioning Using the CLI
 On a network that uses static addressing, you must assign an IP address to
 the interface using the :command:`system host-addr-add` command.
 
-The procedure for attaching an interface depends on the interface type.
+The procedure for adding an IP address depends on the interface type.
 
-|prod| supports three types of interfaces:
+|prod| supports the following types of interfaces:
 
 **Ethernet interfaces**
     These are created automatically for each port on the host. You must
@@ -21,11 +21,32 @@ The procedure for attaching an interface depends on the interface type.
     For link protection, you can create an aggregated Ethernet interface with
     two or more ports, and configure it with the interface class.
 
+    .. code-block:: none
+
+        ~(keystone_admin)$ system host-if-add <hostname> -m mtu -a aemode -x txhashpolicy ifname ae <ethname1> <ethname2>
+
 **VLAN interfaces**
     To support multiple interfaces on the same physical Ethernet or
     aggregated Ethernet interface, you can create |VLAN| interfaces and
     configure them with the interface class.
 
+    .. code-block:: none
+
+        ~(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
+    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
+    configure a subset of virtual functions with the vfio driver that can be
+    used with userspace libraries such as DPDK.
+
+    .. code-block:: none
+
+        ~(keystone_admin)$ system host-if-add -c pci-sriov <hostname> <interfacename> vf <parentinterfacename> -N numvfs --vf-driver=drivername
+
+
 Logical interfaces of network types **oam** and **mgmt** cannot be deleted.
 They can only be modified to use different physical ports when required.
 
@@ -55,16 +76,16 @@ They can only be modified to use different physical ports when required.
 
     where the following options are available:
 
-    **node**
+    ``node``
         The name or UUID of the worker node.
 
-    **ifname**
+    ``ifname``
         The name of the interface.
 
-    **ip\_address**
+    ``ip\_address``
         An IPv4 or IPv6 address.
 
-    **prefix**
+    ``prefix``
         The netmask length for the address.
 
 #.  Unlock the node and wait for it to become available.

doc/source/node_management/kubernetes/node_interfaces/interface-provisioning.rst

@@ -77,7 +77,7 @@ They can only be modified to use different physical ports when required.
    see |planning-doc|: `Ethernet Interfaces <about-ethernet-interfaces>`.
 
 .. note::
-    On the second worker and storage nodes, the Ethernet interface for the
+    On all nodes, except for the initial controller, 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

doc/source/node_management/kubernetes/node_interfaces/interface-settings.rst

@@ -147,7 +147,7 @@ These settings are available on the **Edit Interface** and
         Use an address from a pool of IPv4 addresses that has been defined
         and associated with the data interface.
 
-**IPv4 Addressing Mode**
+**IPv4 Addressing Pool**
     \(Shown only when the **IPv4 Addressing Mode** is set to **pool**\). The
     pool from which to assign an IPv4 address.