Adds UDN and VNV live migration modules to new repo structure (#784)

RichardHoch · web-flow · commit c48a431951f7 · 2025-10-30T18:18:12.000Z
Signed-off-by: Richard Hoch &lt;rhoch@redhat.com&gt;
diff --git a/documentation/doc-Migrating_your_virtual_machines/assemblies/assembly_advanced-migration-options.adoc b/documentation/doc-Migrating_your_virtual_machines/assemblies/assembly_advanced-migration-options.adoc
@@ -40,7 +40,7 @@ include::../modules/adding-hook-using-ui.adoc[leveloffset=+2]
 
 include::../modules/adding-hook-using-cli.adoc[leveloffset=+2]
 
-
+include::../modules/about-udn.adoc[leveloffset=+2]
 
 ifdef::parent-context[:context: {parent-context}]
 ifndef::parent-context[:!context:]
diff --git a/documentation/doc-Planning_your_migration/assemblies/assembly_live-migration.adoc b/documentation/doc-Planning_your_migration/assemblies/assembly_live-migration.adoc
@@ -0,0 +1,25 @@
+:_mod-docs-content-type: ASSEMBLY
+
+[id="assembly_live-migration_{context}"]
+= Live migration in {project-short} 
+
+//:context: cold-warm-migration
+
+[role="_abstract"]
+You can use _live migration_ to migrate virtual machines (VMs) between {virt} clusters, or between namespaces on the same {virt} cluster, with extremely limited downtime.
+
+Live migration is supported by {project-first} version 2.10.0 and later. It requires {virt} 4.20 or later on both your source and target clusters. 
+
+Live migration makes it easier for you to perform Day 2 tasks, such as seamless maintenance and workload balancing after you have migrated your VMs to {virt}.
+
+include::../modules/benefits-live-migration.adoc[leveloffset=+1]
+
+include::../modules/live-migration-mtv-cnv.adoc[leveloffset=+1]
+
+include::../modules/live-migration-limitations.adoc[leveloffset=+1]
+
+include::../modules/live-migration-workflow.adoc[leveloffset=+1]
+
+
+ifdef::parent-context[:context: {parent-context}]
+ifndef::parent-context[:!context:]
diff --git a/documentation/doc-Planning_your_migration/assemblies/assembly_planning-migration-cnv.adoc b/documentation/doc-Planning_your_migration/assemblies/assembly_planning-migration-cnv.adoc
@@ -44,6 +44,8 @@ include::../modules/selecting-migration-network-for-virt-provider.adoc[leveloffs
 
 include::../modules/creating-plan-wizard-cnv.adoc[leveloffset=+1]
 
+include::../modules/creating-plan-wizard-cnv-live.adoc[leveloffset=+2]
+
 :!cnv:
 
 
diff --git a/documentation/doc-Planning_your_migration/assemblies/assembly_prerequisites-for-migration.adoc b/documentation/doc-Planning_your_migration/assemblies/assembly_prerequisites-for-migration.adoc
@@ -68,6 +68,8 @@ include::../modules/ova-prerequisites.adoc[leveloffset=+1]
 
 include::../modules/cnv-prerequisites.adoc[leveloffset=+1]
 
+include::../modules/cnv-cnv-live-prerequisites.adoc[leveloffset=+2]
+
 include::../modules/compatibility-guidelines.adoc[leveloffset=+1]
 
 :!mtv:
diff --git a/documentation/doc-Planning_your_migration/master.adoc b/documentation/doc-Planning_your_migration/master.adoc
@@ -12,6 +12,8 @@ include::modules/con_planning-intro.adoc[leveloffset=+1]
 
 include::assemblies/assembly_cold-warm-migration.adoc[leveloffset=+1]
 
+include::assemblies/assembly_live-migration.adoc[leveloffset=+1]
+
 include::assemblies/assembly_prerequisites-for-migration.adoc[leveloffset=+1]
 
 include::assemblies/assembly_installing-mtv-operator.adoc[leveloffset=+1]
diff --git a/documentation/modules/about-mtv.adoc b/documentation/modules/about-mtv.adoc
@@ -24,7 +24,7 @@ These two types of migration are discussed in detail in xref:about-cold-warm-mig
 
 Live migration is available *_only_* for migrations between {virt} clusters or between namespaces on the same {virt} cluster. It requires {project-short} version 2.10 or later and {virt} version 4.20 or later. 
 
-Live migration is discussed in detail in xref:about-live-migration_mtv[About live migration].
+Live migration is discussed in detail in xref:assembly_live_migration_mtv[Live migration in {product-short}].
 
 [IMPORTANT]
 ====
diff --git a/documentation/modules/cnv-cnv-live-prerequisites.adoc b/documentation/modules/cnv-cnv-live-prerequisites.adoc
@@ -9,7 +9,7 @@
 [role="_abstract"]
 In addition to the regular xref:cnv-prerequisites_mtv[virt} prerequisites], live migration has the following additional prerequisites:
 
-* {project-short} 2.10.0 or later installed. For more information, see xref:upgrading-mtv-ui_mtv[Upgrading the {project-full}]. {project-short} treats all {virt} migrations run on {project-short} 2.9 or earlier as cold migrations, even if they are configured as live migrations.
+* {project-first} 2.10.0 or later installed. {project-short} treats all {virt} migrations run on {project-short} 2.9 or earlier as cold migrations, even if they are configured as live migrations.
 * {virt} 4.20.0 or later installed on both source and target clusters.
 * In the {project-short} Operator, in the `spec` portion of the `forklift-controller` YAML, `feature_ocp_live_migration` is set to `true`. You must have `cluster-admin` privileges to set this field.
 * In the `KubeVirt` resource of both clusters in the `featureGates` of the YAML,`DecntralizedLiveMigration` is listed. You must have `cluster-admin` privileges to set this field.
diff --git a/documentation/modules/con_planning-intro.adoc b/documentation/modules/con_planning-intro.adoc
@@ -8,8 +8,33 @@ You can use the Migration Toolkit for Virtualization (MTV) to plan your migratio
 following source providers to OpenShift Virtualization destination providers:
 
 * {vmw} vSphere
-* {rhv-full} ({rhv-short})
+* {rhv-full} 
 * {osp}
 * Open Virtual Appliances (OVAs) that were created by {vmw} vSphere
 * Remote {virt} clusters
 
+== Types of migration
+
+{project-short} supports three types of migration: cold, warm, and live.
+
+* Cold migration is available for all of the source providers listed above. This type of migration migrates VMs that are powered *_off_* and does not require common stored storage. 
+
+* Warm migration is available only for {vmw} vSphere and {rhv-full}. This type of migration migrates VMs that are powered *_on_* and does require common stored storage. 
++
+These two types of migration are discussed in detail in xref:about-cold-warm-migration_mtv[About cold and warm migration].
+
+* Live migration is available *_only_* for migrations between {virt} clusters or between namespaces on the same {virt} cluster. It requires {project-short} version 2.10 or later and {virt} version 4.20 or later. 
++
+Live migration is discussed in detail in xref:assembly_live_migration_mtv[Live migration in {product-short}.
++
+[IMPORTANT]
+====
+Live migration is a Technology Preview feature only. Technology Preview features
+are not supported with Red Hat production service level agreements (SLAs) and
+might not be functionally complete. Red Hat does not recommend using them
+in production. These features provide early access to upcoming product
+features, enabling customers to test functionality and provide feedback during
+the development process.
+For more information about the support scope of Red Hat Technology Preview
+features, see https://access.redhat.com/support/offerings/techpreview/.
+====
diff --git a/documentation/modules/creating-form-based-storage-maps-ui-cnv.adoc b/documentation/modules/creating-form-based-storage-maps-ui-cnv.adoc
@@ -11,7 +11,7 @@ You can create ownerless storage maps by using the form page of the {project-sho
 
 .Prerequisites
 
-* Have a {virt} source provider and a {virt} destination provider. For more information, see xref:adding-source-provider_cnv[Adding {a-virt} source provider] or xref:adding-source-provider_dest_cnv[Adding {a-virt} destination provider].
+* Have a {virt} source provider and a {virt} destination provider. For more information, see xref:adding-source-provider_cnv[Adding {a-virt} source provider] or xref:adding-source-provider_{context}[Adding {a-virt} destination provider].
 
 .Procedure
 
diff --git a/documentation/modules/creating-form-based-storage-maps-ui-rhv.adoc b/documentation/modules/creating-form-based-storage-maps-ui-rhv.adoc
@@ -6,11 +6,11 @@
 [id="creating-form-based-storage-maps-ui-ova_{context}"]
 = Creating ownerless storage maps using the form page of the {project-short} UI
 
+[role="_abstract"]
 You can create ownerless storage maps by using the form page of the {project-short} UI.
 
 .Prerequisites
 
-[role="_abstract"]
 * Have a {rhv-full} source provider and a {virt} destination provider. For more information, see xref:adding-source-provider_rhv[Adding a {rhv-full} source provider] or xref:adding-source-provider_dest_cnv[Adding {a-virt} destination provider].
 
 .Procedure
diff --git a/documentation/modules/selecting-migration-network-for-virt-provider.adoc b/documentation/modules/selecting-migration-network-for-virt-provider.adoc
@@ -20,7 +20,7 @@ In version 2.10.0 and later, {project-short} detects if you have selected a user
 {project-short} supports using UDNs for all providers except {virt}.
 ====
 
-UDNs are discussed in greater detail in xref:about-udn_mtv[About user defined networks]. Migration procedures have been updated to include UDNs.
+// UDNs are discussed in greater detail in xref:about-udn_mtv[About user defined networks]. Migration procedures have been updated to include UDNs.
 
 [NOTE]
 ====
diff --git a/documentation/modules/warm-migration-stages.adoc b/documentation/modules/warm-migration-stages.adoc
@@ -3,14 +3,11 @@
 // * documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc
 
 :_content-type: CONCEPT
-
-= Cold migration and warm migration in {project-short}
-[id="cold-warm-migration_{context}"]
+[id="warm-migration-stages_{context}"]
+= Warm migration in {project-short}
 
 [role="_abstract"]
-Cold migration is when a powered *_off_* virtual machine (VM) is migrated to a separate host. The VM is powered off, and there is no need for common shared storage.
-
-Warm migration is when a powered *_on_* VM is migrated to a separate host. A source host state is cloned to the destination host.
+Warm migration in {project-first} includes the following two stages:
 
 [id="mtv-cold-warm-migration-precopy_{context}"]
 == Warm migration precopy stage
