Merge pull request #106316 from rheslop/main-CNV-68758

CNV#68758 Procedural corrections

Author: ousleyp

modules/virt-about-changing-removing-mediated-devices.adoc

@@ -7,9 +7,7 @@
 = About using virtual GPUs with {VirtProductName}
 
 [role="_abstract"]
-Some graphics processing unit (GPU) cards support the creation of virtual GPUs (vGPUs). {VirtProductName} can automatically create vGPUs and other mediated devices if an administrator provides configuration details in the `HyperConverged` custom resource (CR).
-
-This automation is especially useful for large clusters.
+You can create vGPUs for your VMs using supported GPU cards. You can use the NVIDIA GPU Operator to manage the lifecycle and creation of these vGPUs on the cluster nodes. You must add these devices to the `HyperConverged` custom resource (CR) so that {VirtProductName} can discover and make them available to virtual machines.
 
 [NOTE]
 ====

modules/virt-about-using-virtual-gpus.adoc

@@ -91,8 +91,6 @@ $ oc edit hyperconverged kubevirt-hyperconverged -n {CNVNamespace}
 
 . Create and expose the mediated devices by updating the configuration:
 
-.. Create mediated devices by adding them to the `spec.mediatedDevicesConfiguration` stanza.
-
 .. Expose the mediated devices to the cluster by adding the `mdevNameSelector` and `resourceName` values to the `spec.permittedHostDevices.mediatedDevices` stanza. The `resourceName` value is based on the `mdevNameSelector` value, but you use underscores instead of spaces.
 +
 Example `HyperConverged` CR:
@@ -105,14 +103,6 @@ metadata:
   name: kubevirt-hyperconverged
   namespace: {CNVNamespace}
 spec:
-  mediatedDevicesConfiguration:
-    mediatedDeviceTypes:
-    - nvidia-745
-    nodeMediatedDeviceTypes:
-    - mediatedDeviceTypes:
-      - nvidia-746
-      nodeSelector:
-        kubernetes.io/hostname: node-11.redhat.com
   permittedHostDevices:
     mediatedDevices:
     - mdevNameSelector: NVIDIA A2-2Q
@@ -126,18 +116,12 @@ spec:
 +
 where:
 
-`mediatedDeviceTypes`:: Specifies global settings for the cluster and is required.
-
-`nodeMediatedDeviceTypes`:: Specifies global configuration overrides for a specific node or group of nodes and is optional. Must be used with the global `mediatedDeviceTypes` configuration.
-
-`mediatedDeviceTypes`:: Specifies an override to the global `mediatedDeviceTypes` configuration for the specified nodes. Required if you use `nodeMediatedDeviceTypes`.
-
-`nodeSelector`:: Specifies the node selector and must include a `key:value` pair. Required if you use `nodeMediatedDeviceTypes`.
-
 `mdevNameSelector`:: Specifies the mediated devices that map to this value on the host.
 
 `resourceName`:: Specifies the matching resource name that is allocated on the node.
 
+`externalResourceProvider`:: Specifies that the device is handled by an external provider, such as the NVIDIA GPU Operator.
+
 . Save your changes and exit the editor.
 
 .Verification

modules/virt-creating-and-exposing-mediated-devices.adoc

@@ -7,7 +7,7 @@
 = Removing mediated devices from the cluster
 
 [role="_abstract"]
-To remove a mediated device from the cluster, delete the information for that device from the `HyperConverged` custom resource (CR).
+As a cluster administrator you can remove mediated devices from the cluster so that you can reallocate GPU hardware. To remove a mediated device from the cluster, delete the information for that device from the `HyperConverged` CR.
 
 .Prerequisites
 
@@ -22,7 +22,7 @@ To remove a mediated device from the cluster, delete the information for that de
 $ oc edit hyperconverged kubevirt-hyperconverged -n {CNVNamespace}
 ----
 
-. Remove the device information from the `spec.mediatedDevicesConfiguration` and `spec.permittedHostDevices` stanzas of the `HyperConverged` CR. Removing both entries ensures that you can later create a new mediated device type on the same node. For example:
+. Remove the device information from the `spec.permittedHostDevices` stanza of the `HyperConverged` CR. For example:
 +
 [source,yaml,subs="attributes+"]
 ----
@@ -32,15 +32,12 @@ metadata:
   name: kubevirt-hyperconverged
   namespace: {CNVNamespace}
 spec:
-  mediatedDevicesConfiguration:
-    mediatedDeviceTypes:
-      - nvidia-231
   permittedHostDevices:
     mediatedDevices:
     - mdevNameSelector: GRID T4-2Q
       resourceName: nvidia.com/GRID_T4-2Q
+      externalResourceProvider: true
 ----
-** To remove the `nvidia-231` device type, delete it from the `mediatedDeviceTypes` array.
 ** To remove the `GRID T4-2Q` device, delete the `mdevNameSelector` field and its corresponding `resourceName` field.
 
 . Save your changes and exit the editor.

modules/virt-removing-mediated-device-from-cluster-cli.adoc

@@ -7,7 +7,7 @@ include::_attributes/common-attributes.adoc[]
 toc::[]
 
 [role="_abstract"]
-If you have graphics processing unit (GPU) cards, {VirtProductName} can automatically create virtual GPUs (vGPUs) that you can assign to virtual machines (VMs).
+Use the NVIDIA GPU operator to create virtual GPUs (vGPUs) and assign them to virtual machines (VMs) in {VirtProductName}.
 
 include::modules/virt-about-using-virtual-gpus.adoc[leveloffset=+1]
 
@@ -36,17 +36,13 @@ include::modules/virt-label-nodes-with-mig-backed-profile.adoc[leveloffset=+2]
 .Additional resources
 * xref:../../../virt/managing_vms/advanced_vm_management/virt-configuring-pci-passthrough.adoc#virt-configuring-pci-passthrough[Configuring PCI passthrough]
 
-include::modules/virt-how-virtual-gpus-assigned-nodes.adoc[leveloffset=+1]
-
 [id="managing-mediated-devices_{context}"]
 == Managing mediated devices
 
 Before you can assign mediated devices to virtual machines, you must create the devices and expose them to the cluster. You can also reconfigure and remove mediated devices.
 
 include::modules/virt-creating-and-exposing-mediated-devices.adoc[leveloffset=+2]
 
-include::modules/virt-about-changing-removing-mediated-devices.adoc[leveloffset=+2]
-
 include::modules/virt-removing-mediated-device-from-cluster-cli.adoc[leveloffset=+2]
 
 [id="using-mediated-devices_{context}"]