starlingx/docs
Code Issues Proposed changes

Fix symlinks

Browse Source 
Changed paths to avoid '..', which breaks symlinks in newer versions of sphinx.
Consolidated installation include files under /_includes. Prefixed r5 versions with 'r5_'
Moved files that are used up/down, but at different paths under /shared/_includes
and /shared/figures
Move two include files to /_includes
Moved addtional images to /shared/figures/... Required for DS platform builds.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: Ia38f4205c5803b3d1fc043e6c59617c34a4e5cbd
Signed-off-by: Ron Stone <ronald.stone@windriver.com>
(cherry picked from commit 2b62f49a9d)
This commit is contained in:
Ron Stone
2021-08-25 09:07:26 -04:00
parent 752ff6a532
commit d9fd2b7923
193 changed files with 712 additions and 378 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/source/deploy_install_guides/r5_release/ansible_install_time_only.txt → doc/source/_includes/ansible_install_time_only.txt
View File

@@ -4,4 +4,4 @@
Review the set of install-time-only parameters before installation and confirm that your values for these parameters are correct for the desired installation. Review the set of install-time-only parameters before installation and confirm that your values for these parameters are correct for the desired installation.
Refer to :ref:`Ansible install-time-only parameters <install-time-only-params-r5>` for details. Refer to :ref:`Ansible install-time-only parameters <install-time-only-params-r6>` for details.

2
doc/source/_includes/docker-proxy-config.rest
View File

@@ -17,7 +17,7 @@ Set proxy at bootstrap
To set the Docker proxy at bootstrap time, refer to :doc:`Ansible Bootstrap To set the Docker proxy at bootstrap time, refer to :doc:`Ansible Bootstrap
Configurations Configurations
<../deploy_install_guides/r6_release/ansible_bootstrap_configs>`. </deploy_install_guides/r6_release/ansible_bootstrap_configs>`.
.. r3_end .. r3_end

4
doc/source/deploy_install_guides/r5_release/kubernetes_install_next.txt → doc/source/_includes/kubernetes_install_next.txt
View File

@@ -1,7 +1,7 @@
Your Kubernetes cluster is now up and running. Your Kubernetes cluster is now up and running.
For instructions on how to access StarlingX Kubernetes see For instructions on how to access StarlingX Kubernetes see
:doc:`../kubernetes_access`. :ref:`kubernetes_access`.
For instructions on how to install and access StarlingX OpenStack see For instructions on how to install and access StarlingX OpenStack see
:doc:`../openstack/index`. :doc:`/deploy_install_guides/r6_release/openstack/index`.

7
doc/source/_includes/r5_kubernetes_install_next.txt Normal file
View File

@@ -0,0 +1,7 @@
Your Kubernetes cluster is now up and running.
For instructions on how to access StarlingX Kubernetes see
:ref:`kubernetes_access`.
For instructions on how to install and access StarlingX OpenStack see
:doc:`/deploy_install_guides/r5_release/openstack/index`.

9
doc/source/_includes/set-proxy-at-bootstrap.rest Normal file
View File

@@ -0,0 +1,9 @@
<<<<<<< HEAD (752ff6 Merge "Updated "Install and Provision the Central Cloud" top)
=======
----------------------
Set proxy at bootstrap
----------------------
To set the Docker proxy at bootstrap time, refer to
:doc:`Ansible Bootstrap Configurations </deploy_install_guides/r3_release/ansible_bootstrap_configs>`.
>>>>>>> CHANGE (2b62f4 Fix symlinks)

2
doc/source/contributor/doc_contribute_guide.rst
View File

@@ -1,3 +1,5 @@
.. _doc_contribute_guide:
=============================== ===============================
Documentation Contributor Guide Documentation Contributor Guide
=============================== ===============================

4
doc/source/contributor/index.rst
View File

@@ -32,8 +32,8 @@ Additional StarlingX-specific resources are listed below.
:maxdepth: 1 :maxdepth: 1
development_process development_process
../developer_resources/code-submission-guide /developer_resources/code-submission-guide
../developer_resources/debug_issues /developer_resources/debug_issues
-------------------- --------------------
Additional resources Additional resources

4
doc/source/datanet/kubernetes/the-data-network-topology-view.rst
View File

@@ -18,7 +18,7 @@ hosts or networks to highlight their connections and obtain more details.
To display this view, select **Admin** \> **Platform** \> **Data Network To display this view, select **Admin** \> **Platform** \> **Data Network
Topology**. Topology**.
.. image:: ../figures/sqw1475425312420.png .. image:: /datanet/figures/sqw1475425312420.png
:height: 365px :height: 365px
.. _the-data-network-topology-view-section-N1002F-N1001C-N10001: .. _the-data-network-topology-view-section-N1002F-N1001C-N10001:
@@ -75,7 +75,7 @@ using icons superimposed on the entities. The alarms are color-coded for
severity using the same colors as the Global Alarm Banner. Details for the severity using the same colors as the Global Alarm Banner. Details for the
alarms are listed in the **Related Alarms** tab for the entity. alarms are listed in the **Related Alarms** tab for the entity.
.. image:: ../figures/eal1475518780745.png .. image:: /shared/figures/datanet/eal1475518780745.png
.. _the-data-network-topology-view-section-N100AD-N1001C-N10001: .. _the-data-network-topology-view-section-N100AD-N1001C-N10001:

6
doc/source/datanet/openstack/adding-a-static-ip-address-to-a-data-interface.rst
View File

@@ -45,18 +45,18 @@ To make interface changes, you must lock the compute host first.
#. In the Edit Interface dialog box, set the **IPv4 Addressing Mode** or #. In the Edit Interface dialog box, set the **IPv4 Addressing Mode** or
the **IPv6 Addressing Mode** to **Static**. the **IPv6 Addressing Mode** to **Static**.
.. image:: ../figures/bju1538154656153.png .. image:: /shared/figures/datanet/bju1538154656153.png
#. Add an IPv4 or IPv6 address to the interface. #. Add an IPv4 or IPv6 address to the interface.
#. On the Host Detail page, click the **Name** of the interface to open #. On the Host Detail page, click the **Name** of the interface to open
the Interface Detail page. the Interface Detail page.
.. image:: ../figures/jow1443041105867.png .. image:: /shared/figures/datanet/jow1443041105867.png
#. Click **Create Address** to open the Create Address dialog box. #. Click **Create Address** to open the Create Address dialog box.
.. image:: ../figures/jow1442607685238.png .. image:: /shared/figures/datanet/jow1442607685238.png
#. Enter the IPv4 or IPv6 address and netmask \(for example, #. Enter the IPv4 or IPv6 address and netmask \(for example,
192.168.1.3/24\), and then click **Create Address**. 192.168.1.3/24\), and then click **Create Address**.

2
doc/source/datanet/openstack/dynamic-vxlan.rst
View File

@@ -37,7 +37,7 @@ for more complex routing requirements but requires IP multicast enabled routers.
:start-after: vswitch-text-1-begin :start-after: vswitch-text-1-begin
:end-before: vswitch-text-1-end :end-before: vswitch-text-1-end
.. figure:: ../figures/eol1510005391750.png .. figure:: /shared/figures/datanet/eol1510005391750.png
Multicast Endpoint Distribution Multicast Endpoint Distribution

2
doc/source/datanet/openstack/static-vxlan.rst
View File

@@ -29,7 +29,7 @@ to receive the packet in order to reach the |VM|.
Static |VXLAN| is limited to use on one data network. If configured, it must be Static |VXLAN| is limited to use on one data network. If configured, it must be
enabled on all OpenStack compute nodes. enabled on all OpenStack compute nodes.
.. figure:: ../figures/oeg1510005898965.png .. figure:: /shared/figures/datanet/oeg1510005898965.png
`Static Endpoint Distribution` `Static Endpoint Distribution`

4
doc/source/datanet/openstack/using-ip-address-pools-for-data-interfaces.rst
View File

@@ -37,7 +37,7 @@ To make interface changes, you must lock the compute node first.
#. Select the **Address Pools** tab. #. Select the **Address Pools** tab.
.. image:: ../figures/jow1445971002260.png .. image:: /shared/figures/datanet/jow1445971002260.png
You can use the controls on the Address Pools page to create, update, or You can use the controls on the Address Pools page to create, update, or
delete address pools. delete address pools.
@@ -45,7 +45,7 @@ To make interface changes, you must lock the compute node first.
#. To create an address pool, click **Create Address Pool** and complete the #. To create an address pool, click **Create Address Pool** and complete the
dialog box. dialog box.
.. image:: ../figures/jow1445971475692.png .. image:: /shared/figures/datanet/jow1445971475692.png
**Name** **Name**
A name used for selecting the pool during data interface setup. A name used for selecting the pool during data interface setup.

2
doc/source/deploy_install_guides/nvme_config.rst
View File

@@ -1,3 +1,5 @@
.. _nvme_config:
==================================== ====================================
Configure NVMe Drive as Primary Disk Configure NVMe Drive as Primary Disk
==================================== ====================================

4
doc/source/deploy_install_guides/r5_release/bare_metal/aio_duplex.rst
View File

@@ -6,13 +6,13 @@ Bare metal All-in-one Duplex Installation R5.0
Overview Overview
-------- --------
.. include:: ../desc_aio_duplex.txt .. include:: /shared/_includes/r5_desc_aio_duplex.txt
The bare metal AIO-DX deployment configuration may be extended with up to four The bare metal AIO-DX deployment configuration may be extended with up to four
worker nodes (not shown in the diagram). Installation instructions for worker nodes (not shown in the diagram). Installation instructions for
these additional nodes are described in :doc:`aio_duplex_extend`. these additional nodes are described in :doc:`aio_duplex_extend`.
.. include:: ../ipv6_note.txt .. include:: /shared/_includes/r5_ipv6_note.txt
------------ ------------
Installation Installation

