Merge pull request #61688 from apinnick/cnv-reorg

CNV docs reorganization

Author: apinnick

_topic_maps/_topic_map.yml

@@ -3594,78 +3594,75 @@ Name: Virtualization
 Dir: virt
 Distros: openshift-enterprise,openshift-origin
 Topics:
-- Name: About OpenShift Virtualization
-  File: about-virt
+- Name: About
+  Dir: about_virt
+  Topics:
+  - Name: About OpenShift Virtualization
+    File: about-virt
+    Distros: openshift-enterprise
+  - Name: About OKD Virtualization
+    File: about-virt
+    Distros: openshift-origin
+  - Name: Security policies
+    File: virt-security-policies
+  - Name: Architecture
+    File: virt-architecture
+    Distros: openshift-enterprise
 - Name: Release notes
   Dir: release_notes
   Topics:
   - Name: OpenShift Virtualization release notes
-    File: placeholder-release-notes
+    File: virt-release-notes-placeholder
+    Distros: openshift-enterprise
+  # - Name: OKD Virtualization release notes
+  #   File: virt-release-notes-placeholder
+  #   Distros: openshift-origin
+- Name: Getting started
+  Dir: getting_started
+  Topics:
+  - Name: Getting started with OpenShift Virtualization
+    File: virt-getting-started
+    Distros: openshift-enterprise
+  - Name: Getting started with OKD Virtualization
+    File: virt-getting-started
+    Distros: openshift-origin
+  - Name: Using the virtctl and libguestfs CLI tools
+    File: virt-using-the-cli-tools
+  - Name: Web console overview
+    File: virt-web-console-overview
     Distros: openshift-enterprise
-# - Name: Release notes
-#   Dir: release_notes
-#   Topics:
-#   - Name: OKD release notes
-#     File: placeholder-release-notes
-#     Distros: openshift-origin
-- Name: OpenShift Virtualization architecture
-  File: virt-architecture
-  Distros: openshift-enterprise
-- Name: About OKD Virtualization
-  File: about-virt
-  Distros: openshift-origin
-- Name: Getting started with OpenShift Virtualization
-  File: virt-getting-started
-  Distros: openshift-enterprise
-- Name: Getting started with OKD Virtualization
-  File: virt-getting-started
-  Distros: openshift-origin
-- Name: Web console overview
-  File: virt-web-console-overview
-  Distros: openshift-enterprise
 - Name: Installing
   Dir: install
   Topics:
-  - Name: Preparing your cluster for OpenShift Virtualization
+  - Name: Preparing your cluster
     File: preparing-cluster-for-virt
+  - Name: Installing OpenShift Virtualization
+    File: installing-virt
     Distros: openshift-enterprise
-  - Name: Preparing your OKD cluster for OKD Virtualization
-    File: preparing-cluster-for-virt
+  - Name: Installing OKD Virtualization
+    File: installing-virt
     Distros: openshift-origin
   - Name: Specifying nodes for OpenShift Virtualization components
     File: virt-specifying-nodes-for-virtualization-components
     Distros: openshift-enterprise
   - Name: Specifying nodes for OKD Virtualization components
     File: virt-specifying-nodes-for-virtualization-components
     Distros: openshift-origin
-  - Name: Installing OpenShift Virtualization using the web console
-    File: installing-virt-web
-    Distros: openshift-enterprise
-  - Name: Installing OKD Virtualization using the web console
-    File: installing-virt-web
-    Distros: openshift-origin
-  - Name: Installing OpenShift Virtualization using the CLI
-    File: installing-virt-cli
-    Distros: openshift-enterprise
-  - Name: Installing OKD Virtualization using the CLI
-    File: installing-virt-cli
-    Distros: openshift-origin
   - Name: Uninstalling OpenShift Virtualization
     File: uninstalling-virt
     Distros: openshift-enterprise
   - Name: Uninstalling OKD Virtualization
     File: uninstalling-virt
     Distros: openshift-origin
-- Name: Updating OpenShift Virtualization
-  File: upgrading-virt
-  Distros: openshift-enterprise
-- Name: Updating OKD Virtualization
-  File: upgrading-virt
-  Distros: openshift-origin
-- Name: Security policies
-  File: virt-security-policies
-- Name: Using the virtctl and libguestfs CLI tools
-  File: virt-using-the-cli-tools
+- Name: Updating
+  Dir: updating
+  Topics:
+  - Name: Updating OpenShift Virtualization
+    File: upgrading-virt
+    Distros: openshift-enterprise
+  - Name: Updating OKD Virtualization
+    File: upgrading-virt
+    Distros: openshift-origin
 - Name: Virtual machines
   Dir: virtual_machines
   Topics:

