Merge pull request #64685 from apinnick/new-cnv-storage

CNV storage updates

Author: apinnick

_topic_maps/_topic_map.yml

@@ -2755,27 +2755,27 @@ Topics:
     - Name: Backing up applications with Restic
       File: oadp-backing-up-applications-restic-doc
     - Name: Creating backup hooks
-      File: oadp-creating-backup-hooks-doc  
+      File: oadp-creating-backup-hooks-doc
     - Name: Scheduling backups using Schedule CR
       File: oadp-scheduling-backups-doc
     - Name: Deleting backups
-      File: oadp-deleting-backups-doc 
+      File: oadp-deleting-backups-doc
   - Name: OADP restoring
     Dir: backing_up_and_restoring
-    Topics:      
+    Topics:
     - Name: Restoring applications
-      File: restoring-applications  
-  - Name: OADP Data Mover     
+      File: restoring-applications
+  - Name: OADP Data Mover
     Dir: installing
     Topics:
     - Name: Introduction to OADP Data Mover
       File: data-mover-intro
     - Name: Using Data Mover for CSI snapshots
-      File: oadp-using-data-mover-for-csi-snapshots-doc  
+      File: oadp-using-data-mover-for-csi-snapshots-doc
     - Name: Using OADP 1.2 Data Mover with Ceph storage
       File: oadp-12-data-mover-ceph-doc
     - Name: Cleaning up after a backup using OADP 1.1 Data Mover
-      File: oadp-cleaning-up-after-data-mover-1-1-backup-doc         
+      File: oadp-cleaning-up-after-data-mover-1-1-backup-doc
   - Name: Troubleshooting
     File: troubleshooting
   - Name: OADP API
@@ -3688,9 +3688,23 @@ Topics:
 - Name: Virtual machines
   Dir: virtual_machines
   Topics:
-###VIRTUAL MACHINE CHESS SALAD (silly name to highlight that the commented out assemblies need to be checked against merged filenams)
-  - Name: Creating virtual machines
-    File: virt-creating-vms
+  - Name: Creating VMs
+    Dir: creating_vms
+    Topics:
+    - Name: Creating VMs from Red Hat images
+      File: virt-creating-vms-from-rh-images
+    - Name: Creating VMs from custom images
+      File: virt-creating-vms-from-custom-images
+    - Name: Creating VMs by using container disks
+      File: virt-creating-vms-from-container-disks
+    - Name: Creating VMs by importing images from web pages
+      File: virt-creating-vms-from-web-images
+    - Name: Creating VMs by uploading images
+      File: virt-creating-vms-uploading-images
+    - Name: Creating VMs by cloning PVCs
+      File: virt-creating-vms-by-cloning-pvcs
+    - Name: Installing the QEMU guest agent and VirtIO drivers
+      File: virt-installing-qemu-guest-agent
   - Name: Connecting to VM consoles
     File: virt-accessing-vm-consoles
   - Name: Configuring SSH access to VMs
@@ -3707,20 +3721,10 @@ Topics:
     File: virt-manage-vmis
   - Name: Controlling virtual machine states
     File: virt-controlling-vm-states
-  - Name: Automating Windows installation with sysprep
-    File: virt-automating-windows-sysprep
-  - Name: Installing the QEMU guest agent and VirtIO drivers
-    File: virt-installing-qemu-guest-agent
-  - Name: Viewing the QEMU guest agent information for virtual machines
-    File: virt-viewing-qemu-guest-agent-web
   - Name: Using virtual Trusted Platform Module devices
     File: virt-using-vtpm-devices
   - Name: Managing virtual machines with OpenShift Pipelines
     File: virt-managing-vms-openshift-pipelines
-  - Name: Managing automatic boot source updates
-    File: virt-automatic-bootsource-updates
-  - Name: Creating custom boot sources
-    File: virt-creating-and-using-boot-sources
   - Name: Advanced virtual machine management
     Dir: advanced_vm_management
     Topics:
@@ -3755,64 +3759,14 @@ Topics:
       File: virt-high-availability-for-vms
     - Name: Control plane tuning
       File: virt-vm-control-plane-tuning
-# Importing virtual machines
-  - Name: Importing virtual machines
-    Dir: importing_vms
-    Topics:
-    - Name: TLS certificates for data volume imports
-      File: virt-tls-certificates-for-dv-imports
-    - Name: Importing virtual machine images with data volumes
-      File: virt-importing-virtual-machine-images-datavolumes
-# Cloning virtual machines
-  - Name: Cloning virtual machines
-    Dir: cloning_vms
-    Topics:
-    - Name: Enabling user permissions to clone data volumes across namespaces
-      File: virt-enabling-user-permissions-to-clone-datavolumes
-    - Name: Cloning a virtual machine disk into a new data volume
-      File: virt-cloning-vm-disk-into-new-datavolume
-    - Name: Cloning a virtual machine by using a data volume template
-      File: virt-cloning-vm-using-datavolumetemplate
-    - Name: Cloning a virtual machine disk into a new block storage persistent volume claim
-      File: virt-cloning-vm-disk-to-new-block-storage-pvc
 #A BETTER NAME THAN 'STORAGE 4 U'
