starlingx/docs
Code Issues Proposed changes

Node Mgmt updates

Browse Source 
Implement two changes on this closed review:
https://review.opendev.org/c/starlingx/docs/+/783852/2/doc/source/node_management/kubernetes/node_interfaces/provisioning-sr-iov-interfaces-using-the-cli.rst#164

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: Ibc671a559464fb2b32884510967a6ca74c529b1f
This commit is contained in:
Ron Stone
2021-06-03 13:42:25 -04:00
parent 2bf222e02d
commit 0b4d34f078
2 changed files with 19 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
doc/source/node_management/kubernetes/node_interfaces/configuring-vf-interfaces-rate-limiting-using-cli.rst
View File

@@ -6,7 +6,7 @@
Configure VF Interfaces Rate Limiting Using the CLI Configure VF Interfaces Rate Limiting Using the CLI
===================================================== =====================================================
You can apply rate-limiting on VFs used for Data networks. You can apply rate-limiting on |VFs| used for Data networks.
.. rubric:: |context| .. rubric:: |context|
@@ -23,17 +23,17 @@ Be aware of the following guidance when using this feature:
- Rate limiting is disabled by default. - Rate limiting is disabled by default.
- If all VF's are in contention then each will get an equal share of the - If all |VFs| are in contention then each will get an equal share of the
bandwidth. bandwidth.
- The total sum of the maximum transmission rates of all rate limited VFs - The total sum of the maximum transmission rates of all rate limited |VFs|
cannot exceed 90% of the port link speed. cannot exceed 90% of the port link speed.
- The unit is Mbps, and value of 0 means turn off the rate limiting. - The unit is Mbps, and value of 0 means turn off the rate limiting.
- VFs with different limited rate are supposed to be attached separate data - |VFs| with different limited rate are supposed to be attached separate data
networks and managed by Kubernetes SR-IOV device plugin as different networks and managed by Kubernetes |SRIOV| device plugin as different
ResourcePools. You can then use the VFs by specifying the corresponding ResourcePools. You can then use the |VFs| by specifying the corresponding
<resourceName>. <resourceName>.
@@ -41,7 +41,7 @@ This task must be performed from the CLI.
.. rubric:: |prereq| .. rubric:: |prereq|
You must create an SR-IOV interface before you can provision VF interface. For You must create an |SRIOV| interface before you can provision VF interface. For
more information, see :ref:`Provisioning SR-IOV Interfaces using the CLI more information, see :ref:`Provisioning SR-IOV Interfaces using the CLI
<provisioning-sr-iov-interfaces-using-the-cli>`. <provisioning-sr-iov-interfaces-using-the-cli>`.
@@ -59,6 +59,10 @@ Data networks should be created for VF sub-interfaces attachment.
#. Lock the host. #. Lock the host.
.. note::
AIO-SX hosts do not need to be locked to provision an |SRIOV|
interface and assign it to a data network.
.. code-block:: none .. code-block:: none
~(keystone_admin)$ system host-lock controller-0 ~(keystone_admin)$ system host-lock controller-0
@@ -103,6 +107,10 @@ Data networks should be created for VF sub-interfaces attachment.
#. Unlock the host. #. Unlock the host.
.. note::
AIO-SX hosts do not need to be locked to provision an |SRIOV|
interface and assign it to a data network.
.. code-block:: none .. code-block:: none
~(keystone_admin)$ system host-unlock controller-0 ~(keystone_admin)$ system host-unlock controller-0

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

@@ -151,6 +151,10 @@ For more information, see :ref:`Provision SR-IOV Interfaces using the CLI
#. Unlock the host. #. Unlock the host.
.. note::
AIO-SX hosts do not need to be locked to provision an |SRIOV|
interface and assign it to a data network.
.. code-block:: none .. code-block:: none
~(keystone_admin)$ system host-unlock compute-0 ~(keystone_admin)$ system host-unlock compute-0