starlingx/docs
Code Issues Proposed changes

sriov-fec-operator upgrade (dsR8)

Browse Source 
Add procedure of how to switch between Static Method Hardware Accelerator and SR-IOV FEC operator

Story: 2010826
Task: 49079

Change-Id: Ic4ca05b97fc88662016f52c963d32988ca2dce19
Signed-off-by: Elisamara Aoki Goncalves <elisamaraaoki.goncalves@windriver.com>
This commit is contained in:
Elisamara Aoki Goncalves 2023-11-10 18:54:47 +00:00
parent 1f2da97166
commit b6807e2bf1
2 changed files with 74 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

73
doc/source/node_management/kubernetes/hardware_acceleration_devices/switch-between-static-method-hardware-accelerator-and-srminusi-5f893343ee15.rst Normal file
View File

@ -0,0 +1,73 @@
.. _switch-between-static-method-hardware-accelerator-and-srminusi-5f893343ee15:
=========================================================================
Switch between Static Method Hardware Accelerator and SR-IOV FEC Operator
=========================================================================
.. rubric:: |context|
The removal of the static device configuration requires a lock and unlock,
which is service impacting due to host reset. In addition, the |vRAN| Pods must
be reconfigured and recreated for this process, so the end-to-end service
impact will also be dependent on the application specific steps and recovery
process.
.. rubric:: |proc|
The following procedure allows to switch from the manual static method
configuration of a hardware accelerator device to the |SRIOV| |FEC| operator
method. This is necessary as it is not possible to use both methods at the same
time.
Taking in consideration that an accelerator card has been configured as in the
example in
:ref:`enabling-mount-bryce-hw-accelerator-for-hosted-vram-containerized-workloads`
to switch from Static to |SRIOV| |FEC| operator, follow the steps below.
.. note::
As the device will be reconfigured in Kubernetes, it may be required to
restart the app after switching methods.
#. Lock the node containing the accelerator card.
.. code-block:: none
$ source /etc/platform/openrc
~(keystone_admin)]$ system host-lock <hostname>
#. Remove the past configuration from the accelerator card with
:command:`host-device-modify` command.
.. code-block:: none
~(keystone_admin)]$ system host-device-modify <hostname> <pci_address> --vf-driver none -N 0
~(keystone_admin)]$ system host-device-modify <hostname> <pci_address> --driver none
#. Unlock the node containing the accelerator card.
.. code-block:: none
~(keystone_admin)]$ system host-unlock <hostname>
#. After the node finishes the unlocking process, find the |SRIOV| |FEC|
operator along with other applications at
``/usr/local/share/applications/helm/sriov-fec-operator-<version>.tgz``.
Follow the steps in
:ref:`configure-sriov-fec-operator-to-enable-hw-accelerators-for-hosted-vran-containarized-workloads`
to upload and apply |SRIOV| |FEC| operator, and to create the pods for the
suitable accelerator card.
.. note::
For compatibility between Static and |SRIOV| |FEC| operator, it is
recommended to keep the same resource name for the accelerator (ACC100 in
the example) while configuring |SRIOV| |FEC| operator using the following
command before apply the application:
.. code-block:: none
~(keystone_admin)$ system helm-override-update sriov-fec-operator sriov-fec-operator sriov-fec-system --set env.SRIOV_FEC_ACC100_RESOURCE_NAME=intel_acc100_fec

1
doc/source/node_management/kubernetes/index-node-mgmt-kub-5ff5993b9c60.rst
View File

@ -337,6 +337,7 @@ vRAN Accelerator Adapters (ACC100/ACC200/N3000)
hardware_acceleration_devices/enabling-mount-bryce-hw-accelerator-for-hosted-vram-containerized-workloads
hardware_acceleration_devices/configure-sriov-fec-operator-to-enable-hw-accelerators-for-hosted-vran-containarized-workloads.rst
hardware_acceleration_devices/set-up-pods-to-use-sriov
hardware_acceleration_devices/switch-between-static-method-hardware-accelerator-and-srminusi-5f893343ee15
****************************