applications/creating_applications/odc-creating-applications-using-developer-perspective.adoc

@@ -50,7 +50,7 @@ The Managed services option is also available if the RHOAS Operator is installed
 * *Re-ordering of resources*: Use these resources to re-order pinned resources added to your navigation pane. The drag-and-drop icon is displayed on the left side of the pinned resource when you hover over it in the navigation pane. The dragged resource can be dropped only in the section where it resides.
 
 ifdef::openshift-enterprise,openshift-webscale[]
-Note that certain options, such as *Pipelines*, *Event Source*, and *Import Virtual Machines*, are displayed only when the xref:../../cicd/pipelines/installing-pipelines.adoc#op-installing-pipelines-operator-in-web-console_installing-pipelines[OpenShift Pipelines Operator], link:https://docs.openshift.com/serverless/1.28/install/install-serverless-operator.html#serverless-install-web-console_install-serverless-operator[{ServerlessOperatorName}], and xref:../../virt/install/installing-virt-web.adoc#virt-subscribing-to-the-catalog_installing-virt-web[OpenShift Virtualization Operator] are installed, respectively.
+Note that certain options, such as *Pipelines*, *Event Source*, and *Import Virtual Machines*, are displayed only when the xref:../../cicd/pipelines/installing-pipelines.adoc#op-installing-pipelines-operator-in-web-console_installing-pipelines[OpenShift Pipelines Operator], link:https://docs.openshift.com/serverless/1.28/install/install-serverless-operator.html#serverless-install-web-console_install-serverless-operator[{ServerlessOperatorName}], and xref:../../virt/install/installing-virt.adoc#virt-subscribing-cli_installing-virt[OpenShift Virtualization Operator] are installed, respectively.
 endif::[]
 
 [id="prerequisites_odc-creating-applications-using-developer-perspective"]

installing/installing_bare_metal/preparing-to-install-on-bare-metal.adoc

