Merge pull request #130 from apinnick/small-changes

various organizational changes

documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc

@@ -27,8 +27,8 @@ endif::[]
 include::modules/mtv-resources-and-services.adoc[leveloffset=+2]
 include::modules/mtv-workflow.adoc[leveloffset=+2]
 include::modules/virt-migration-workflow.adoc[leveloffset=+2]
-include::modules/about-storage.adoc[leveloffset=+2]
-include::modules/about-warm-migration.adoc[leveloffset=+2]
+include::modules/storage-support.adoc[leveloffset=+2]
+include::modules/warm-migration.adoc[leveloffset=+2]
 
 [id='installing-mtv_{context}']
 == Installing {the-lc} {project-full}
@@ -42,16 +42,23 @@ After you have installed {project-short}, you must create a VMware Virtual Disk
 
 If you are performing more than 10 concurrent VM migrations from a single ESXi host, you must increase the NFC service memory of the host to enable additional connections for migrations. Otherwise, the migration will fail because the NFC service memory is limited to 10 parallel connections.
 
+include::modules/migration-environment-requirements.adoc[leveloffset=+2]
+
+[id="installing-the-operator_{context}"]
+=== Installing the {operator-name}
+
+You can install the {operator-name} by using the {project-short} web console or the command line interface (CLI).
+
 :context: web
 :web:
-include::modules/installing-mtv-console.adoc[leveloffset=+2]
+include::modules/installing-mtv-operator.adoc[leveloffset=+3]
 
 [discrete]
 include::modules/obtaining-console-url.adoc[leveloffset=+3]
 :!web:
 :context: cli
 :cli:
-include::modules/installing-mtv-console.adoc[leveloffset=+2]
+include::modules/installing-mtv-operator.adoc[leveloffset=+3]
 
 [discrete]
 include::modules/obtaining-console-url.adoc[leveloffset=+3]
@@ -60,33 +67,51 @@ include::modules/obtaining-console-url.adoc[leveloffset=+3]
 :mtv:
 
 include::modules/adding-vddk-to-mtv.adoc[leveloffset=+2]
-include::modules/increasing-esxi-nfc-service-memory.adoc[leveloffset=+2]
 
 [id="migrating-virtual-machines-to-virt_{context}"]
 == Migrating virtual machines to {virt}
 
 You can migrate virtual machines (VMs) to {virt} by using the {project-short} web console or the command line interface (CLI).
 
-You can run a cold or a warm migration. For details, see xref:about-warm-migration.adoc#about-warm-migration_{context}[About warm migration].
+You can run a cold or a warm migration. For details, see xref:warm-migration.adoc#warm-migration_{context}[Warm migration].
+
+If you are performing more than 10 concurrent migrations from a single ESXi host, you must increase the NFC service memory of the host.
 
-include::modules/migration-prerequisites.adoc[leveloffset=+2]
+include::modules/increasing-esxi-nfc-service-memory.adoc[leveloffset=+2]
 
 [id='migrating-vms-web-console_{context}']
 === Migrating virtual machines by using the {project-short} web console
 
 You can migrate virtual machines to {virt} by using the {project-short} web console.
 
-include::modules/adding-source-provider.adoc[leveloffset=+3]
+[id="adding-providers_{context}"]
+==== Adding providers
+
+You can add VMware and {virt} providers by using the {project-short} web console.
+
+include::modules/adding-source-provider.adoc[leveloffset=+4]
+
+[discrete]
 include::modules/selecting-migration-network-for-source-provider.adoc[leveloffset=+4]
-include::modules/adding-virt-provider.adoc[leveloffset=+3]
+
+include::modules/adding-virt-provider.adoc[leveloffset=+4]
+
+[discrete]
 include::modules/selecting-migration-network-for-virt-provider.adoc[leveloffset=+4]
+
 include::modules/creating-network-mapping.adoc[leveloffset=+3]
 include::modules/creating-storage-mapping.adoc[leveloffset=+3]
 include::modules/creating-migration-plan.adoc[leveloffset=+3]
 include::modules/running-migration-plan.adoc[leveloffset=+3]
-include::modules/canceling-migration-ui.adoc[leveloffset=+3]
 
 include::modules/migrating-virtual-machines-cli.adoc[leveloffset=+2]
+
+[id="canceling-migration_{context}"]
+=== Canceling a migration
+
+You can cancel a migration by using the {ocp} web console or the command line interface (CLI).
+
+include::modules/canceling-migration-ui.adoc[leveloffset=+3]
 include::modules/canceling-migration-cli.adoc[leveloffset=+3]
 
 [id="uninstalling-mtv_{context}"]

documentation/doc-Migration_Toolkit_for_Virtualization/modules/adding-hooks.adoc

@@ -16,7 +16,8 @@ You can create a hook before a migration plan or while creating a migration plan
 
 .Procedure
 
-. In the web console, navigate to *Hooks* and click *Create hook*.
+. In the web console, click *Hooks*.
+. Click *Create hook*.
 . Specify the hook *Name*.
 . Select *Ansible playbook* or *Custom container image* as the *Hook definition*.
 . If you select *Custom container image*, specify the image location, for example, `quay.io/github_project/container_name:container_id`.

documentation/doc-Migration_Toolkit_for_Virtualization/modules/adding-vddk-to-mtv.adoc

@@ -3,7 +3,7 @@
 // * documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc
 
 [id="adding-vddk-to-mtv_{context}"]
