7.2. 推荐的集群配置来运行 vDU 应用程序

1. 确保在集群性能配置集中设置以下 additionalKernelArgs ：

   apiVersion: performance.openshift.io/v2
   kind: PerformanceProfile
   # ...
   spec:
     additionalKernelArgs:
     - "rcupdate.rcu_normal_after_boot=0"
     - "efi=runtime"
     - "vfio_pci.enable_sriov=1"
     - "vfio_pci.disable_idle_d3=1"
     - "module_blacklist=irdma"
   
     # ...

   Copy to Clipboard Toggle word wrap

2. 可选：在 hardwareTuning 字段中设置 CPU 频率：

   您可以使用硬件调优来为保留和隔离的内核 CPU 调优 CPU 频率。对于像应用程序一样的 FlexRAN，硬件厂商建议您在默认 CPU 上运行 CPU 频率。强烈建议您在设置任何频率之前，请参阅硬件厂商的准则，以获得处理器生成的最大频率设置。本例显示了为 Sapphire 快速硬件保留和隔离的 CPU 频率：

   apiVersion: performance.openshift.io/v2
   kind: PerformanceProfile
   metadata:
     name: openshift-node-performance-profile
   spec:
         cpu:
           isolated: "2-19,22-39"
           reserved: "0-1,20-21"
         hugepages:
           defaultHugepagesSize: 1G
           pages:
             - size: 1G
               count: 32
         realTimeKernel:
             enabled: true
         hardwareTuning:
             isolatedCpuFreq: 2500000
             reservedCpuFreq: 2800000

   Copy to Clipboard Toggle word wrap

3. 确保 Tuned CR 中的 performance-patch 配置集配置与相关 PerformanceProfile CR 中设置的隔离 CPU 的正确 CPU 隔离集，例如：

   apiVersion: tuned.openshift.io/v1
   kind: Tuned
   metadata:
     name: performance-patch
     namespace: openshift-cluster-node-tuning-operator
     annotations:
       ran.openshift.io/ztp-deploy-wave: "10"
   spec:
     profile:
       - name: performance-patch
         # The 'include' line must match the associated PerformanceProfile name, for example:
         # include=openshift-node-performance-${PerformanceProfile.metadata.name}
         # When using the standard (non-realtime) kernel, remove the kernel.timer_migration override from the [sysctl] section
         data: |
           [main]
           summary=Configuration changes profile inherited from performance created tuned
           include=openshift-node-performance-openshift-node-performance-profile
           [scheduler]
           group.ice-ptp=0:f:10:*:ice-ptp.*
           group.ice-gnss=0:f:10:*:ice-gnss.*
           group.ice-dplls=0:f:10:*:ice-dplls.*
           [service]
           service.stalld=start,enable
           service.chronyd=stop,disable
   # ...

   Copy to Clipboard Toggle word wrap

流程

1. 运行以下命令来获取集群版本：

   $ OCP_VERSION=$(oc get clusterversion version -o jsonpath='{.status.desired.version}{"\n"}')

   Copy to Clipboard Toggle word wrap

2. 获取发行镜像 SHA 号：

   $ DTK_IMAGE=$(oc adm release info --image-for=driver-toolkit quay.io/openshift-release-dev/ocp-release:$OCP_VERSION-x86_64)

   Copy to Clipboard Toggle word wrap

3. 运行发行镜像容器，并提取与集群当前发行版本一起打包的内核版本：

   $ podman run --rm $DTK_IMAGE rpm -qa | grep 'kernel-rt-core-' | sed 's#kernel-rt-core-##'

   Copy to Clipboard Toggle word wrap

   输出示例

   4.18.0-305.49.1.rt7.121.el8_4.x86_64

   Copy to Clipboard Toggle word wrap

   这是版本附带的默认 realtime 内核版本。

   注意

   realtime 内核由内核版本中的字符串 .rt 表示。

1. 打开到集群节点的远程 shell 连接：

   $ oc debug node/<node_name>

   Copy to Clipboard Toggle word wrap

2. 检查 realtime 内核版本：

   sh-4.4# uname -r

   Copy to Clipboard Toggle word wrap

   输出示例

   4.18.0-305.49.1.rt7.121.el8_4.x86_64

   Copy to Clipboard Toggle word wrap