2
doc/source/deploy_install_guides/r5_release/bare_metal/aio_duplex_hardware.rst
View File

@@ -31,7 +31,7 @@ host types are:
+-------------------------+-----------------------------------------------------------+ +-------------------------+-----------------------------------------------------------+
| Minimum memory | 64 GB | | Minimum memory | 64 GB |
+-------------------------+-----------------------------------------------------------+ +-------------------------+-----------------------------------------------------------+
| Primary disk | 500 GB SSD or NVMe (see :doc:`../../nvme_config`) | | Primary disk | 500 GB SSD or NVMe (see :ref:`nvme_config`) |
+-------------------------+-----------------------------------------------------------+ +-------------------------+-----------------------------------------------------------+
| Additional disks | - 1 or more 500 GB (min. 10K RPM) for Ceph OSD | | Additional disks | - 1 or more 500 GB (min. 10K RPM) for Ceph OSD |
| | - Recommended, but not required: 1 or more SSDs or NVMe | | | - Recommended, but not required: 1 or more SSDs or NVMe |

6
doc/source/deploy_install_guides/r5_release/bare_metal/aio_duplex_install_kubernetes.rst
View File

@@ -30,7 +30,7 @@ Install Kubernetes Platform on All-in-one Duplex
Install software on controller-0 Install software on controller-0
-------------------------------- --------------------------------
.. include:: inc-install-software-on-controller.rest .. include:: /shared/_includes/r5_inc-install-software-on-controller.rest
:start-after: incl-install-software-controller-0-aio-start :start-after: incl-install-software-controller-0-aio-start
:end-before: incl-install-software-controller-0-aio-end :end-before: incl-install-software-controller-0-aio-end
@@ -91,7 +91,7 @@ Bootstrap system on controller-0
.. only:: starlingx .. only:: starlingx
.. include:: ../ansible_install_time_only.txt .. include:: /shared/_includes/r5_ansible_install_time_only.txt
Specify the user configuration override file for the Ansible bootstrap Specify the user configuration override file for the Ansible bootstrap
playbook using one of the following methods: playbook using one of the following methods:
@@ -1101,7 +1101,7 @@ machine.
Next steps Next steps
---------- ----------
.. include:: ../kubernetes_install_next.txt .. include:: /_includes/r5_kubernetes_install_next.txt
.. only:: partner .. only:: partner

4
doc/source/deploy_install_guides/r5_release/bare_metal/aio_simplex.rst
View File

@@ -6,9 +6,9 @@ Bare metal All-in-one Simplex Installation R5.0
Overview Overview
-------- --------
.. include:: ../desc_aio_simplex.txt .. include:: /shared/_includes/r5_desc_aio_simplex.txt
.. include:: ../ipv6_note.txt .. include:: /shared/_includes/r5_ipv6_note.txt
------------ ------------
Installation Installation

68
doc/source/deploy_install_guides/r5_release/bare_metal/aio_simplex_hardware.rst
View File

@@ -16,40 +16,40 @@ Minimum hardware requirements
The recommended minimum hardware requirements for bare metal servers for various The recommended minimum hardware requirements for bare metal servers for various
host types are: host types are:
+-------------------------+-----------------------------------------------------------+ +-------------------------+--------------------------------------------------------------------+
| Minimum Requirement | All-in-one Controller Node | | Minimum Requirement | All-in-one Controller Node |
+=========================+===========================================================+ +=========================+====================================================================+
| Number of servers | 1 | | Number of servers | 1 |
+-------------------------+-----------------------------------------------------------+ +-------------------------+--------------------------------------------------------------------+
| Minimum processor class | - Dual-CPU Intel® Xeon® E5 26xx family (SandyBridge) | | Minimum processor class | - Dual-CPU Intel® Xeon® E5 26xx family (SandyBridge) |
| | 8 cores/socket | | | 8 cores/socket |
| | | | | |
| | or | | | or |
| | | | | |
| | - Single-CPU Intel® Xeon® D-15xx family, 8 cores | | | - Single-CPU Intel® Xeon® D-15xx family, 8 cores |
| | (low-power/low-cost option) | | | (low-power/low-cost option) |
+-------------------------+-----------------------------------------------------------+ +-------------------------+--------------------------------------------------------------------+
| Minimum memory | 64 GB | | Minimum memory | 64 GB |
+-------------------------+-----------------------------------------------------------+ +-------------------------+--------------------------------------------------------------------+
| Primary disk | 500 GB SSD or NVMe (see :doc:`../../nvme_config`) | | Primary disk | 500 GB SSD or NVMe (see :ref:`nvme_config`) |
+-------------------------+-----------------------------------------------------------+ +-------------------------+--------------------------------------------------------------------+
| Additional disks | - 1 or more 500 GB (min. 10K RPM) for Ceph OSD | | Additional disks | - 1 or more 500 GB (min. 10K RPM) for Ceph OSD |
| | - Recommended, but not required: 1 or more SSDs or NVMe | | | - Recommended, but not required: 1 or more SSDs or NVMe |
| | drives for Ceph journals (min. 1024 MiB per OSD | | | drives for Ceph journals (min. 1024 MiB per OSD |
| | journal) | | | journal) |
| | - For OpenStack, recommend 1 or more 500 GB (min. 10K | | | - For OpenStack, recommend 1 or more 500 GB (min. 10K |
| | RPM) for VM local ephemeral storage | | | RPM) for VM local ephemeral storage |
+-------------------------+-----------------------------------------------------------+ +-------------------------+--------------------------------------------------------------------+
| Minimum network ports | - OAM: 1x1GE | | Minimum network ports | - OAM: 1x1GE |
| | - Data: 1 or more x 10GE | | | - Data: 1 or more x 10GE |
+-------------------------+-----------------------------------------------------------+ +-------------------------+--------------------------------------------------------------------+
| BIOS settings | - Hyper-Threading technology enabled | | BIOS settings | - Hyper-Threading technology enabled |
| | - Virtualization technology enabled | | | - Virtualization technology enabled |
| | - VT for directed I/O enabled | | | - VT for directed I/O enabled |
| | - CPU power and performance policy set to performance | | | - CPU power and performance policy set to performance |
| | - CPU C state control disabled | | | - CPU C state control disabled |
| | - Plug & play BMC detection disabled | | | - Plug & play BMC detection disabled |
+-------------------------+-----------------------------------------------------------+ +-------------------------+--------------------------------------------------------------------+
-------------------------- --------------------------
Prepare bare metal servers Prepare bare metal servers

6
doc/source/deploy_install_guides/r5_release/bare_metal/aio_simplex_install_kubernetes.rst
View File

@@ -30,7 +30,7 @@ Install Kubernetes Platform on All-in-one Simplex
Install software on controller-0 Install software on controller-0
-------------------------------- --------------------------------
.. include:: inc-install-software-on-controller.rest .. include:: /shared/_includes/r5_inc-install-software-on-controller.rest
:start-after: incl-install-software-controller-0-aio-start :start-after: incl-install-software-controller-0-aio-start
:end-before: incl-install-software-controller-0-aio-end :end-before: incl-install-software-controller-0-aio-end
@@ -91,7 +91,7 @@ Bootstrap system on controller-0
.. only:: starlingx .. only:: starlingx
.. include:: ../ansible_install_time_only.txt .. include:: /shared/_includes/r5_ansible_install_time_only.txt
Specify the user configuration override file for the Ansible bootstrap Specify the user configuration override file for the Ansible bootstrap
playbook using one of the following methods: playbook using one of the following methods:
@@ -687,7 +687,7 @@ machine.
Next steps Next steps
---------- ----------
.. include:: ../kubernetes_install_next.txt .. include::/_includes/r5_kubernetes_install_next.txt
.. only:: partner .. only:: partner

4
doc/source/deploy_install_guides/r5_release/bare_metal/controller_storage.rst
View File

@@ -6,9 +6,9 @@ Bare metal Standard with Controller Storage Installation R5.0
Overview Overview
-------- --------
.. include:: ../desc_controller_storage.txt .. include:: /shared/_includes/r5_desc_controller_storage.txt
.. include:: ../ipv6_note.txt .. include:: /shared/_includes/r5_ipv6_note.txt
------------ ------------

2
doc/source/deploy_install_guides/r5_release/bare_metal/controller_storage_hardware.rst
View File

