Merge pull request #59891 from orelmisan/update_dpdk_cluster_config

Virt: Update DPDK cluster configuration instructions

Author: sjhala-ccs

modules/virt-configuring-cluster-dpdk.adoc

@@ -34,12 +34,10 @@ $ oc label node <node_name> node-role.kubernetes.io/worker-dpdk=""
 apiVersion: machineconfiguration.openshift.io/v1
 kind: MachineConfigPool
 metadata:
-  name: dpdk-workers
+  name: worker-dpdk
   labels:
-    machineconfiguration.openshift.io/role: dpdk-workers
-    pools.operator.machineconfiguration.openshift.io/dpdk-workers: ""
+    machineconfiguration.openshift.io/role: worker-dpdk
 spec:
-  configuration:
   machineConfigSelector:
     matchExpressions:
       - key: machineconfiguration.openshift.io/role
@@ -63,24 +61,48 @@ metadata:
   name: profile-1
 spec:
   cpu:
-    isolated: 20,22,24,26,28,30,32,34,36,38,60,62,64,66,68,70,72,74,76,78
-    reserved: 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,21,23,25,27,29,31,33,35,37,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,61,63,65,67,69,71,73,75,77,79
+    isolated: 4-39,44-79
+    reserved: 0-3,40-43
   hugepages:
     defaultHugepagesSize: 1G
     pages:
-      - count: 32
-        size: 1G
+    - count: 32
+      node: 0
+      size: 1G
+  net:
+    userLevelNetworking: true
+  nodeSelector:
+    node-role.kubernetes.io/worker-dpdk: ""
   numa:
     topologyPolicy: single-numa-node
-  nodeSelector:
-    node-role.kubernetes.io/worker-dpdk: "" 
 ----
 +
 [NOTE]
 ====
 The compute nodes automatically restart after you apply the `MachineConfigPool` and `PerformanceProfile` manifests.
 ====
 
+. Retrieve the name of the generated `RuntimeClass` resource from the `status.runtimeClass` field of the `PerformanceProfile` object:
++
+[source,terminal]
+----
+$ oc get performanceprofiles.performance.openshift.io profile-1 -o=jsonpath='{.status.runtimeClass}{"\n"}'
+----
+
+. Set the previously obtained `RuntimeClass` name as the default container runtime class for the `virt-launcher` pods by adding the following annotation to the `HyperConverged` custom resource (CR):
++
+[source,terminal]
+----
+$ oc annotate --overwrite -n openshift-cnv hco kubevirt-hyperconverged \
+    kubevirt.kubevirt.io/jsonpatch='[{"op": "add", "path": "/spec/configuration/defaultRuntimeClass", "value": <runtimeclass_name>}]'
+----
++
+[NOTE]
+====
+Adding the annotation to the `HyperConverged` CR changes a global setting that affects all VMs that are created after the annotation is applied.
+Setting this annotation breaches support of the {VirtProductName} instance and must be used only on test clusters. For best performance, apply for a support exception.
+====
+
 . Create an `SriovNetworkNodePolicy` object with the `spec.deviceType` field set to `vfio-pci`:
 +
 .Example `SriovNetworkNodePolicy` manifest
@@ -107,17 +129,3 @@ spec:
   nodeSelector:
     feature.node.kubernetes.io/network-sriov.capable: "true"
 ----
-
-. Set the container runtime configuration for the `virt-launcher` pod by adding the following annotation to the `HyperConverged` custom resource (CR):
-+
-[source,terminal]
-----
-$ oc annotate --overwrite -n openshift-cnv hco kubevirt-hyperconverged \
-    kubevirt.kubevirt.io/jsonpatch='[{"op": "add", "path": "/spec/configuration/defaultRuntimeClass", "value": <runtimeclass-name>}]'
-----
-+
-[NOTE]
-====
-Adding the annotation to the `HyperConverged` CR changes a global setting that affects all VMs that are created after the annotation is applied.
-====
-