System Config Guide and Data Network Guide

Global Pass Upgrades

Pacth 01: inputs from email by Greg

patch 02: removed content from topic
	-display data network information using horizon

Story: TBD
Task: TBD

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

doc/source/datanet/kubernetes/adding-data-networks-using-the-cli.rst

@@ -6,17 +6,10 @@
 Add Data Networks Using the CLI
 ===============================
 
-If you prefer, you can add data networks using the CLI. You can set up flat,
+You can add data networks using the CLI. You can set up flat, VLAN and VXLAN
-VLAN and VXLAN data networks over physical networks using the **controller-0**
+data networks over physical networks using the command-line interface. The data
-command-line interface. The data networks provide connectivity for project
+networks model the L2 networks that are attached to node data, pci-sriov and
-networks.
+pci-passthrough interface.
-
-.. rubric:: |prereq|
-
-
-.. _adding-data-networks-using-the-cli-prereq-controller-0-ready:
-
-Controller-0 must be installed and configured.
 
 .. rubric:: |proc|
 
@@ -81,8 +74,6 @@ Controller-0 must be installed and configured.
         | description  | None                                 |
         +--------------+--------------------------------------+
 
-    You must configure at least one data network in order to assign data
-    interfaces to worker nodes and unlock the hosts.
 
 .. rubric:: |postreq|
 

doc/source/datanet/kubernetes/assigning-a-data-network-to-an-interface.rst

@@ -7,10 +7,10 @@ Assign a Data Network to an Interface
 =====================================
 
 In order to associate the L2 Network definition of a Data Network with a
-physical network, the Data Network must be mapped to an Ethernet or Aggregated
+physical network, the Data Network must be mapped to an interface on a host.
-Ethernet interface on a compute node.
 
 The command for performing the mapping has the format:
 
-:command:`system interface‐datanetwork‐assign` <compute> <interface\_uuid>
+.. code-block:: none
-<datanetwork\_uuid>
+
+    ~(keystone_admin)]$ system interface‐datanetwork‐assign <host\_name> <interface\_uuid> <datanetwork\_uuid>

doc/source/datanet/kubernetes/data-network-management-data-networks.rst

@@ -34,9 +34,6 @@ created:
     .. note::
         This data interface is ONLY applicable to the |prod-os| application.
 
-        Static VXLAN is limited to one data network, and if configured, it must
-        be enabled on all openstack-compute labeled nodes.
-
     A data network implemented across non-contiguous physical networks
     connected by Layer 3 routers, using a VNI identifier. This allows
     multiple data networks over physically separated Layer 2 networks.

doc/source/datanet/kubernetes/displaying-data-network-information-using-horizon.rst

@@ -6,29 +6,11 @@
 Display Data Network Information Using Horizon
 ==============================================
 
-You can view data network details from the Horizon Web interface or the CLI.
-You can also view data network topologies from Horizon.
-
 .. rubric:: |context|
 
 Using Horizon, you can obtain information about data networks using the
 following:
 
-The **Data Network Topology** view. This is a graphical representation of all
-data networks on the system and their connections to worker hosts. You can
-select individual data networks to view details. You can also review active
-alarms for data network connections.
-
-.. For more information, see :ref:`The Data Network Topology View <the-data-network-topology-view>`.
-
-.. note::
-    You cannot make changes from this view.
-
-Both places use the **Data Network Details** tab to present details. If you
-prefer, you can view the details using the CLI; for more information, see
-:ref:`Displaying Data Network Information Using the CLI
-<displaying-data-network-information-using-the-cli>`.
-
 .. rubric:: |proc|
 
 #.  From the left pane menu, select **Admin** \> **Platform** \> **Data
@@ -38,3 +20,7 @@ prefer, you can view the details using the CLI; for more information, see
 
     Details for the data network are displayed and, in the case of |prod-os|,
     the project networks.
+
+.. note::
+    You can view data network topologies from Horizon, see :ref:`Data Network
+    Topology View <the-data-network-topology-view>`.

doc/source/datanet/kubernetes/index.rst

@@ -3,13 +3,14 @@
 .. _datanet_kubernetes_index:
 
 ========
-Contents
+Overview
 ========
 
 .. toctree::
    :maxdepth: 1
 
    data-network-management-data-networks
+   vxlan-data-networks
 
 --------------------------------
 Display data network information
@@ -21,7 +22,6 @@ Display data network information
    displaying-data-network-information-using-horizon
    displaying-data-network-information-using-the-cli
    the-data-network-topology-view
-   vxlan-data-networks
 
 -------------------------------------
 Add, assign, and remove data networks

doc/source/datanet/kubernetes/removing-a-data-network-using-the-cli.rst

@@ -11,7 +11,7 @@ associations.
 
 .. rubric:: |context|
 
-Complete the following steps to delete a data interface.
+Complete the following steps to delete a data network.
 
 .. rubric:: |prereq|
 
@@ -21,7 +21,7 @@ The following procedure requires that the host be locked.
 
 #.  Remove the data network from the interface.
 
-    #.  Identify the interface to be removed.
+    #.  Identify the interface to be removed from the data network.
 
         For example:
 
@@ -36,7 +36,7 @@ The following procedure requires that the host be locked.
             | controller-1 | c4ac3c62-283e-491f-a08b-2e4a5ece205c | pthru0 | group0-data0     |
             +--------------+--------------------------------------+--------+------------------+
 
-    #.  Remove the network.
+    #.  Remove the interface from the network.
 
         For example:
 

doc/source/datanet/kubernetes/vxlan-data-networks.rst