@@ -28,7 +28,7 @@ host types are:
| Minimum memory | 64 GB | 32 GB | | Minimum memory | 64 GB | 32 GB |
+-------------------------+-----------------------------+-----------------------------+ +-------------------------+-----------------------------+-----------------------------+
| Primary disk | 500 GB SSD or NVMe (see | 120 GB (Minimum 10k RPM) | | Primary disk | 500 GB SSD or NVMe (see | 120 GB (Minimum 10k RPM) |
| | :doc:`../../nvme_config`) | | | | :ref:`nvme_config`) | |
+-------------------------+-----------------------------+-----------------------------+ +-------------------------+-----------------------------+-----------------------------+
| Additional disks | - 1 or more 500 GB (min. | - For OpenStack, recommend | | Additional disks | - 1 or more 500 GB (min. | - For OpenStack, recommend |
| | 10K RPM) for Ceph OSD | 1 or more 500 GB (min. | | | 10K RPM) for Ceph OSD | 1 or more 500 GB (min. |

6
doc/source/deploy_install_guides/r5_release/bare_metal/controller_storage_install_kubernetes.rst
View File

@@ -26,7 +26,7 @@ Install Kubernetes Platform on Standard with Controller Storage
Install software on controller-0 Install software on controller-0
-------------------------------- --------------------------------
.. include:: inc-install-software-on-controller.rest .. include:: /shared/_includes/r5_inc-install-software-on-controller.rest
:start-after: incl-install-software-controller-0-standard-start :start-after: incl-install-software-controller-0-standard-start
:end-before: incl-install-software-controller-0-standard-end :end-before: incl-install-software-controller-0-standard-end
@@ -90,7 +90,7 @@ Bootstrap system on controller-0
.. only:: starlingx .. only:: starlingx
.. include:: ../ansible_install_time_only.txt .. include:: /shared/_includes/r5_ansible_install_time_only.txt
Specify the user configuration override file for the Ansible bootstrap Specify the user configuration override file for the Ansible bootstrap
playbook using one of the following methods: playbook using one of the following methods:
@@ -909,7 +909,7 @@ If configuring Ceph Storage Backend, Add Ceph OSDs to controllers
Next steps Next steps
---------- ----------
.. include:: ../kubernetes_install_next.txt .. include:: /_includes/r5_kubernetes_install_next.txt
.. only:: partner .. only:: partner

4
doc/source/deploy_install_guides/r5_release/bare_metal/dedicated_storage.rst
View File

@@ -7,9 +7,9 @@ Bare metal Standard with Dedicated Storage Installation R5.0
Overview Overview
-------- --------
.. include:: ../desc_dedicated_storage.txt .. include:: /shared/_includes/r5_desc_dedicated_storage.txt
.. include:: ../ipv6_note.txt .. include:: /shared/_includes/r5_ipv6_note.txt
------------ ------------
Installation Installation

2
doc/source/deploy_install_guides/r5_release/bare_metal/dedicated_storage_hardware.rst
View File

@@ -28,7 +28,7 @@ host types are:
| Minimum memory | 64 GB | 64 GB | 32 GB | | Minimum memory | 64 GB | 64 GB | 32 GB |
+---------------------+---------------------------+-----------------------+-----------------------+ +---------------------+---------------------------+-----------------------+-----------------------+
| Primary disk | 500 GB SSD or NVMe (see | 120 GB (min. 10k RPM) | 120 GB (min. 10k RPM) | | Primary disk | 500 GB SSD or NVMe (see | 120 GB (min. 10k RPM) | 120 GB (min. 10k RPM) |
| | :doc:`../../nvme_config`) | | | | | :ref:`nvme_config`) | | |
+---------------------+---------------------------+-----------------------+-----------------------+ +---------------------+---------------------------+-----------------------+-----------------------+
| Additional disks | None | - 1 or more 500 GB | - For OpenStack, | | Additional disks | None | - 1 or more 500 GB | - For OpenStack, |
| | | (min. 10K RPM) for | recommend 1 or more | | | | (min. 10K RPM) for | recommend 1 or more |

4
doc/source/deploy_install_guides/r5_release/bare_metal/dedicated_storage_install_kubernetes.rst
View File

@@ -30,7 +30,7 @@ This section describes the steps to install the |prod| Kubernetes platform on a
Install software on controller-0 Install software on controller-0
-------------------------------- --------------------------------
.. include:: inc-install-software-on-controller.rest .. include:: /shared/_includes/r5_inc-install-software-on-controller.rest
:start-after: incl-install-software-controller-0-standard-start :start-after: incl-install-software-controller-0-standard-start
:end-before: incl-install-software-controller-0-standard-end :end-before: incl-install-software-controller-0-standard-end
@@ -525,7 +525,7 @@ host machine.
Next steps Next steps
---------- ----------
.. include:: ../kubernetes_install_next.txt .. include:: /_includes/r5_kubernetes_install_next.txt
.. only:: partner .. only:: partner

4
doc/source/deploy_install_guides/r5_release/bare_metal/ironic.rst
View File

@@ -17,10 +17,10 @@ more bare metal servers.
.. note:: .. note::
If you are behind a corporate firewall or proxy, you need to set proxy If you are behind a corporate firewall or proxy, you need to set proxy
settings. Refer to :doc:`/../../configuration/docker_proxy_config` for settings. Refer to :ref:`docker_proxy_config` for
details. details.
.. figure:: ../figures/starlingx-deployment-options-ironic.png .. figure:: /deploy_install_guides/r5_release/figures/starlingx-deployment-options-ironic.png
:scale: 50% :scale: 50%
:alt: Standard with Ironic deployment configuration :alt: Standard with Ironic deployment configuration

4
doc/source/deploy_install_guides/r5_release/bare_metal/rook_storage.rst
View File

@@ -6,9 +6,9 @@ Bare metal Standard with Rook Storage Installation R5.0
Overview Overview
-------- --------
.. include:: ../desc_rook_storage.txt .. include:: /shared/_includes/r5_desc_rook_storage.txt
.. include:: ../ipv6_note.txt .. include:: /shared/_includes/r5_ipv6_note.txt
------------ ------------

2
doc/source/deploy_install_guides/r5_release/bare_metal/rook_storage_hardware.rst
View File

@@ -29,7 +29,7 @@ host types are:
| Minimum memory | 64 GB | 64 GB | 32 GB | | Minimum memory | 64 GB | 64 GB | 32 GB |
+---------------------+---------------------------+-----------------------+-----------------------+ +---------------------+---------------------------+-----------------------+-----------------------+
| Primary disk | 500 GB SSD or NVMe (see | 120 GB (min. 10k RPM) | 120 GB (min. 10k RPM) | | Primary disk | 500 GB SSD or NVMe (see | 120 GB (min. 10k RPM) | 120 GB (min. 10k RPM) |
| | :doc:`../../nvme_config`) | | | | | :ref:`nvme_config`) | | |
+---------------------+---------------------------+-----------------------+-----------------------+ +---------------------+---------------------------+-----------------------+-----------------------+
| Additional disks | None | - 1 or more 500 GB | - For OpenStack, | | Additional disks | None | - 1 or more 500 GB | - For OpenStack, |
| | | (min. 10K RPM) for | recommend 1 or more | | | | (min. 10K RPM) for | recommend 1 or more |

12
doc/source/deploy_install_guides/r5_release/bare_metal/rook_storage_install_kubernetes.rst
View File

@@ -16,8 +16,8 @@ configuration.
Create bootable USB Create bootable USB
------------------- -------------------
Refer to :doc:`/deploy_install_guides/bootable_usb` for instructions on how to Refer to :ref:`bootable_usb` for instructions on how to create a bootable USB
create a bootable USB with the StarlingX ISO on your system. with the StarlingX ISO on your system.
-------------------------------- --------------------------------
Install software on controller-0 Install software on controller-0
@@ -100,7 +100,7 @@ Bootstrap system on controller-0
The default location where Ansible looks for and imports user The default location where Ansible looks for and imports user
configuration override files for hosts. For example: ``$HOME/<hostname>.yml``. configuration override files for hosts. For example: ``$HOME/<hostname>.yml``.
.. include:: ../ansible_install_time_only.txt .. include:: /shared/_includes/r5_ansible_install_time_only.txt
Specify the user configuration override file for the Ansible bootstrap Specify the user configuration override file for the Ansible bootstrap
playbook using one of the following methods: playbook using one of the following methods:
@@ -151,7 +151,7 @@ Bootstrap system on controller-0
Refer to :doc:`/deploy_install_guides/r5_release/ansible_bootstrap_configs` Refer to :doc:`/deploy_install_guides/r5_release/ansible_bootstrap_configs`
for information on additional Ansible bootstrap configurations for advanced for information on additional Ansible bootstrap configurations for advanced
Ansible bootstrap scenarios, such as Docker proxies when deploying behind a Ansible bootstrap scenarios, such as Docker proxies when deploying behind a
firewall, etc. Refer to :doc:`/../../configuration/docker_proxy_config` for firewall, etc. Refer to :ref:`docker_proxy_config` for
details about Docker proxy settings. details about Docker proxy settings.
#. Run the Ansible bootstrap playbook: #. Run the Ansible bootstrap playbook:
@@ -212,7 +212,7 @@ Configure controller-0
system service-parameter-list platform docker system service-parameter-list platform docker
#. Refer to :doc:`/../../configuration/docker_proxy_config` for #. Refer to :ref:`docker_proxy_config` for
details about Docker proxy settings. details about Docker proxy settings.
************************************* *************************************
@@ -749,4 +749,4 @@ On host storage-0 and storage-1:
Next steps Next steps
---------- ----------
.. include:: ../kubernetes_install_next.txt .. include:: /_includes/r5_kubernetes_install_next.txt

2
doc/source/deploy_install_guides/r5_release/distributed_cloud/index.rst
View File

@@ -85,7 +85,7 @@ networks, as shown in Figure 1.
Alarms raised at the subclouds are sent to the System Controller for Alarms raised at the subclouds are sent to the System Controller for
central reporting. central reporting.
.. figure:: ../figures/starlingx-deployment-options-distributed-cloud.png .. figure:: /deploy_install_guides/r5_release/figures/starlingx-deployment-options-distributed-cloud.png
:scale: 45% :scale: 45%
:alt: Distributed cloud deployment configuration :alt: Distributed cloud deployment configuration

2
doc/source/deploy_install_guides/r5_release/kubernetes_access.rst
View File

@@ -1,3 +1,5 @@
.. _kubernetes_access:
================================ ================================
Access StarlingX Kubernetes R5.0 Access StarlingX Kubernetes R5.0
================================ ================================

4
doc/source/deploy_install_guides/r5_release/openstack/access.rst
View File

@@ -157,14 +157,14 @@ using the :command:`openstack` command. For example:
The image below shows a typical successful run. The image below shows a typical successful run.
.. figure:: ../figures/starlingx-access-openstack-flavorlist.png .. figure:: /deploy_install_guides/r5_release/figures/starlingx-access-openstack-flavorlist.png
:alt: starlingx-access-openstack-flavorlist :alt: starlingx-access-openstack-flavorlist
:scale: 50% :scale: 50%
*Figure 1: StarlingX OpenStack Flavorlist* *Figure 1: StarlingX OpenStack Flavorlist*
.. figure:: ../figures/starlingx-access-openstack-command.png .. figure:: /deploy_install_guides/r5_release/figures/starlingx-access-openstack-command.png
:alt: starlingx-access-openstack-command :alt: starlingx-access-openstack-command
:scale: 50% :scale: 50%

4
doc/source/deploy_install_guides/r5_release/virtual/aio_duplex.rst
View File

@@ -6,9 +6,9 @@ Virtual All-in-one Duplex Installation R5.0
Overview Overview
-------- --------
.. include:: ../desc_aio_duplex.txt .. include:: /shared/_includes/r5_desc_aio_duplex.txt
.. include:: ../ipv6_note.txt .. include:: /shared/_includes/r5_ipv6_note.txt
------------ ------------
Installation Installation

8
doc/source/deploy_install_guides/r5_release/virtual/aio_duplex_install_kubernetes.rst
View File

@@ -84,7 +84,7 @@ On virtual controller-0:
The default location where Ansible looks for and imports user The default location where Ansible looks for and imports user
configuration override files for hosts. For example: ``$HOME/<hostname>.yml``. configuration override files for hosts. For example: ``$HOME/<hostname>.yml``.
.. include:: ../ansible_install_time_only.txt .. include:: /shared/_includes/r5_ansible_install_time_only.txt
Specify the user configuration override file for the Ansible bootstrap Specify the user configuration override file for the Ansible bootstrap
playbook using one of the following methods: playbook using one of the following methods:
@@ -129,7 +129,7 @@ On virtual controller-0:
Refer to :doc:`/deploy_install_guides/r5_release/ansible_bootstrap_configs` Refer to :doc:`/deploy_install_guides/r5_release/ansible_bootstrap_configs`
for information on additional Ansible bootstrap configurations for advanced for information on additional Ansible bootstrap configurations for advanced
Ansible bootstrap scenarios, such as Docker proxies when deploying behind a Ansible bootstrap scenarios, such as Docker proxies when deploying behind a
firewall, etc. Refer to :doc:`/../../configuration/docker_proxy_config` for firewall, etc. Refer to :ref:`docker_proxy_config` for
details about Docker proxy settings. details about Docker proxy settings.
#. Run the Ansible bootstrap playbook: #. Run the Ansible bootstrap playbook:
@@ -284,7 +284,7 @@ For Rook container-based Ceph:
system service-parameter-list platform docker system service-parameter-list platform docker
#. Refer to :doc:`/../../configuration/docker_proxy_config` for #. Refer to :ref:`docker_proxy_config` for
details about Docker proxy settings. details about Docker proxy settings.
************************************* *************************************
@@ -575,4 +575,4 @@ On **virtual** controller-0 and controller-1:
Next steps Next steps
---------- ----------
.. include:: ../kubernetes_install_next.txt .. include:: /_includes/r5_kubernetes_install_next.txt

4
doc/source/deploy_install_guides/r5_release/virtual/aio_simplex.rst
View File

@@ -6,9 +6,9 @@ Virtual All-in-one Simplex Installation R5.0
Overview Overview
-------- --------
.. include:: ../desc_aio_simplex.txt .. include:: /shared/_includes/r5_desc_aio_simplex.txt
.. include:: ../ipv6_note.txt .. include:: /shared/_includes/r5_ipv6_note.txt
------------ ------------
Installation Installation

8
doc/source/deploy_install_guides/r5_release/virtual/aio_simplex_install_kubernetes.rst
View File

@@ -85,7 +85,7 @@ On virtual controller-0:
The default location where Ansible looks for and imports user The default location where Ansible looks for and imports user
configuration override files for hosts. For example: ``$HOME/<hostname>.yml``. configuration override files for hosts. For example: ``$HOME/<hostname>.yml``.
.. include:: ../ansible_install_time_only.txt .. include:: /shared/_includes/r5_ansible_install_time_only.txt
Specify the user configuration override file for the Ansible bootstrap Specify the user configuration override file for the Ansible bootstrap
playbook using one of the following methods: playbook using one of the following methods:
@@ -128,7 +128,7 @@ On virtual controller-0:
Refer to :doc:`/deploy_install_guides/r5_release/ansible_bootstrap_configs` Refer to :doc:`/deploy_install_guides/r5_release/ansible_bootstrap_configs`
for information on additional Ansible bootstrap configurations for advanced for information on additional Ansible bootstrap configurations for advanced
Ansible bootstrap scenarios, such as Docker proxies when deploying behind a Ansible bootstrap scenarios, such as Docker proxies when deploying behind a
firewall, etc. Refer to :doc:`/../../configuration/docker_proxy_config` for firewall, etc. Refer to :ref:`docker_proxy_config` for
details about Docker proxy settings. details about Docker proxy settings.
#. Run the Ansible bootstrap playbook: #. Run the Ansible bootstrap playbook:
@@ -275,7 +275,7 @@ For Rook container-based Ceph:
system service-parameter-list platform docker system service-parameter-list platform docker
#. Refer to :doc:`/../../configuration/docker_proxy_config` for #. Refer to :ref:`docker_proxy_config` for
details about Docker proxy settings. details about Docker proxy settings.
************************************* *************************************
@@ -411,4 +411,4 @@ On **virtual** controller-0:
Next steps Next steps
---------- ----------
.. include:: ../kubernetes_install_next.txt .. include:: /_includes/r5_kubernetes_install_next.txt

4
doc/source/deploy_install_guides/r5_release/virtual/controller_storage.rst
View File

@@ -6,9 +6,9 @@ Virtual Standard with Controller Storage Installation R5.0
Overview Overview
-------- --------
.. include:: ../desc_controller_storage.txt .. include:: /shared/_includes/r5_desc_controller_storage.txt
.. include:: ../ipv6_note.txt .. include:: /shared/_includes/r5_ipv6_note.txt
------------ ------------
Installation Installation

8
doc/source/deploy_install_guides/r5_release/virtual/controller_storage_install_kubernetes.rst
View File

@@ -89,7 +89,7 @@ On virtual controller-0:
The default location where Ansible looks for and imports user The default location where Ansible looks for and imports user
configuration override files for hosts. For example: ``$HOME/<hostname>.yml``. configuration override files for hosts. For example: ``$HOME/<hostname>.yml``.
.. include:: ../ansible_install_time_only.txt .. include:: /shared/_includes/r5_ansible_install_time_only.txt
Specify the user configuration override file for the Ansible bootstrap Specify the user configuration override file for the Ansible bootstrap
playbook using one of the following methods: playbook using one of the following methods:
@@ -134,7 +134,7 @@ On virtual controller-0:
Refer to :doc:`/deploy_install_guides/r5_release/ansible_bootstrap_configs` Refer to :doc:`/deploy_install_guides/r5_release/ansible_bootstrap_configs`
for information on additional Ansible bootstrap configurations for advanced for information on additional Ansible bootstrap configurations for advanced
Ansible bootstrap scenarios, such as Docker proxies when deploying behind a Ansible bootstrap scenarios, such as Docker proxies when deploying behind a
firewall, etc. Refer to :doc:`/../../configuration/docker_proxy_config` for firewall, etc. Refer to :ref:`docker_proxy_config` for
details about Docker proxy settings. details about Docker proxy settings.
#. Run the Ansible bootstrap playbook: #. Run the Ansible bootstrap playbook:
@@ -215,7 +215,7 @@ On virtual controller-0:
system service-parameter-list platform docker system service-parameter-list platform docker
#. Refer to :doc:`/../../configuration/docker_proxy_config` for #. Refer to :ref:`docker_proxy_config` for
details about Docker proxy settings. details about Docker proxy settings.
************************************* *************************************
@@ -597,4 +597,4 @@ On virtual controller-0:
Next steps Next steps
---------- ----------
.. include:: ../kubernetes_install_next.txt .. include:: /_includes/r5_kubernetes_install_next.txt

4
doc/source/deploy_install_guides/r5_release/virtual/dedicated_storage.rst
View File

@@ -6,9 +6,9 @@ Virtual Standard with Dedicated Storage Installation R5.0
Overview Overview
-------- --------
.. include:: ../desc_dedicated_storage.txt .. include:: /shared/_includes/r5_desc_dedicated_storage.txt
.. include:: ../ipv6_note.txt .. include:: /shared/_includes/r5_ipv6_note.txt
------------ ------------
Installation Installation

2
doc/source/deploy_install_guides/r5_release/virtual/dedicated_storage_install_kubernetes.rst
View File

@@ -399,4 +399,4 @@ Unlock worker nodes
Next steps Next steps
---------- ----------
.. include:: ../kubernetes_install_next.txt .. include:: /_includes/r5_kubernetes_install_next.txt

4
doc/source/deploy_install_guides/r5_release/virtual/install_virtualbox.rst
View File

@@ -324,7 +324,7 @@ Controller Node Install vs Graphics Controller Node Install), and hitting the
tab key to allow command line modification. The example below shows how to tab key to allow command line modification. The example below shows how to
modify the ``rootfs_device`` specification. modify the ``rootfs_device`` specification.
.. figure:: ../figures/install_virtualbox_configparms.png .. figure:: /deploy_install_guides/r5_release/figures/install_virtualbox_configparms.png
:scale: 100% :scale: 100%
:alt: Install controller-0 :alt: Install controller-0
@@ -361,6 +361,6 @@ If you’d prefer to install to the second disk on your node, use the command:
Alternatively, these values can be set from the GUI via the ``Edit Host`` Alternatively, these values can be set from the GUI via the ``Edit Host``
option. option.
.. figure:: ../figures/install_virtualbox_guiscreen.png .. figure:: /deploy_install_guides/r5_release/figures/install_virtualbox_guiscreen.png
:scale: 100% :scale: 100%
:alt: Install controller-0 :alt: Install controller-0

4
doc/source/deploy_install_guides/r5_release/virtual/rook_storage.rst
View File

@@ -6,9 +6,9 @@ Virtual Standard with Rook Storage Installation R5.0
Overview Overview
-------- --------
.. include:: ../desc_rook_storage.txt .. include:: /shared/_includes/r5_desc_rook_storage.txt
.. include:: ../ipv6_note.txt .. include:: /shared/_includes/r5_ipv6_note.txt
------------ ------------
Installation Installation

2
doc/source/deploy_install_guides/r5_release/virtual/rook_storage_install_kubernetes.rst
View File

@@ -543,4 +543,4 @@ On virtual storage-0 and storage-1:
Next steps Next steps
---------- ----------
.. include:: ../kubernetes_install_next.txt .. include:: /_includes/r5_kubernetes_install_next.txt

2
doc/source/developer_resources/backup_restore.rst
View File

@@ -182,7 +182,7 @@ The backup contains the following:
* Docker registries on controller * Docker registries on controller
* Docker proxy (See :doc:`../configuration/docker_proxy_config` for details.) * Docker proxy (See :ref:`docker_proxy_config` for details.)
* Backup data: * Backup data:

2
doc/source/developer_resources/debug_issues.rst
View File

@@ -111,7 +111,7 @@ Implement fixes
* Make the changes in your *development workspace* with the StarlingX * Make the changes in your *development workspace* with the StarlingX
codebase. codebase.
* Build the related packages using ``build-pkgs <package_name>``. * Build the related packages using ``build-pkgs <package_name>``.
* Create and apply the patch using the :doc:`starlingx_patching` guide. * Create and apply the patch using the :ref:`starlingx_patching` guide.
* Restart the services using the ``systemctl`` command or the StarlingX * Restart the services using the ``systemctl`` command or the StarlingX
``sm`` (service management) command. ``sm`` (service management) command.

2
doc/source/developer_resources/starlingx_patching.rst
View File

@@ -1,3 +1,5 @@
.. _starlingx_patching:
================== ==================
StarlingX patching StarlingX patching
================== ==================

2
doc/source/developer_resources/stx_ipv6_deployment.rst
View File

@@ -1,3 +1,5 @@
.. _stx_ipv6_deployment:
========================= =========================
StarlingX IPv6 Deployment StarlingX IPv6 Deployment
========================= =========================

2
doc/source/fault-mgmt/kubernetes/100-series-alarm-messages.rst
View File

@@ -10,7 +10,7 @@ The system inventory and maintenance service reports system changes with
different degrees of severity. Use the reported alarms to monitor the overall different degrees of severity. Use the reported alarms to monitor the overall
health of the system. health of the system.
.. include:: ../../_includes/x00-series-alarm-messages.rest .. include:: /_includes/x00-series-alarm-messages.rest
.. _100-series-alarm-messages-table-zrd-tg5-v5: .. _100-series-alarm-messages-table-zrd-tg5-v5:

2
doc/source/fault-mgmt/kubernetes/200-series-alarm-messages.rst
View File

@@ -10,7 +10,7 @@ The system inventory and maintenance service reports system changes with
different degrees of severity. Use the reported alarms to monitor the overall different degrees of severity. Use the reported alarms to monitor the overall
health of the system. health of the system.
.. include:: ../../_includes/x00-series-alarm-messages.rest .. include:: /_includes/x00-series-alarm-messages.rest
.. _200-series-alarm-messages-table-zrd-tg5-v5: .. _200-series-alarm-messages-table-zrd-tg5-v5:

2
doc/source/fault-mgmt/kubernetes/300-series-alarm-messages.rst
View File

@@ -10,7 +10,7 @@ The system inventory and maintenance service reports system changes with
different degrees of severity. Use the reported alarms to monitor the different degrees of severity. Use the reported alarms to monitor the
overall health of the system. overall health of the system.
.. include:: ../../_includes/x00-series-alarm-messages.rest .. include:: /_includes/x00-series-alarm-messages.rest
.. _300-series-alarm-messages-table-zrd-tg5-v5: .. _300-series-alarm-messages-table-zrd-tg5-v5:

2
doc/source/fault-mgmt/kubernetes/400-series-alarm-messages.rst
View File

@@ -10,7 +10,7 @@ The system inventory and maintenance service reports system changes with
different degrees of severity. Use the reported alarms to monitor the overall different degrees of severity. Use the reported alarms to monitor the overall
health of the system. health of the system.
.. include:: ../../_includes/x00-series-alarm-messages.rest .. include:: /_includes/x00-series-alarm-messages.rest
.. _400-series-alarm-messages-table-zrd-tg5-v5: .. _400-series-alarm-messages-table-zrd-tg5-v5:

2
doc/source/fault-mgmt/kubernetes/500-series-alarm-messages.rst
View File

@@ -10,7 +10,7 @@ The system inventory and maintenance service reports system changes with
different degrees of severity. Use the reported alarms to monitor the overall different degrees of severity. Use the reported alarms to monitor the overall
health of the system. health of the system.
.. include:: ../../_includes/x00-series-alarm-messages.rest .. include:: /_includes/x00-series-alarm-messages.rest
.. _500-series-alarm-messages-table-zrd-tg5-v5: .. _500-series-alarm-messages-table-zrd-tg5-v5:

2
doc/source/fault-mgmt/kubernetes/750-series-alarm-messages.rst
View File

@@ -10,7 +10,7 @@ The system inventory and maintenance service reports system changes with
different degrees of severity. Use the reported alarms to monitor the overall different degrees of severity. Use the reported alarms to monitor the overall
health of the system. health of the system.
.. include:: ../../_includes/x00-series-alarm-messages.rest .. include:: /_includes/x00-series-alarm-messages.rest
.. _750-series-alarm-messages-table-zrd-tg5-v5: .. _750-series-alarm-messages-table-zrd-tg5-v5:

2
doc/source/fault-mgmt/kubernetes/800-series-alarm-messages.rst
View File

@@ -10,7 +10,7 @@ The system inventory and maintenance service reports system changes with
different degrees of severity. Use the reported alarms to monitor the overall different degrees of severity. Use the reported alarms to monitor the overall
health of the system. health of the system.
.. include:: ../../_includes/x00-series-alarm-messages.rest .. include:: /_includes/x00-series-alarm-messages.rest
.. _800-series-alarm-messages-table-zrd-tg5-v5: .. _800-series-alarm-messages-table-zrd-tg5-v5:

2
doc/source/fault-mgmt/kubernetes/900-series-alarm-messages.rst
View File

@@ -10,7 +10,7 @@ The system inventory and maintenance service reports system changes with
different degrees of severity. Use the reported alarms to monitor the overall different degrees of severity. Use the reported alarms to monitor the overall
health of the system. health of the system.
.. include:: ../../_includes/x00-series-alarm-messages.rest .. include:: /_includes/x00-series-alarm-messages.rest
.. _900-series-alarm-messages-table-zrd-tg5-v5: .. _900-series-alarm-messages-table-zrd-tg5-v5:

2
doc/source/fault-mgmt/kubernetes/events-suppression-overview.rst
View File

@@ -28,6 +28,6 @@ You can sort events by clicking the **Event ID**, **Description**, and
**Status** column headers. You can also use these as filtering criteria **Status** column headers. You can also use these as filtering criteria
from the **Search** field. from the **Search** field.
.. figure:: ../figures/uty1463514747661.png .. figure:: /shared/figures/fault-mgmt/uty1463514747661.png
:scale: 70 % :scale: 70 %
:alt: Event Suppression :alt: Event Suppression

2
doc/source/fault-mgmt/kubernetes/suppressing-and-unsuppressing-events.rst
View File

@@ -34,4 +34,4 @@ You can set events to a suppressed state and toggle them back to unsuppressed.
replaced by **Unsuppress Event**, providing a way to toggle the event back replaced by **Unsuppress Event**, providing a way to toggle the event back
to unsuppressed. to unsuppressed.
.. image:: ../figures/nlc1463584178366.png .. image:: /shared/figures/fault-mgmt/nlc1463584178366.png

2
doc/source/fault-mgmt/kubernetes/the-global-alarm-banner.rst
View File

@@ -14,7 +14,7 @@ that is always visible, regardless of what page you are on in the GUI. The
banner provides a color-coded snapshot of current active alarm counts for each banner provides a color-coded snapshot of current active alarm counts for each
alarm severity. alarm severity.
.. image:: ../figures/xyj1558447807645.png .. image:: /shared/figures/fault-mgmt/xyj1558447807645.png
.. note:: .. note::
Suppressed alarms are not shown. For more about suppressed alarms, see Suppressed alarms are not shown. For more about suppressed alarms, see

2
doc/source/fault-mgmt/kubernetes/troubleshooting-log-collection.rst
View File

@@ -96,4 +96,4 @@ Collect Tool Caveats and Usage
.. only:: partner .. only:: partner
.. include:: ../../_includes/troubleshooting-log-collection.rest .. include:: /_includes/troubleshooting-log-collection.rest

2
doc/source/fault-mgmt/kubernetes/viewing-the-event-log-using-horizon.rst
View File

@@ -45,7 +45,7 @@ buffer, with older entries discarded as needed to release logging space.
The **Suppression Status** column is only shown in the table when The **Suppression Status** column is only shown in the table when
**Show Suppressed** filter button is selected. **Show Suppressed** filter button is selected.
.. image:: ../figures/psa1567524091300.png .. image:: /shared/figures/fault-mgmt/psa1567524091300.png
You can sort the entries by clicking on the column titles. For example, to You can sort the entries by clicking on the column titles. For example, to
sort the view of the entries by severity, click **Severity**; the entries sort the view of the entries by severity, click **Severity**; the entries

2
doc/source/node_management/kubernetes/common_host_tasks/deleting-a-host-using-horizon.rst
View File

@@ -22,5 +22,5 @@ hard drive.
#. From the **Edit** menu for the host, select **Delete Host**. #. From the **Edit** menu for the host, select **Delete Host**.
.. figure:: ../figures/mwl1579716430090.png .. figure:: /node_management/kubernetes/figures/mwl1579716430090.png
:scale: 100% :scale: 100%

2
doc/source/node_management/kubernetes/common_host_tasks/force-locking-a-host-using-horizon.rst
View File

@@ -30,7 +30,7 @@ configuration and maintenance purposes.
#. From the **Edit** menu for the host, select **Force Lock Host**. #. From the **Edit** menu for the host, select **Force Lock Host**.
.. figure:: ../figures/xwu1579713699282.png .. figure:: /node_management/kubernetes/figures/xwu1579713699282.png
:scale: 100% :scale: 100%
The system displays a warning message appropriate to the The system displays a warning message appropriate to the

2
doc/source/node_management/kubernetes/common_host_tasks/locking-a-host-using-horizon.rst
View File

@@ -37,5 +37,5 @@ the host, causing any containers on that host to be evicted.
#. From the **Edit** menu for the host, select **Lock Host**. #. From the **Edit** menu for the host, select **Lock Host**.
.. figure:: ../figures/rst1442611298701.png .. figure:: /shared/figures/system_configuration/rst1442611298701.png
:scale: 100% :scale: 100%

2
doc/source/node_management/kubernetes/common_host_tasks/rebooting-a-host-using-horizon.rst
View File

@@ -23,5 +23,5 @@ The host then reboots automatically.
#. From the **Edit** menu for the host, select **Reboot Host**. #. From the **Edit** menu for the host, select **Reboot Host**.
.. figure:: ../figures/mwl1579716430090.png .. figure:: /node_management/kubernetes/figures/mwl1579716430090.png
:scale: 100% :scale: 100%

2
doc/source/node_management/kubernetes/common_host_tasks/reinstalling-a-host-using-horizon.rst
View File

@@ -54,5 +54,5 @@ the network interfaces through the BIOS boot option.
#. From the **Edit** menu for the host, select **Reinstall Host**. #. From the **Edit** menu for the host, select **Reinstall Host**.
.. figure:: ../figures/mwl1579716430090.png .. figure:: /node_management/kubernetes/figures/mwl1579716430090.png
:scale: 100% :scale: 100%

2
doc/source/node_management/kubernetes/common_host_tasks/swacting-a-master-controller-using-horizon.rst
View File

@@ -26,5 +26,5 @@ when updating hardware or replacing faulty components.
#. From the **Edit** menu for the standby controller, select **Swact Host**. #. From the **Edit** menu for the standby controller, select **Swact Host**.
.. figure:: ../figures/wwd1579715313055.png .. figure:: /node_management/kubernetes/figures/wwd1579715313055.png
:scale: 100% :scale: 100%

2
doc/source/node_management/kubernetes/common_host_tasks/unlocking-a-host-using-horizon.rst
View File

@@ -34,5 +34,5 @@ see :ref:`Reboot Limits for Host Unlock <reboot-limits-for-host-unlock>`.
#. From the **Edit** menu for the host, select **Unlock Host**. #. From the **Edit** menu for the host, select **Unlock Host**.
.. figure:: ../figures/mwl1579716430090.png .. figure:: /node_management/kubernetes/figures/mwl1579716430090.png
:scale: 100% :scale: 100%

6
doc/source/node_management/kubernetes/configuring_cpu_core_assignments/configuring-cpu-core-assignments.rst
View File

@@ -33,7 +33,7 @@ CPU cores from the Horizon Web interface.
The Edit CPU Assignments dialog appears. The Edit CPU Assignments dialog appears.
.. figure:: ../figures/tku1572941730454.png .. figure:: /node_management/kubernetes/figures/tku1572941730454.png
:scale: 100% :scale: 100%
#. Make CPU allocation changes. #. Make CPU allocation changes.
@@ -82,7 +82,7 @@ CPU cores from the Horizon Web interface.
.. only:: partner .. only:: partner
../../_includes/configure-cpu-core-vswitch.rest /_includes/configure-cpu-core-vswitch.rest
**Shared** **Shared**
Not currently supported. Not currently supported.
@@ -90,5 +90,5 @@ CPU cores from the Horizon Web interface.
To see how many cores a processor contains, hover over the To see how many cores a processor contains, hover over the
**Information** icon. **Information** icon.
.. figure:: ../figures/jow1436300231676.png .. figure:: /node_management/kubernetes/figures/jow1436300231676.png
:scale: 100% :scale: 100%

2
doc/source/node_management/kubernetes/configuring_node_labels/configuring-node-labels-using-horizon.rst
View File

@@ -20,7 +20,7 @@ You can assign and remove labels to modify node functionality using Horizon.
#. Select the Labels tab. #. Select the Labels tab.
.. figure:: ../figures/qes1567103095290.png .. figure:: /node_management/kubernetes/figures/qes1567103095290.png
:scale: 100% :scale: 100%
#. To delete a label, select the **Delete Label** button for the label key #. To delete a label, select the **Delete Label** button for the label key

2
doc/source/node_management/kubernetes/customizing_the_host_life_cycles/configuring-heartbeat-failure-action.rst
View File

@@ -101,7 +101,7 @@ Customer logs are created. The customer can change from one action to any
other action at any time and the log reflects the from <action> to <action> other action at any time and the log reflects the from <action> to <action>
change in the log text. For example, change in the log text. For example,
.. figure:: ../figures/wnz1537822287984.jpeg .. figure:: /node_management/kubernetes/figures/wnz1537822287984.jpeg
:scale: 65% :scale: 65%
The heartbeat alarms, such as Management Network can be viewed. For example: The heartbeat alarms, such as Management Network can be viewed. For example:

2
doc/source/node_management/kubernetes/customizing_the_host_life_cycles/configuring-multi-node-failure-avoidance.rst
View File

@@ -76,7 +76,7 @@ heartbeat failures.
Customer logs are created. The customer logs record **from** and **to** Customer logs are created. The customer logs record **from** and **to**
changes in the log text. For example: changes in the log text. For example:
.. figure:: ../figures/oio1537823446860.jpeg .. figure:: /node_management/kubernetes/figures/oio1537823446860.jpeg
:scale: 65% :scale: 65%
#. Apply the service parameter change. #. Apply the service parameter change.

2
doc/source/node_management/kubernetes/host_hardware_sensors/adjusting-sensor-actions-and-audit-intervals.rst
View File

@@ -31,7 +31,7 @@ To use the command-line interface, see :ref:`CLI Commands for Managing Sensors
#. In the **Sensor Groups** list, click **Edit SensorGroup** for the #. In the **Sensor Groups** list, click **Edit SensorGroup** for the
group you want to configure. group you want to configure.
.. figure:: ../figures/jow1443885204993.png .. figure:: /node_management/kubernetes/figures/jow1443885204993.png
:scale: 100% :scale: 100%
In the Edit SensorGroup dialog box, change the settings as required. In the Edit SensorGroup dialog box, change the settings as required.

2
doc/source/node_management/kubernetes/host_hardware_sensors/relearning-sensor-models.rst
View File

@@ -50,7 +50,7 @@ for your system.
#. On the Sensors page, click **Relearn Sensor Model**. #. On the Sensors page, click **Relearn Sensor Model**.
.. figure:: ../figures/eoc1497190198018.png .. figure:: /node_management/kubernetes/figures/eoc1497190198018.png
:scale: 100% :scale: 100%
Allow about two minutes for the sensor information to be updated. Allow about two minutes for the sensor information to be updated.

4
doc/source/node_management/kubernetes/host_hardware_sensors/suppressing-sensor-actions.rst
View File

@@ -43,11 +43,11 @@ see :ref:`CLI Commands for Managing Sensors <cli-commands-for-managing-sensors>`
+------------------------------+--------------------------------------------------------------------------------------------------------------------------------+ +------------------------------+--------------------------------------------------------------------------------------------------------------------------------+
| **For a group of sensors** | To suppress actions for a group of sensors, open the **Actions** menu for the group, and then select **Suppress SensorGroup**. | | **For a group of sensors** | To suppress actions for a group of sensors, open the **Actions** menu for the group, and then select **Suppress SensorGroup**. |
| | | | | |
| | .. figure:: ../figures/jow1443890971677.png | | | .. figure:: /node_management/kubernetes/figures/jow1443890971677.png |
+------------------------------+--------------------------------------------------------------------------------------------------------------------------------+ +------------------------------+--------------------------------------------------------------------------------------------------------------------------------+
| **For an individual sensor** | To suppress actions for an individual sensor, locate the sensor in the **Sensors** list, and click **Suppress Sensor**. | | **For an individual sensor** | To suppress actions for an individual sensor, locate the sensor in the **Sensors** list, and click **Suppress Sensor**. |
| | | | | |
| | .. figure:: ../figures/jow1443890898358.png | | | .. figure:: /node_management/kubernetes/figures/jow1443890898358.png |
+------------------------------+--------------------------------------------------------------------------------------------------------------------------------+ +------------------------------+--------------------------------------------------------------------------------------------------------------------------------+
.. rubric:: |result| .. rubric:: |result|

2
doc/source/node_management/kubernetes/host_inventory/devices-tab.rst
View File

@@ -14,7 +14,7 @@ All non-|NIC| |PCI| devices that can be exposed
to a guest application are listed. They are automatically detected by the to a guest application are listed. They are automatically detected by the
system, and cannot be manually added or deleted. system, and cannot be manually added or deleted.
.. figure:: ../figures/szv1567164542479.png .. figure:: /node_management/kubernetes/figures/szv1567164542479.png
:scale: 100% :scale: 100%
.. note:: .. note::

2
doc/source/node_management/kubernetes/host_inventory/filesystems-tab.rst
View File

@@ -9,7 +9,7 @@ Filesystems Tab
The **Filesystems** tab on the Host Detail page presents file system details The **Filesystems** tab on the Host Detail page presents file system details
for a host. for a host.
.. figure:: ../figures/mov1566319898101.png .. figure:: /node_management/kubernetes/figures/mov1566319898101.png
:scale: 100% :scale: 100%
The **Filesystems** tab includes the following items: The **Filesystems** tab includes the following items:

4
doc/source/node_management/kubernetes/host_inventory/hosts-tab.rst
View File

@@ -12,7 +12,7 @@ detailed information about the hosts, and execute maintenance operations.
A sample **Hosts** tab is illustrated below: A sample **Hosts** tab is illustrated below:
.. figure:: ../figures/jpx1567098739405.png .. figure:: /node_management/kubernetes/figures/jpx1567098739405.png
:scale: 100% :scale: 100%
**Host Name** **Host Name**
@@ -139,7 +139,7 @@ A sample **Hosts** tab is illustrated below:
The **Edit Host** button displays the Edit Host window, as illustrated The **Edit Host** button displays the Edit Host window, as illustrated
below for a worker node: below for a worker node:
.. figure:: ../figures/gkb1569351598356.png .. figure:: /node_management/kubernetes/figures/gkb1569351598356.png
:scale: 100% :scale: 100%
This is the same window you use to assign the host's personality when This is the same window you use to assign the host's personality when

2
doc/source/node_management/kubernetes/host_inventory/interfaces-tab.rst
View File

@@ -11,7 +11,7 @@ logical L2 network interfaces on a node.
The following example is for an unlocked controller node: The following example is for an unlocked controller node:
.. figure:: ../figures/hxu1567097201027.png .. figure:: /node_management/kubernetes/figures/hxu1567097201027.png
:scale: 100% :scale: 100%
On a configured worker node, the Interfaces tab may include additional On a configured worker node, the Interfaces tab may include additional

2
doc/source/node_management/kubernetes/host_inventory/labels-tab.rst
View File

@@ -12,7 +12,7 @@ review the labels attached to a host.
The Labels tab displays the list of Kubernetes labels and their values The Labels tab displays the list of Kubernetes labels and their values
assigned to the current host. assigned to the current host.
.. figure:: ../figures/qes1567103095290.png .. figure:: /node_management/kubernetes/figures/qes1567103095290.png
:scale: 100% :scale: 100%
Use the **Assign Kube Label** button to select additional host labels. Use the **Assign Kube Label** button to select additional host labels.

2
doc/source/node_management/kubernetes/host_inventory/lldp-tab.rst
View File

@@ -12,7 +12,7 @@ neighbors' ports though the Link Layer Discovery Protocol.
The **LLDP** tab provides the following information about each LLDP-enabled The **LLDP** tab provides the following information about each LLDP-enabled
neighbor device: neighbor device:
.. figure:: ../figures/blp1567103635948.png .. figure:: /node_management/kubernetes/figures/blp1567103635948.png
:scale: 100% :scale: 100%
------------ ------------

2
doc/source/node_management/kubernetes/host_inventory/memory-tab.rst
View File

@@ -8,7 +8,7 @@ Memory Tab
The **Memory** tab on the Host Detail page displays host memory details. The **Memory** tab on the Host Detail page displays host memory details.
.. figure:: ../figures/qjh1567165597148.png .. figure:: /node_management/kubernetes/figures/qjh1567165597148.png
:scale: 100% :scale: 100%
The information is presented in three columns, as follows: The information is presented in three columns, as follows:

2
doc/source/node_management/kubernetes/host_inventory/overview-tab.rst
View File

@@ -9,7 +9,7 @@ Overview Tab
The **Overview** tab on the Host Detail page summarizes essential information The **Overview** tab on the Host Detail page summarizes essential information
about a host object. about a host object.
.. figure:: ../figures/pcd1567096217474.png .. figure:: /node_management/kubernetes/figures/pcd1567096217474.png
:scale: 100% :scale: 100%

2
doc/source/node_management/kubernetes/host_inventory/ports-tab.rst
View File

@@ -9,7 +9,7 @@ Ports Tab
The **Ports** tab on the Host Detail page presents information about the The **Ports** tab on the Host Detail page presents information about the
physical ports on a host. physical ports on a host.
.. figure:: ../figures/iln1567164165572.png .. figure:: /node_management/kubernetes/figures/iln1567164165572.png
:scale: 100% :scale: 100%
Currently none of the port attributes is configurable; they are all read Currently none of the port attributes is configurable; they are all read

2
doc/source/node_management/kubernetes/host_inventory/processor-tab.rst
View File

@@ -9,7 +9,7 @@ Processor Tab
The **Processor** tab on the Host Detail page presents processor details for The **Processor** tab on the Host Detail page presents processor details for
a host. a host.
.. figure:: ../figures/ldv1567165392491.png .. figure:: /node_management/kubernetes/figures/ldv1567165392491.png
:scale: 100% :scale: 100%

2
doc/source/node_management/kubernetes/host_inventory/sensors-tab.rst
View File

@@ -13,7 +13,7 @@ This tab lists the available |BMC| sensors and
shows their status. It also lists sensor groups that have been defined for shows their status. It also lists sensor groups that have been defined for
the sensors. the sensors.
.. figure:: ../figures/jow1443825878164.png .. figure:: /node_management/kubernetes/figures/jow1443825878164.png
:scale: 100% :scale: 100%
.. _sensors-tab-section-N1006C-N10029-N10001: .. _sensors-tab-section-N1006C-N10029-N10001:

8
doc/source/node_management/kubernetes/host_inventory/storage-tab.rst
View File

@@ -21,7 +21,7 @@ Disks
This list is presented for all host types. It lists all available hardware This list is presented for all host types. It lists all available hardware
devices used for storage. devices used for storage.
.. figure:: ../figures/bsa1464962126609.png .. figure:: /node_management/kubernetes/figures/bsa1464962126609.png
:scale: 100% :scale: 100%
For each device, the following information is included: For each device, the following information is included:
@@ -58,7 +58,7 @@ Partitions
For all host types, this list shows user-created disk partitions. For all host types, this list shows user-created disk partitions.
.. figure:: ../figures/lci1515513441685.png .. figure:: /node_management/kubernetes/figures/lci1515513441685.png
:scale: 100% :scale: 100%
**UUID** **UUID**
@@ -88,7 +88,7 @@ Physical Volumes
On controller and worker hosts, this list shows physical volumes On controller and worker hosts, this list shows physical volumes
\(disk or partitions\) assigned to local volume groups. \(disk or partitions\) assigned to local volume groups.
.. figure:: ../figures/fph1515514594885.png .. figure:: /node_management/kubernetes/figures/fph1515514594885.png
:scale: 100% :scale: 100%
**Name** **Name**
@@ -123,7 +123,7 @@ Storage Functions
This list is presented for storage hosts. It shows a list of logical storage This list is presented for storage hosts. It shows a list of logical storage
functions \(OSDs and Ceph journal functions\) defined on available disks. functions \(OSDs and Ceph journal functions\) defined on available disks.
.. figure:: ../figures/caf1464886132887.png .. figure:: /shared/figures/storage/caf1464886132887.png
:scale: 100% :scale: 100%
For each volume, the following information is included: For each volume, the following information is included:

8
doc/source/node_management/kubernetes/host_memory_provisioning/allocating-host-memory-using-horizon.rst
View File

@@ -46,7 +46,7 @@ from the available memory, an informative message is displayed.
#. On the **Memory** tab, click **Update Memory**. #. On the **Memory** tab, click **Update Memory**.
.. figure:: ../figures/esy1567176125909.png .. figure:: /node_management/kubernetes/figures/esy1567176125909.png
:scale: 100% :scale: 100%
#. Use the Update Memory Allocation dialog box to set the memory allocations #. Use the Update Memory Allocation dialog box to set the memory allocations
@@ -59,7 +59,7 @@ from the available memory, an informative message is displayed.
in Kubernetes, only a single huge page size can be used per host, across in Kubernetes, only a single huge page size can be used per host, across
Application memory. Application memory.
.. figure:: ../figures/yfv1567176747837.png .. figure:: /node_management/kubernetes/figures/yfv1567176747837.png
:scale: 100% :scale: 100%
.. only:: partner .. only:: partner
@@ -75,7 +75,7 @@ from the available memory, an informative message is displayed.
minimum requirement, hover over the information icon next to the minimum requirement, hover over the information icon next to the
field. field.
.. figure:: ../figures/jow1436294915672.png .. figure:: /node_management/kubernetes/figures/jow1436294915672.png
:scale: 100% :scale: 100%
**\# of Application 2M Hugepages Node n** **\# of Application 2M Hugepages Node n**
@@ -124,7 +124,7 @@ from the available memory, an informative message is displayed.
on a node \(assuming that pages of another size are not also requested\), on a node \(assuming that pages of another size are not also requested\),
hover over the information icon next to the field. hover over the information icon next to the field.
.. figure:: ../figures/jow1432129731308.png .. figure:: /node_management/kubernetes/figures/jow1432129731308.png
:scale: 100% :scale: 100%
Any unused memory is automatically allocated as 4 KiB pages of regular Any unused memory is automatically allocated as 4 KiB pages of regular

6
doc/source/node_management/kubernetes/node_interfaces/configuring-aggregated-ethernet-interfaces-using-horizon.rst
View File

@@ -29,12 +29,12 @@ for different types of interface, see :ref:`Interface Settings
#. Select the **Interfaces** tab. #. Select the **Interfaces** tab.
.. figure:: ../figures/zbl1538147657952.png .. figure:: /node_management/kubernetes/figures/zbl1538147657952.png
:scale: 100% :scale: 100%
#. Click **Create Interface**. #. Click **Create Interface**.
.. figure:: ../figures/bpw1538149046903.png .. figure:: /node_management/kubernetes/figures/bpw1538149046903.png
:scale: 100% :scale: 100%
#. Select the class of the interface, from the **Interface Class** drop-down #. Select the class of the interface, from the **Interface Class** drop-down
@@ -69,4 +69,4 @@ The interface is created and attached to the network.
.. only:: partner .. only:: partner
.. include:: ../../../_includes/configuring-aggregated-ethernet-interfaces-using-horizon.rest .. include:: /_includes/configuring-aggregated-ethernet-interfaces-using-horizon.rest

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

@@ -13,7 +13,7 @@ Ethernet interfaces to networks.
.. only:: partner .. only:: partner
../../../_includes/configuring-aggregated-ethernet-interfaces-using-the-cli.rest /_includes/configuring-aggregated-ethernet-interfaces-using-the-cli.rest
For more about link aggregation modes and policies, see :ref:`Link Aggregation For more about link aggregation modes and policies, see :ref:`Link Aggregation
Settings <link-aggregation-settings>`. Settings <link-aggregation-settings>`.

6
doc/source/node_management/kubernetes/node_interfaces/configuring-ethernet-interfaces-on-sriov-interface-from-horizon.rst
View File

@@ -21,7 +21,7 @@ the CLI <provisioning-sr-iov-interfaces-using-the-cli>`.
\> **Host Inventory** in the left-hand panel, under **Actions** click on the \> **Host Inventory** in the left-hand panel, under **Actions** click on the
down arrow button on "Edit Host" and select "Lock Host". down arrow button on "Edit Host" and select "Lock Host".
.. image:: ../figures/rst1442611298701.png .. image:: /shared/figures/system_configuration/rst1442611298701.png
:width: 550 :width: 550
#. Open the Host Detail page for the host. #. Open the Host Detail page for the host.
@@ -36,7 +36,7 @@ the CLI <provisioning-sr-iov-interfaces-using-the-cli>`.
#. Select the **Interfaces** tab. #. Select the **Interfaces** tab.
.. image:: ../figures/vpw1612788524636.png .. image:: /node_management/kubernetes/figures/vpw1612788524636.png
#. Open the **Host Inventory** page, available from **Admin** \> **Platform** #. Open the **Host Inventory** page, available from **Admin** \> **Platform**
\> **Host Inventory** in the left-hand panel, under **Actions** click on the \> **Host Inventory** in the left-hand panel, under **Actions** click on the
@@ -56,4 +56,4 @@ the CLI <provisioning-sr-iov-interfaces-using-the-cli>`.
#. Click **Create Interface** to save your changes and close the dialog box. #. Click **Create Interface** to save your changes and close the dialog box.
.. image:: ../figures/qes1612788640104.png .. image:: /node_management/kubernetes/figures/qes1612788640104.png

4
doc/source/node_management/kubernetes/node_interfaces/configuring-ethernet-interfaces-using-horizon.rst
View File

@@ -46,13 +46,13 @@ see :ref:`Interface Settings <interface-settings>`.
#. Select the **Interfaces** tab. #. Select the **Interfaces** tab.
.. figure:: ../figures/zbl1538147657952.png .. figure:: /node_management/kubernetes/figures/zbl1538147657952.png
:scale: 100% :scale: 100%
#. Click **Edit Interface** for the interface you want to attach to a #. Click **Edit Interface** for the interface you want to attach to a
network. network.
.. figure:: ../figures/bvb1538146331222.png .. figure:: /node_management/kubernetes/figures/bvb1538146331222.png
:scale: 100% :scale: 100%
For an Ethernet interface, the **Port** is already selected. For an Ethernet interface, the **Port** is already selected.

4
doc/source/node_management/kubernetes/node_interfaces/configuring-vlan-interfaces-using-horizon.rst
View File

@@ -32,12 +32,12 @@ can do this using the Horizon Web interface or the CLI.
#. Select the **Interfaces** tab. #. Select the **Interfaces** tab.
.. figure:: ../figures/zbl1538147657952.png .. figure:: /node_management/kubernetes/figures/zbl1538147657952.png
:scale: 100% :scale: 100%
#. Click **Create Interface**. #. Click **Create Interface**.
.. figure:: ../figures/bpw1538149046903.png .. figure:: /node_management/kubernetes/figures/bpw1538149046903.png
:scale: 100% :scale: 100%
#. Select the type of network for the interface. #. Select the type of network for the interface.

4
doc/source/node_management/kubernetes/node_interfaces/deleting-or-disabling-interfaces-using-horizon.rst
View File

@@ -26,12 +26,12 @@ You can delete an interface using the Horizon Web interface.
+-------------------------------------------+--------------------------------------------------------------------------------------------+ +-------------------------------------------+--------------------------------------------------------------------------------------------+
| **To delete a non-Ethernet Interface** | Select **Delete Interface** from the **Actions** menu for the interface. | | **To delete a non-Ethernet Interface** | Select **Delete Interface** from the **Actions** menu for the interface. |
| | | | | |
| | .. figure:: ../figures/wuq1538163902474.png | | | .. figure:: /node_management/kubernetes/figures/wuq1538163902474.png |
| | :scale: 60% | | | :scale: 60% |
+-------------------------------------------+--------------------------------------------------------------------------------------------+ +-------------------------------------------+--------------------------------------------------------------------------------------------+
| **To disable an Ethernet Interface** | #. Select **Edit Interface** from the **Actions** menu for the interface. | | **To disable an Ethernet Interface** | #. Select **Edit Interface** from the **Actions** menu for the interface. |
| | | | | |
| | #. In the Edit Interface pop-up, set **Interface Class** to None and select **Save**. | | | #. In the Edit Interface pop-up, set **Interface Class** to None and select **Save**. |
| | | | | |
| | .. figure:: ../figures/juc1579524423575.png | | | .. figure:: /node_management/kubernetes/figures/juc1579524423575.png |
+-------------------------------------------+--------------------------------------------------------------------------------------------+ +-------------------------------------------+--------------------------------------------------------------------------------------------+

4
doc/source/node_management/kubernetes/node_interfaces/editing-interface-settings.rst
View File

@@ -35,12 +35,12 @@ management network, you must update this manually to **aggregated ethernet**.
#. Select the **Interfaces** tab to display the existing interfaces. #. Select the **Interfaces** tab to display the existing interfaces.
.. figure:: ../figures/zbl1538147657952.png .. figure:: /node_management/kubernetes/figures/zbl1538147657952.png
:scale: 100% :scale: 100%
#. Click **Edit Interface** for the interface you want to change. #. Click **Edit Interface** for the interface you want to change.
.. figure:: ../figures/bvb1538146331222.png .. figure:: /node_management/kubernetes/figures/bvb1538146331222.png
:scale: 100% :scale: 100%
#. Make the required changes and then click **Save**. #. Make the required changes and then click **Save**.

2
doc/source/node_management/kubernetes/node_interfaces/provisioning-sr-iov-vf-interfaces-using-the-cli.rst
View File

@@ -113,7 +113,7 @@ For more information, see :ref:`Provision SR-IOV Interfaces using the CLI
.. only:: partner .. only:: partner
.. include:: ../../../_includes/provisioning-sr-iov-vf-interfaces-using-the-cli.rest .. include:: /_includes/provisioning-sr-iov-vf-interfaces-using-the-cli.rest
**networks** **networks**
A list of data networks that are attached to the interface, delimited A list of data networks that are attached to the interface, delimited

2
doc/source/node_management/kubernetes/node_inventory_tasks/starting-starlingx.rst
View File

@@ -69,5 +69,5 @@ shut down and physically moved.
#. On the Hosts tab of the **Admin** \> **Platform** \> #. On the Hosts tab of the **Admin** \> **Platform** \>
**Host Inventory** page, select **Edit Host** \> **Unlock Host**. **Host Inventory** page, select **Edit Host** \> **Unlock Host**.
.. figure:: ../figures/rst1446643548268.png .. figure:: /node_management/kubernetes/figures/rst1446643548268.png
:scale: 100% :scale: 100%

2
doc/source/node_management/kubernetes/provisioning_bmc/deprovisioning-board-management-control-from-horizon.rst
View File

@@ -26,7 +26,7 @@ For more information about |IPMI|, see:
#. Switch to the Board Management tab. #. Switch to the Board Management tab.
.. figure:: ../figures/sxl1575923501137.jpeg .. figure:: /node_management/kubernetes/figures/sxl1575923501137.jpeg
:scale: 80% :scale: 80%
#. From the **Board Management Controller Type** drop-down list, select #. From the **Board Management Controller Type** drop-down list, select

2
doc/source/node_management/kubernetes/provisioning_bmc/provisioning-board-management-control-from-horizon.rst
View File

@@ -32,7 +32,7 @@ Management Control from Horizon
#. Switch to the Board Management tab. #. Switch to the Board Management tab.
.. figure:: ../figures/sxl1575923501137.jpeg .. figure:: /node_management/kubernetes/figures/sxl1575923501137.jpeg
:scale: 80% :scale: 80%
#. From the **Board Management Controller Type** drop-down list, select #. From the **Board Management Controller Type** drop-down list, select

2
doc/source/node_management/openstack/adding-compute-nodes-to-an-existing-duplex-system.rst
View File

@@ -13,7 +13,7 @@ the standard procedures for adding compute nodes to a system.
.. only:: partner .. only:: partner
.. include:: ../../_includes/adding-compute-nodes-to-an-existing-duplex-system.rest .. include:: /_includes/adding-compute-nodes-to-an-existing-duplex-system.rest
Before adding compute nodes to a duplex system, you can either add and Before adding compute nodes to a duplex system, you can either add and
provision platform RAM and CPU cores on the controllers or reallocate RAM and provision platform RAM and CPU cores on the controllers or reallocate RAM and

2
doc/source/node_management/openstack/configuring-a-flavor-to-use-a-generic-pci-device.rst
View File

@@ -27,7 +27,7 @@ extra specification. From the |os-prod-hor| interface, use the **Custom
Extra Spec** selection in the **Create Flavor Extra Spec** drop-down menu. For Extra Spec** selection in the **Create Flavor Extra Spec** drop-down menu. For
the **Key**, use **pci\_passthrough:alias**. the **Key**, use **pci\_passthrough:alias**.
.. image:: ../figures/kho1513370501907.png .. image:: /node_management/figures/kho1513370501907.png

Some files were not shown because too many files have changed in this diff Show More