@@ -17,8 +17,8 @@ include::modules/virt-planning-bare-metal-cluster-for-ocp-virt.adoc[leveloffset=
 [role="_additional-resources"]
 .Additional resources
 
+* xref:../../virt/getting_started/virt-getting-started.adoc#virt-getting-started[Getting started with {VirtProductName}]
 * xref:../../virt/install/preparing-cluster-for-virt.adoc#preparing-cluster-for-virt[Preparing your cluster for {VirtProductName}]
-* xref:../../virt/virt-getting-started.adoc#virt-getting-started[Getting started with {VirtProductName}]
 * xref:../../networking/hardware_networks/about-sriov.adoc#about-sriov[About Single Root I/O Virtualization (SR-IOV) hardware networks]
 * xref:../../virt/virtual_machines/vm_networking/virt-attaching-vm-to-sriov-network.adoc#virt-attaching-vm-to-sriov-network[Connecting a virtual machine to an SR-IOV network]
 

installing/installing_sno/install-sno-installing-sno.adoc

@@ -20,7 +20,7 @@ include::modules/install-sno-generating-the-discovery-iso-with-the-assisted-inst
 .Additional resources
 
 * xref:../../storage/persistent_storage/persistent_storage_local/persistent-storage-using-lvms.adoc#persistent-storage-using-lvms_logical-volume-manager-storage[Persistent storage using logical volume manager storage]
-* xref:../../virt/about-virt.adoc#virt-what-you-can-do-with-virt_about-virt[What you can do with OpenShift Virtualization]
+* xref:../../virt/about_virt/about-virt.adoc#virt-what-you-can-do-with-virt_about-virt[What you can do with OpenShift Virtualization]
 
 include::modules/install-sno-installing-with-the-assisted-installer.adoc[leveloffset=+2]
 

modules/olm-approving-pending-upgrade.adoc

@@ -1,7 +1,7 @@
 // Module included in the following assemblies:
 //
 // * operators/admin/olm-upgrading-operators.adoc
-// * virt/upgrading-virt.adoc
+// * virt/updating/upgrading-virt.adoc
 
 :_content-type: PROCEDURE
 [id="olm-approving-pending-upgrade_{context}"]

modules/virt-about-eus-updates.adoc

@@ -1,14 +1,14 @@
 // Module included in the following assemblies:
 //
-// * virt/upgrading-virt.adoc
+// * virt/updating/upgrading-virt.adoc
 
 :_content-type: CONCEPT
 [id="virt-about-eus-updates_{context}"]
 = About EUS-to-EUS updates
 
-Every even-numbered minor version of {product-title}, including 4.10 and 4.12, is an Extended Update Support (EUS) version. However, because Kubernetes design mandates serial minor version updates, you cannot directly update from one EUS version to the next. 
+Every even-numbered minor version of {product-title}, including 4.10 and 4.12, is an Extended Update Support (EUS) version. However, because Kubernetes design mandates serial minor version updates, you cannot directly update from one EUS version to the next.
 
-After you update from the source EUS version to the next odd-numbered minor version, you must sequentially update {VirtProductName} to all z-stream releases of that minor version that are on your update path. When you have upgraded to the latest applicable z-stream version, you can then update {product-title} to the target EUS minor version. 
+After you update from the source EUS version to the next odd-numbered minor version, you must sequentially update {VirtProductName} to all z-stream releases of that minor version that are on your update path. When you have upgraded to the latest applicable z-stream version, you can then update {product-title} to the target EUS minor version.
 
 When the {product-title} update succeeds, the corresponding update for {VirtProductName} becomes available. You can now update {VirtProductName} to the target EUS version.
 
@@ -17,7 +17,7 @@ When the {product-title} update succeeds, the corresponding update for {VirtProd
 
 Before beginning an EUS-to-EUS update, you must:
 
-* Pause worker nodes' machine config pools before you start an EUS-to-EUS update so that the workers are not rebooted twice. 
+* Pause worker nodes' machine config pools before you start an EUS-to-EUS update so that the workers are not rebooted twice.
 
 * Disable automatic workload updates before you begin the update process. This is to prevent {VirtProductName} from migrating or evicting your virtual machines (VMs) until you update to your target EUS version.
 

modules/virt-about-libguestfs-tools-virtctl-guestfs.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * virt/virt-using-the-cli-tools.adoc
+// * virt/getting_started/virt-using-the-cli-tools.adoc
 
 :_content-type: REFERENCE
 [id="virt-about-libguestfs-tools-virtctl-guestfs_{context}"]

modules/virt-about-storage-volumes-for-vm-disks.adoc

@@ -1,27 +1,27 @@
 // Module included in the following assemblies:
 //
-// * virt/about-virt.adoc
+// * virt/about/about-virt.adoc
+// * virt/install/preparing-cluster-for-virt.adoc
 
 :_content-type: CONCEPT
 [id="virt-about-storage-volumes-for-vm-disks_{context}"]
-= About storage volumes for virtual machine disks
+= About volume and access modes for virtual machine disks
 
-If you use the storage API with known storage providers, volume and access modes are selected automatically. However, if you use a storage class that does not have a storage profile, you must select the volume and access mode.
+If you use the storage API with known storage providers, the volume and access modes are selected automatically. However, if you use a storage class that does not have a storage profile, you must configure the volume and access mode.
 
-For best results, use `accessMode: ReadWriteMany` and `volumeMode: Block`. This is important for the following reasons:
+For best results, use the `ReadWriteMany` (RWX) access mode and the `Block` volume mode. This is important for the following reasons:
 
-* The ReadWriteMany (RWX) access mode is required for live migration.
+* `ReadWriteMany` (RWX) access mode is required for live migration.
 
-* The `Block` volume mode performs significantly better in comparison to the `Filesystem` volume mode. This is because the `Filesystem` volume mode uses more storage layers, including a file system layer and a disk image file. These layers are not necessary for VM disk storage.
+* The `Block` volume mode performs significantly better than the `Filesystem` volume mode. This is because the `Filesystem` volume mode uses more storage layers, including a file system layer and a disk image file. These layers are not necessary for VM disk storage.
 +
 For example, if you use {rh-storage-first}, Ceph RBD volumes are preferable to CephFS volumes.
-+
+
 [IMPORTANT]
 ====
-You cannot live migrate virtual machines that use:
-
-* A storage volume with ReadWriteOnce (RWO) access mode
+You cannot live migrate virtual machines with the following configurations:
 
+* Storage volume with `ReadWriteOnce` (RWO) access mode
 * Passthrough features such as GPUs
 
 Do not set the `evictionStrategy` field to `LiveMigrate` for these virtual machines.

modules/virt-about-upgrading-virt.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * virt/upgrading-virt.adoc
+// * virt/updating/upgrading-virt.adoc
 
 :_content-type: CONCEPT
 [id="virt-about-upgrading-virt_{context}"]

modules/virt-about-workload-updates.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * virt/upgrading-virt.adoc
+// * virt/updating/upgrading-virt.adoc
 
 :_content-type: CONCEPT
 [id="virt-about-workload-updates_{context}"]