@@ -41,6 +41,11 @@ are included in the outer IP header.
 Before you can create project networks on a |VXLAN| provider network, you must
 define at least one network segment range.
 
+.. note::
+
+    Static VXLAN is limited to one data network, and if configured, it must
+    be enabled on all openstack-compute labeled nodes.
+
 -   :ref:`Dynamic VXLAN <dynamic-vxlan>`
 
 -   :ref:`Static VXLAN <static-vxlan>`

doc/source/system_configuration/kubernetes/applying-a-custom-branding-tarball-to-newly-installed-systems.rst

@@ -2,14 +2,14 @@
 .. hur1582149306886
 .. _applying-a-custom-branding-tarball-to-newly-installed-systems:
 
-==========================================================
+==================================================================
-Apply a Custom Branding Tarball to Newly Installed Systems
+Apply a Custom Horizon Branding Tarball to Newly Installed Systems
-==========================================================
+==================================================================
 
-You can apply a custom branding tarball to newly installed systems
+You can apply a custom Horizon branding tarball to newly installed systems
 prior to running the bootstrap playbook.
 
-Complete the following steps to apply the custom branding tarball:
+Complete the following steps to apply the custom Horizon branding tarball:
 
 .. rubric:: |proc|
 

doc/source/system_configuration/kubernetes/applying-a-custom-branding-tarball-to-running-systems.rst

@@ -2,13 +2,13 @@
 .. cmk1582149379500
 .. _applying-a-custom-branding-tarball-to-running-systems:
 
-==================================================
+==========================================================
-Apply a Custom Branding Tarball to Running Systems
+Apply a Custom Horizon Branding Tarball to Running Systems
-==================================================
+==========================================================
 
-You can apply the custom branding tarball to running systems.
+You can apply the custom Horizon branding tarball to running systems.
 
-Complete the following steps to apply the custom branding tarball:
+Complete the following steps to apply the custom Horizon branding tarball:
 
 .. rubric:: |proc|
 
@@ -16,7 +16,7 @@ Complete the following steps to apply the custom branding tarball:
 
 #.  Delete any previous branding tarball from /opt/branding.
 
-#.  Copy the new branding tarball to the /opt/branding directory on the
+#.  Copy the new Horizon branding tarball to the /opt/branding directory on the
     active controller.
 
 #.  Restart the Horizon Web interface.

doc/source/system_configuration/kubernetes/changing-the-oam-ip-configuration-using-horizon.rst

@@ -63,7 +63,7 @@ and ensure that any existing system alarms are cleared.
         If you change the IP address version \(IPv4 or IPv6\), ensure that the
         same version is used for the DNS servers
         \(see :ref:`Specify DNS Servers Using Horizon <specifying-dns-servers-using-horizon>`\)
-        and NTP servers \(see :ref:`Configure NTP Servers and Services Using Horizon <configuring-ntp-servers-and-services-using-horizon>`\).
+        and NTP servers \(see :ref:`Configure NTP Servers Using Horizon <configuring-ntp-servers-and-services-using-horizon>`\).
 
 #.  Click **Save**.
 

doc/source/system_configuration/kubernetes/configuring-ntp-servers-and-services-using-horizon.rst

@@ -3,7 +3,7 @@
 .. _configuring-ntp-servers-and-services-using-horizon:
 
 ================================================
-Configure NTP Servers and Services Using Horizon
+Configure NTP Servers Using Horizon
 ================================================
 
 You can add or update a list of external NTP servers for |prod| to use for

doc/source/system_configuration/kubernetes/configuring-ntp-servers-and-services-using-the-cli.rst

@@ -2,16 +2,16 @@
 .. ktx1552673128591
 .. _configuring-ntp-servers-and-services-using-the-cli:
 
-================================================
+===================================
-Configure NTP Servers and Services Using the CLI
+Configure NTP Servers Using the CLI
-================================================
+===================================
 
 You can use the CLI to add or update a list of |NTP| servers and services.
 
 **NTP Servers**
 
 You can specify up to three |NTP| servers using the CLI or the Horizon Web
-interface. For more information, see :ref:`Configure NTP Servers and Services Using Horizon <configuring-ntp-servers-and-services-using-horizon>`.
+interface. For more information, see :ref:`Configure NTP Servers Using Horizon <configuring-ntp-servers-and-services-using-horizon>`.
 
 To view the existing |NTP| server configuration, use the following command.
 

doc/source/system_configuration/kubernetes/creating-a-custom-branding-tarball.rst

@@ -2,9 +2,9 @@
 .. ngt1557520137257
 .. _creating-a-custom-branding-tarball:
 
-================================
+========================================
-Create a Custom Branding Tarball
+Create a Custom Horizon Branding Tarball
-================================
+========================================
 
 This section contains instructions and examples for creating and applying a
 tarball containing a custom Horizon Web interface theme, and associated
@@ -122,9 +122,9 @@ installation.
 
 For more information on applying the tarball to newly installed systems prior
 to running the bootstrap playbook,
-see :ref:`Apply a Custom Branding Tarball to Newly Installed Systems
+see :ref:`Apply a Custom Horizon Branding Tarball to Newly Installed Systems
 <applying-a-custom-branding-tarball-to-newly-installed-systems>`.
 
 For more information on applying the tarball to running systems,
-see :ref:`Apply a Custom Branding Tarball to Running Systems
+see :ref:`Apply a Custom Horizon Branding Tarball to Running Systems
 <applying-a-custom-branding-tarball-to-running-systems>`.