-  - Name: Virtual machine disks
+  - Name: VM disks
     Dir: virtual_disks
     Topics:
-    - Name: Configuring local storage for virtual machines
-      File: virt-configuring-local-storage-for-vms
-    - Name: Creating data volumes
-      File: virt-creating-data-volumes
-    - Name: Reserving PVC space for file system overhead
-      File: virt-reserving-pvc-space-fs-overhead
-    - Name: Configuring CDI to work with namespaces that have a compute resource quota
-      File: virt-configuring-cdi-for-namespace-resourcequota
-    - Name: Managing data volume annotations
-      File: virt-managing-data-volume-annotations
-    - Name: Using preallocation for data volumes
-      File: virt-using-preallocation-for-datavolumes
-    - Name: Uploading local disk images by using the web console
-      File: virt-uploading-local-disk-images-web
-    - Name: Uploading local disk images by using the virtctl tool
-      File: virt-uploading-local-disk-images-virtctl
-    - Name: Uploading a local disk image to a block storage persistent volume claim
-      File: virt-uploading-local-disk-images-block
-    - Name: Managing virtual machine snapshots
-      File: virt-managing-vm-snapshots
-    - Name: Expanding virtual storage by adding blank disk images
-      File: virt-expanding-virtual-storage-with-blank-disk-images
-    - Name: Cloning a data volume using smart-cloning
-      File: virt-cloning-a-datavolume-using-smart-cloning
-    - Name: Hot plugging virtual disks
+    - Name: Hot-plugging VM disks
       File: virt-hot-plugging-virtual-disks
-    - Name: Using container disks with virtual machines
-      File: virt-using-container-disks-with-vms
-    - Name: Preparing CDI scratch space
-      File: virt-preparing-cdi-scratch-space
-    - Name: Re-using statically provisioned persistent volumes
-      File: virt-reusing-statically-provisioned-persistent-volumes
-    - Name: Expanding a virtual machine disk
-      File: virt-expanding-vm-disk
+    - Name: Expanding VM disks
+      File: virt-expanding-vm-disks
 - Name: Networking
   Dir: vm_networking
   Topics:
@@ -3838,6 +3792,29 @@ Topics:
     File: virt-accessing-vm-secondary-network-fqdn
   - Name: Managing MAC address pools for network interfaces
     File: virt-using-mac-address-pool-for-vms
+- Name: Storage
+  Dir: storage
+  Topics:
+  - Name: Storage configuration overview
+    File: virt-storage-config-overview
+  - Name: Configuring storage profiles
+    File: virt-configuring-storage-profile
+  - Name: Managing automatic boot source updates
+    File: virt-automatic-bootsource-updates
+  - Name: Reserving PVC space for file system overhead
+    File: virt-reserving-pvc-space-fs-overhead
+  - Name: Configuring local storage by using HPP
+    File: virt-configuring-local-storage-with-hpp
+  - Name: Enabling user permissions to clone data volumes across namespaces
+    File: virt-enabling-user-permissions-to-clone-datavolumes
+  - Name: Configuring CDI to override CPU and memory quotas
+    File: virt-configuring-cdi-for-namespace-resourcequota
+  - Name: Preparing CDI scratch space
+    File: virt-preparing-cdi-scratch-space
+  - Name: Using preallocation for data volumes
+    File: virt-using-preallocation-for-datavolumes
+  - Name: Managing data volume annotations
+    File: virt-managing-data-volume-annotations
 # Virtual machine live migration
 - Name: Live migration
   Dir: live_migration
@@ -3894,6 +3871,8 @@ Topics:
 - Name: Backup and restore
   Dir: backup_restore
   Topics:
+  - Name: Backup and restore by using VM snapshots
+    File: virt-backup-restore-snapshots
   - Name: Installing and configuring OADP
     File: virt-installing-configuring-oadp
   - Name: Backing up and restoring virtual machines

modules/virt-creating-data-volumes-using-storage-api.adoc renamed to _unused_topics/virt-creating-data-volumes-using-storage-api.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * virt/virtual_machines/virtual_disks/virt-creating-data-volumes.adoc
+// * virt/storage/virt-creating-data-volumes.adoc
 
 :_content-type: PROCEDURE
 [id="virt-creating-data-volumes-using-storage-api_{context}"]
@@ -11,9 +11,9 @@ When you create a data volume by using the storage API, the Containerized Data I
 For example:
 
 * When using Ceph RBD, `accessModes` is automatically set to `ReadWriteMany`, which enables live migration. `volumeMode` is set to `Block` to maximize performance.
-* When you are using `volumeMode: Filesystem`, more space will automatically be requested by the CDI, if required to accommodate file system overhead.
+* When you are using `volumeMode: Filesystem`, more space will automatically be requested by CDI, if required to accommodate file system overhead.
 
