Merge pull request #83516 from kquinn1204/OCPBUGS-43101

OCPBUGS 43101: Configure how to set SR-IOV in systemd mode relevant for configuring hardware offloading

Author: jab-rh

modules/nw-sriov-hwol-configuring-machine-config-pool.adoc

@@ -6,12 +6,11 @@
 [id="configuring-machine-config-pool_{context}"]
 = Configuring a machine config pool for hardware offloading
 
-To enable hardware offloading, you must first create a dedicated machine config pool and configure it to work with the SR-IOV Network Operator.
+To enable hardware offloading, you now create a dedicated machine config pool and configure it to work with the SR-IOV Network Operator.
 
 .Prerequisites
 
-* You installed the OpenShift CLI (`oc`).
-* You have access to the cluster as a user with the `cluster-admin` role.
+. SR-IOV Network Operator installed and set into `systemd` mode.
 
 .Procedure
 

modules/nw-sriov-hwol-configuring-systemd-mode.adoc

@@ -0,0 +1,44 @@
+// Module included in the following assemblies:
+//
+// * networking/hardware_networks/configuring-hardware-offloading.adoc
+
+:_mod-docs-content-type: PROCEDURE
+[id="nw-sriov-hwol-configuring-systemd-mode_{context}"]
+= Setting the SR-IOV Network Operator into systemd mode
+
+To support hardware offloading, you must first set the SR-IOV Network Operator into `systemd` mode.
+
+.Prerequisites
+
+* You installed the OpenShift CLI (`oc`).
+* You have access to the cluster as a user that has the `cluster-admin` role.
+
+.Procedure
+
+. Create a `SriovOperatorConfig` custom resource (CR) to deploy all the SR-IOV Operator components:
+
+.. Create a file named `sriovOperatorConfig.yaml` that contains the following YAML:
++
+[source,yaml]
+----
+apiVersion: sriovnetwork.openshift.io/v1
+kind: SriovOperatorConfig
+metadata:
+  name: default <1>
+  namespace: openshift-sriov-network-operator
+spec:
+  enableInjector: true
+  enableOperatorWebhook: true
+  configurationMode: "systemd" <2>
+  logLevel: 2
+----
++
+<1> The only valid name for the `SriovOperatorConfig` resource is `default` and it must be in the namespace where the Operator is deployed.
+<2> Setting the SR-IOV Network Operator into `systemd` mode is only relevant for Open vSwitch hardware offloading. 
+
+.. Create the resource by running the following command:
++
+[source,terminal]
+----
+$ oc apply -f sriovOperatorConfig.yaml
+----

modules/proc-switching-bf2-nic.adoc

@@ -93,3 +93,5 @@ spec:
 <1> Optional: The PCI address of a specific card can optionally be specified, for example `ExecStart=/bin/bash -c '/etc/default/switch_in_sriov_config_daemon.sh nic 0000:5e:00.0 || echo done'`. By default, the first device is selected. If there is more than one device, you must specify which PCI address to be used. The PCI address must be the same on all nodes that are switching Bluefield-2 from DPU mode to NIC mode.
 
 . Wait for the worker nodes to restart. After restarting, the Bluefield-2 network device on the worker nodes is switched into NIC mode.
+
+. Optional: You might need to restart the host hardware because most recent Bluefield-2 firmware releases require a hardware restart to switch into NIC mode. 

networking/hardware_networks/configuring-hardware-offloading.adoc

@@ -24,6 +24,9 @@ include::modules/nw-sriov-hwol-supported-devices.adoc[leveloffset=+1]
 * Your cluster uses the xref:../../networking/ovn_kubernetes_network_provider/about-ovn-kubernetes.adoc#about-ovn-kubernetes[OVN-Kubernetes network plugin].
 * In your xref:../../networking/cluster-network-operator.adoc#gatewayConfig-object_cluster-network-operator[OVN-Kubernetes network plugin configuration], the `gatewayConfig.routingViaHost` field is set to `false`.
 
+//Configure a machine config pool for hardware offloading
+include::modules/nw-sriov-hwol-configuring-systemd-mode.adoc[leveloffset=+1]
+
 //Configure a machine config pool for hardware offloading
 include::modules/nw-sriov-hwol-configuring-machine-config-pool.adoc[leveloffset=+1]