From 68908e2565849467ef9592d590776b5afeac4b0a Mon Sep 17 00:00:00 2001 From: RichardHoch Date: Tue, 29 Oct 2024 14:36:14 +0200 Subject: [PATCH] fix --- .../doc-Migration_Toolkit_for_Virtualization/master.adoc | 8 ++++---- ...gration-plan.adoc => creating-migration-plan-2-7.adoc} | 2 +- documentation/modules/snip-mtu-value.adoc | 2 +- 3 files changed, 6 insertions(+), 6 deletions(-) rename documentation/modules/{creating-migration-plan.adoc => creating-migration-plan-2-7.adoc} (99%) diff --git a/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc b/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc index b4e4f2bbe5d..0ebecb9cf85 100644 --- a/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc +++ b/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc @@ -192,8 +192,8 @@ You can create a migration plan by using the {ocp} web console to specify a sour For your convenience, there are two procedures to create migration plans, starting with either a source provider or with specific VMs: -* To start with a source provider, see xref:creating-migration-plan_provider[Creating a migration plan starting with a source provider]. -* To start with specific VMs, see xref:creating-migration-plan_vms[Creating a migration plan starting with specific VMs]. +* To start with a source provider, see xref:creating-migration-plan-2-7_provider[Creating a migration plan starting with a source provider]. +* To start with specific VMs, see xref:creating-migration-plan-2-7_vms[Creating a migration plan starting with specific VMs]. [WARNING] ==== @@ -208,12 +208,12 @@ include::modules/snip_plan-limits.adoc[] :context: provider :provider: -include::modules/creating-migration-plan.adoc[leveloffset=+3] +include::modules/creating-migration-plan-2-7.adoc[leveloffset=+3] :provider!: :context: vms :vms: -include::modules/creating-migration-plan.adoc[leveloffset=+3] +include::modules/creating-migration-plan-2-7.adoc[leveloffset=+3] :vms!: :context: mtv diff --git a/documentation/modules/creating-migration-plan.adoc b/documentation/modules/creating-migration-plan-2-7.adoc similarity index 99% rename from documentation/modules/creating-migration-plan.adoc rename to documentation/modules/creating-migration-plan-2-7.adoc index 6887e1abdaa..9d4bf8c035d 100644 --- a/documentation/modules/creating-migration-plan.adoc +++ b/documentation/modules/creating-migration-plan-2-7.adoc @@ -1,7 +1,7 @@ // * documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc :_mod-docs-content-type: PROCEDURE -[id="creating-migration-plan_{context}"] +[id="creating-migration-plan-2-7_{context}"] ifdef::provider[] = Creating a migration plan starting with a source provider diff --git a/documentation/modules/snip-mtu-value.adoc b/documentation/modules/snip-mtu-value.adoc index 75fce42119e..c2f65895a0a 100644 --- a/documentation/modules/snip-mtu-value.adoc +++ b/documentation/modules/snip-mtu-value.adoc @@ -2,5 +2,5 @@ [NOTE] ==== -If you input any value of maximum transmission unit (MTU) besides the default value in your migration network, you must also input the same value in the {ocp-short} transfer network that you use For more information about the {ocp-short} transfer network, see xref:creating-migration-plan_provider[Creating a migration plan starting with a source provider] or xref:creating-migration-plan_vms[Creating a migration plan starting with specific VMs]. +If you input any value of maximum transmission unit (MTU) besides the default value in your migration network, you must also input the same value in the {ocp-short} transfer network that you use For more information about the {ocp-short} transfer network, see xref:creating-migration-plan-2-7_provider[Creating a migration plan starting with a source provider] or xref:creating-migration-plan-2-7_vms[Creating a migration plan starting with specific VMs]. ==== \ No newline at end of file