Minor provisioning SRIOV updates

Applied as continuation of merged https://review.opendev.org/c/starlingx/docs/+/783852
Updates based on patchset 1 comments.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: Iddc2c6852f189a9c07f225109d33aa312e1afa05
Signed-off-by: Ron Stone <ronald.stone@windriver.com>
This commit is contained in:
Ron Stone 2021-05-19 17:07:22 -04:00
parent 7ce412da79
commit 82e5971128
2 changed files with 10 additions and 1 deletions

View File

@ -38,7 +38,7 @@ See |datanet-doc|: :ref:`Add Data Networks using the CLI
#. Lock the host to which you will assign the label.
.. note::
AIO-SX hosts do not need to be locked to provision an |SRIOV|
|AIO-SX| hosts do not need to be locked to provision an |SRIOV|
interface and assign it to a data network.
For example:
@ -172,6 +172,7 @@ See |datanet-doc|: :ref:`Add Data Networks using the CLI
~(keystone_admin)$ system host-unlock compute-0
.. rubric:: |postreq|
When launching an |SRIOV|-enabled Kubernetes deployment, pods will only be

View File

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