after QE II

Author: RichardHoch

documentation/modules/creating-plan-wizard-vmware.adoc

@@ -259,7 +259,7 @@ Variable names cannot exceed 63 characters.
 
 *** Click the *Edit* icon.
 *** Click *Enter custom naming template*.
-*** Enter the template according to the instructions. Be sure that your template does not generate VM names that include uppercase letters.
+*** Enter the template according to the instructions. Be sure that your template generates VM names that follow RFC 1123, but do not include uppercase letters.
 *** Click *Save*.
 
 ** To specify a PVC name template only for specific VMs, do the following:
@@ -268,7 +268,7 @@ Variable names cannot exceed 63 characters.
 *** Select the desired VMs.
 *** Click the {kebab} of the VM.
 *** Select *Edit PVC name template*.
-*** Enter the template according to the instructions. Be sure that your template does not generate VM names that include uppercase letters.
+*** Enter the template according to the instructions. Be sure that your template generates VM names that follow RFC 1123, but do not include uppercase letters.
 *** Click *Save*.
 +
 [IMPORTANT]
@@ -296,7 +296,7 @@ Variable names cannot exceed 63 characters.
 
 *** Click the *Edit* icon.
 *** Click *Enter custom naming template*.
-*** Enter the template according to the instructions. Be sure that your template does not generate VM names that include uppercase letters.
+*** Enter the template according to the instructions. Be sure that your template generates VM names that follow RFC 1123, but do not include uppercase letters.
 *** Click *Save*.
 
 ** To specify a different network name template only for specific VMs, do the following:
@@ -305,7 +305,7 @@ Variable names cannot exceed 63 characters.
 *** Select the desired VMs.
 *** Click the {kebab} of the VM.
 *** Select *Edit Network name template*.
-*** Enter the template according to the instructions. Be sure that your template does not generate VM names that include uppercase letters.
+*** Enter the template according to the instructions. Be sure that your template generates VM names that follow RFC 1123, but do not include uppercase letters.
 *** Click *Save*.
 +
 [IMPORTANT]
@@ -315,7 +315,7 @@ Changes you make on the *Virtual Machines* tab override any changes on the *Plan
 +
 [IMPORTANT]
 ====
-{project-short} does not validate VM names generated by the templates you enter on the *Plan details* page. Migrations that include VMs whose names include uppercase letters fail automatically. To avoid failures, you might want to run a Go script that uses the `sprig` methods that {project-short} supports. For tables documenting the methods that {project-short} supports, see {mtv-mig}assembly_migrating-from-vmware#mtv-template-utility_vmware[{project-short} template utility for {vmw} VM names].
+{project-short} does not validate VM names generated by the templates you enter on the *Plan details* page. Migrations that include VMs whose names include uppercase letters or that violate RFC 1123 rules fail automatically. To avoid failures, you might want to run a Go script that uses the `sprig` methods that {project-short} supports. For tables documenting the methods that {project-short} supports, see {mtv-mig}assembly_migrating-from-vmware#mtv-template-utility_vmware[{project-short} template utility for {vmw} VM names].
 ====
 
 .. *Raw copy mode*: By default, during migration, virtual machines (VMs) are converted using a tool named `virt-v2v` that makes them compatible with {virt}. For more information about the virt-v2v conversion process, see 'How {project-short} uses the virt-v2v tool' in _Migrating your virtual machines to Red Hat {virt}_. _Raw copy mode_ copies VMs without converting them. This allows for faster conversions, migrating VMs running a wider range of operating systems, and supporting migrating disks encrypted using Linux Unified Key Setup (LUKS) without needing keys. However, VMs migrated using raw copy mode might not function properly on {virt}.

documentation/modules/proc_migrating-virtual-machines-cli.adoc

@@ -879,7 +879,13 @@ The template follows the Go template syntax and has access to the following vari
 * `"net-{{.NetworkIndex}}"`
 * `{{if eq .NetworkType "pod"}}pod{{else}}multus-{{.NetworkIndex}}{{end}}"`
 +
-Variable names cannot exceed 63 characters. This rule applies to a network name network template, a PVC name template, a VM name template, and a volume name template.
+Variable names cannot exceed 63 characters. VM names geneated by templates must not include uppercase letters or violate RFC 1123 rules.  These rules apply to a network name network template, a PVC name template, a VM name template, and a volume name template.
++
+[IMPORTANT]
+====
+{project-short} does not validate VM names generated by the templates described here. Migrations that include VMs whose names include uppercase letters or that violate RFC 1123 rules fail automatically. To avoid failures, you might want to run a Go script that uses the `sprig` methods that {project-short} supports. For tables documenting the methods that {project-short} supports, see xref:mtv-template-utility_vmware[{project-short} template utility for {vmw} VM names].
+====
++
 <10> [[callout10]]Optional. Specify a template for the persistent volume claim (PVC) name for a plan.
 The template follows the Go template syntax and has access to the following variables:
 * `.VmName`: Name of the VM.
@@ -933,11 +939,7 @@ The template follows the Go template syntax and has access to the following vari
 <26> Allowed values are `PreHook` before the migration plan starts or `PostHook` after the migration is complete.
 +
 include::snip_vmware-name-change.adoc[]
-+
-[IMPORTANT]
-====
-{project-short} does not validate VM names generated by the templates described here. Migrations that include VMs whose names include uppercase letters fail automatically. To avoid failures, you might want to run a Go script that uses the `sprig` methods that {project-short} supports. For tables documenting the methods that {project-short} supports, see xref:mtv-template-utility_vmware[{project-short} template utility for {vmw} VM names].
-====
+
 endif::[]
 
 ifdef::rhv[]