-In the following YAML, using the storage API requests a data volume with two gigabytes of usable space. The user does not need to know the `volumeMode` in order to correctly estimate the required persistent volume claim (PVC) size. The CDI chooses the optimal combination of `accessModes` and `volumeMode` attributes automatically.  These optimal values are based on the type of storage or the defaults that you define in your storage profile. If you want to provide custom values, they override the system-calculated values.
+In the following YAML, using the storage API requests a data volume with two gigabytes of usable space. The user does not need to know the `volumeMode` in order to correctly estimate the required persistent volume claim (PVC) size. CDI chooses the optimal combination of `accessModes` and `volumeMode` attributes automatically.  These optimal values are based on the type of storage or the defaults that you define in your storage profile. If you want to provide custom values, they override the system-calculated values.
 
 .Procedure
 

modules/virt-about-cdi-operator.adoc

@@ -4,9 +4,9 @@
 
 :_content-type: CONCEPT
 [id="virt-about-cdi-operator_{context}"]
-= About the the Containerized Data Importer (CDI) Operator
+= About the Containerized Data Importer (CDI) Operator
 
-The CDI Operator, `cdi-operator`, manages the CDI and its related resources, which imports a virtual machine (VM) image into a persistent volume claim (PVC) by using a data volume.
+The CDI Operator, `cdi-operator`, manages CDI and its related resources, which imports a virtual machine (VM) image into a persistent volume claim (PVC) by using a data volume.
 
 image::cnv_components_cdi-operator.png[cdi-operator components]
 

modules/virt-about-container-disks.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * virt/virtual_machines/virtual_disks/virt-configuring-cdi-for-namespace-resourcequota.adoc
+// * virt/storage/virt-configuring-cdi-for-namespace-resourcequota.adoc
 
 :_content-type: CONCEPT
 [id="virt-about-cpu-and-memory-quota-namespace_{context}"]

modules/virt-about-cpu-and-memory-quota-namespace.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * virt/virtual_machines/virtual_disks/virt-configuring-local-storage-for-vms.adoc
+// * virt/storage/virt-configuring-local-storage-with-hpp.adoc
 
 :_content-type: CONCEPT
 [id="virt-about-creating-storage-classes_{context}"]

modules/virt-about-creating-storage-classes.adoc

@@ -1,17 +1,8 @@
 // Module included in the following assemblies:
 //
-// * virt/virtual_machines/virtual_disks/virt-creating-data-volumes.adoc
-// * virt/virtual_machines/virtual_disks/virt-cloning-a-datavolume-using-smart-cloning.adoc
 // * virt/virtual_machines/virtual_disks/virt-expanding-virtual-storage-with-blank-disk-images.adoc
-// * virt/virtual_machines/virtual_disks/virt-uploading-local-disk-images-block.adoc
-// * virt/virtual_machines/virtual_disks/virt-preparing-cdi-scratch-space.adoc
-// * virt/virtual_machines/cloning_vms/virt-cloning-vm-disk-into-new-datavolume.adoc
-// * virt/virtual_machines/cloning_vms/virt-cloning-vm-using-datavolumetemplate.adoc
-// * virt/virtual_machines/cloning_vms/virt-enabling-user-permissions-to-clone-datavolumes.adoc
-// * virt/virtual_machines/cloning_vms/virt-cloning-vm-disk-to-new-block-storage-pvc.adoc
-// * virt/virtual_machines/importing_vms/virt-importing-virtual-machine-images-datavolumes.adoc
-
-
+// * virt/storage/virt-preparing-cdi-scratch-space.adoc
+// * virt/storage/virt-enabling-user-permissions-to-clone-datavolumes.adoc
 
 :_content-type: CONCEPT
 [id="virt-about-datavolumes_{context}"]

modules/virt-about-datavolumes.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * virt/virtual_machines/virtual_disks/virt-using-preallocation-for-datavolumes.adoc
+// * virt/storage/virt-using-preallocation-for-datavolumes.adoc
 
 :_content-type: CONCEPT
 [id="virt-about-preallocation_{context}"]
@@ -11,7 +11,7 @@ The Containerized Data Importer (CDI) can use the QEMU preallocate mode for data
 If preallocation is enabled, CDI uses the better preallocation method depending on the underlying file system and device type:
 
 `fallocate`::
-If the file system supports it, CDI uses the operating system's `fallocate` call to preallocate space by using the `posix_fallocate` function, which allocates blocks and marks them as uninitialized. 
+If the file system supports it, CDI uses the operating system's `fallocate` call to preallocate space by using the `posix_fallocate` function, which allocates blocks and marks them as uninitialized.
 
 `full`::
 If `fallocate` mode cannot be used, `full` mode allocates space for the image by writing data to the underlying storage. Depending on the storage location, all the empty allocated space might be zeroed.

modules/virt-about-hot-plugging-virtual-disks.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * virt/virtual_machines/virtual_disks/virt-preparing-cdi-scratch-space.adoc
+// * virt/storage/virt-preparing-cdi-scratch-space.adoc
 
 :_content-type: CONCEPT
 [id="virt-about-scratch-space_{context}"]