-= Creating a VDDK image
+= Creating a VDDK image and adding it to a config map
 
 {project-first} uses the VMware Virtual Disk Development Kit (VDDK) SDK to transfer virtual disks.
 
@@ -17,8 +17,8 @@ Storing the VDDK image in a public registry might violate the VMware license ter
 .Prerequisites
 
 * link:https://docs.openshift.com/container-platform/{ocp-version}/registry/configuring_registry_storage/configuring-registry-storage-baremetal.html[{ocp} image registry] or a secure link:https://docs.openshift.com/container-platform/{ocp-version}/registry/registry-options.html[external registry].
-* Podman installed.
-* If you are using an external registry, {virt} must have access.
+* `podman` installed.
+* If you are using an external registry, {virt} must be able to access it.
 
 .Procedure
 

documentation/doc-Migration_Toolkit_for_Virtualization/modules/canceling-migration-cli.adoc

@@ -3,7 +3,7 @@
 // * documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc
 
 [id="canceling-migration-cli_{context}"]
-= Cancelling a migration
+= Canceling a migration from the command line interface
 
 You can cancel an entire migration or individual virtual machines (VMs) while a migration is in progress from the command line interface (CLI).
 

documentation/doc-Migration_Toolkit_for_Virtualization/modules/canceling-migration-ui.adoc

@@ -3,7 +3,7 @@
 // * documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc
 
 [id="canceling-migration-ui_{context}"]
-= Cancelling a migration
+= Canceling a migration by using the {project-short} web console
 
 You can cancel the migration of some or all virtual machines while a migration plan is in progress by using the {project-short} web console.
 

documentation/doc-Migration_Toolkit_for_Virtualization/modules/creating-migration-plan.adoc

@@ -14,32 +14,39 @@ A migration plan allows you to group virtual machines that should be migrated to
 * You must create a VDDK image and add it to the `v2v-vmware` config map.
 * You must add a source provider to the web console.
 * If the target provider is not the {virt} cluster on which you installed {project-short}, you must add a target provider.
-* For warm migration, you must enable link:https://kb.vmware.com/s/article/1020128[changed block tracking] on the virtual machines and on the virtual machine disks.
+* If you are running a warm migration, you must enable link:https://kb.vmware.com/s/article/1020128[changed block tracking (CBT)] on the VMs and on the VM disks.
+* If you are performing more than 10 concurrent migrations from a single ESXi host, you must increase the NFC service memory of the host.
 
 .Procedure
 
-. In the web console, navigate to *Migration plans* and click *Create migration plan*.
+. In the web console, click *Migration plans* and then click *Create migration plan*.
 . Complete the following fields:
 
 * *Plan name*: Enter a migration plan name to display in the migration plan list.
 * *Plan description*: Optional. Brief description of the migration plan.
 * *Source provider*: Select a source provider.
 * *Target provider*: Select a target provider.
-* *Target namespace*: You can type to search for an existing target namespace or create a new namespace.
+* *Target namespace*: You can type to search for an existing target namespace or  create a new namespace.
 * You can change the migration transfer network for this plan by clicking *Select a different network*, selecting a network from the list, and clicking *Select*.
 +
 If you defined a migration transfer network for the {virt} provider and if the network is in the target namespace, that network is the default network for all migration plans. Otherwise, the `pod` network is used.
 
 . Click *Next*.
-. Click *By clusters and hosts* or *By folders*, select clusters, hosts, or folders to filter the VMs, and then click *Next*.
-. Select the VMs to migrate and click *Next*.
+. Click *By clusters and hosts* or *By folders*, select clusters, hosts, or folders to _filter_ the list of VMs, and then click *Next*.
+. Select the VMs to migrate and then click *Next*.
 . Select an existing network mapping or create a new network mapping.
-. If you select *Create a new network mapping*, select a target network for each source network.
-. Optional. If you want to save the network mapping, select *Save mapping to use again* and enter a network mapping name.
++
+To create a new network mapping:
+
+* Select a target network for each source network.
+* Optional. Select *Save mapping to use again* and enter a network mapping name.
 . Click *Next*.
 . Select an existing storage mapping or create a new storage mapping.
-. If you select *Create a new storage mapping*, select a target storage class for each source data store.
-. Optional. If you want to save the storage mapping, select *Save mapping to use again* and enter a storage mapping name.
++
+To create a new storage mapping:
+
+* Select a target storage class for each source data store.
+* Optional. Select *Save mapping to use again* and enter a storage mapping name.
 . Click *Next*.
 
 . Select *Cold migration* or *Warm migration* and click *Next*.

documentation/doc-Migration_Toolkit_for_Virtualization/modules/creating-network-mapping.adoc

@@ -18,7 +18,7 @@ You cannot map an opaque network, typically managed by NSX, to {a-virt} network.
 
 .Procedure
 
-. In the web console, navigate to *Mappings* -> *Network*.
+. Click *Mappings* -> *Network*.
 . Click *Create mapping*.
 . Complete the following fields:
 

documentation/doc-Migration_Toolkit_for_Virtualization/modules/creating-storage-mapping.adoc

@@ -14,7 +14,7 @@ You can create a storage mapping by using the {project-short} web console to map
 
 .Procedure
 
-. In the web console, navigate to *Mappings* -> *Storage*.
+. Click *Mappings* -> *Storage*.
 . Click *Create mapping*.
 . Complete the following fields: