From 4638ccbe70532ba745799bfc7d95d2f5bee99f6b Mon Sep 17 00:00:00 2001 From: Shikha Jhala Date: Thu, 14 Aug 2025 13:32:53 -0400 Subject: [PATCH] CNV-62384: Removed DPDK checkup content --- modules/virt-configuring-vm-project-dpdk.adoc | 7 ++-- .../virt-running-cluster-checkups.adoc | 33 +------------------ .../virt-using-dpdk-with-sriov.adoc | 1 - 3 files changed, 4 insertions(+), 37 deletions(-) diff --git a/modules/virt-configuring-vm-project-dpdk.adoc b/modules/virt-configuring-vm-project-dpdk.adoc index 4a7107ad16..27a52f29d2 100644 --- a/modules/virt-configuring-vm-project-dpdk.adoc +++ b/modules/virt-configuring-vm-project-dpdk.adoc @@ -17,7 +17,7 @@ You can configure the project to run DPDK workloads on SR-IOV hardware. + [source,terminal] ---- -$ oc create ns dpdk-checkup-ns +$ oc create ns dpdk-ns ---- . Create an `SriovNetwork` object that references the `SriovNetworkNodePolicy` object. When you create an `SriovNetwork` object, the SR-IOV Network Operator automatically creates a `NetworkAttachmentDefinition` object. @@ -42,7 +42,7 @@ spec: }], "gateway": "10.56.217.1" } - networkNamespace: dpdk-checkup-ns <1> + networkNamespace: dpdk-ns <1> resourceName: intel_nics_dpdk <2> spoofChk: "off" trust: "on" @@ -51,5 +51,4 @@ spec: <1> The namespace where the `NetworkAttachmentDefinition` object is deployed. <2> The value of the `spec.resourceName` attribute of the `SriovNetworkNodePolicy` object that was created when configuring the cluster for DPDK workloads. -. Optional: Run the virtual machine latency checkup to verify that the network is properly configured. -. Optional: Run the DPDK checkup to verify that the namespace is ready for DPDK workloads. +. Optional: Run the virtual machine latency checkup to verify that the network is properly configured. \ No newline at end of file diff --git a/virt/monitoring/virt-running-cluster-checkups.adoc b/virt/monitoring/virt-running-cluster-checkups.adoc index 19edd22cc1..e189128dd5 100644 --- a/virt/monitoring/virt-running-cluster-checkups.adoc +++ b/virt/monitoring/virt-running-cluster-checkups.adoc @@ -16,9 +16,6 @@ Before you run a latency checkup, you must first xref:../../virt/vm_networking/v ===== * Storage checkup, which verifies if the cluster storage is optimally configured for {VirtProductName}. -* DPDK checkup, which verifies that a node can run a VM with a Data Plane Development Kit (DPDK) workload with zero packet loss. -//xref:../../virt/monitoring/virt-running-cluster-checkups.adoc#virt-running-real-time-checkup_virt-running-cluster-checkups[Real-time checkup]:: -//Verifies that your {product-title} cluster can run virtualized real-time workloads. :FeatureName: The {VirtProductName} cluster checkup framework include::snippets/technology-preview.adoc[] @@ -43,25 +40,6 @@ include::modules/virt-measuring-latency-vm-secondary-network.adoc[leveloffset=+2 include::modules/virt-checking-storage-configuration.adoc[leveloffset=+2] -include::modules/virt-checking-cluster-dpdk-readiness.adoc[leveloffset=+2] - -include::modules/virt-dpdk-config-map-parameters.adoc[leveloffset=+3] - -include::modules/virt-building-vm-containerdisk-image.adoc[leveloffset=+3] - -//// -include::modules/virt-running-real-time-checkup.adoc[leveloffset=+1] - -[role="_additional-resources"] -.Additional resources -* xref:../../virt/virtual_machines/advanced_vm_management/virt-configuring-cluster-realtime-workloads.adoc#virt-configuring-cluster-realtime-workloads[Configuring a cluster for real-time workloads] - -include::modules/virt-real-time-config-map-parameters.adoc[leveloffset=+2] - -include::modules/virt-building-real-time-container-disk-image.adoc[leveloffset=+2] - -//// - ifndef::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[] [role="_additional-resources"] @@ -70,13 +48,4 @@ ifndef::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[] endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[] ifndef::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[] * xref:../../virt/vm_networking/virt-connecting-vm-to-linux-bridge.adoc#virt-connecting-vm-to-linux-bridge[Attaching a virtual machine to multiple networks] -endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[] -// Hiding pending resolution of OSDOCS-3691 -ifndef::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[] -* xref:../../networking/hardware_networks/using-dpdk-and-rdma.adoc#example-vf-use-in-dpdk-mode-intel_using-dpdk-and-rdma[Using a virtual function in DPDK mode with an Intel NIC] -* xref:../../networking/hardware_networks/using-dpdk-and-rdma.adoc#nw-example-dpdk-line-rate_using-dpdk-and-rdma[Using SR-IOV and the Node Tuning Operator to achieve a DPDK line rate] -endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[] -ifndef::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[] -* link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/composing_a_customized_rhel_system_image/installing-composer_composing-a-customized-rhel-system-image[Installing image builder] -* link:https://access.redhat.com/solutions/253273[How to register and subscribe a RHEL system to the Red Hat Customer Portal using Red Hat Subscription Manager] -endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[] +endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[] \ No newline at end of file diff --git a/virt/vm_networking/virt-using-dpdk-with-sriov.adoc b/virt/vm_networking/virt-using-dpdk-with-sriov.adoc index 740cf706f6..28545f8fd3 100644 --- a/virt/vm_networking/virt-using-dpdk-with-sriov.adoc +++ b/virt/vm_networking/virt-using-dpdk-with-sriov.adoc @@ -32,7 +32,6 @@ include::modules/virt-configuring-vm-project-dpdk.adoc[leveloffset=+1] .Additional resources * xref:../../applications/projects/working-with-projects.adoc#working-with-projects[Working with projects] * xref:../../virt/monitoring/virt-running-cluster-checkups.adoc#virt-measuring-latency-vm-secondary-network_virt-running-cluster-checkups[Virtual machine latency checkup] -* xref:../../virt/monitoring/virt-running-cluster-checkups.adoc#virt-checking-cluster-dpdk-readiness_virt-running-cluster-checkups[DPDK checkup] include::modules/virt-configuring-vm-dpdk.adoc[leveloffset=+1]