Updates for modules 1, 2 and 3

content/modules/ROOT/pages/index.adoc

@@ -78,7 +78,7 @@ If you would like to learn more about OpenShift Virtualization, please visit the
 
 Your OpenShift cluster console is available {console_url}[here^].
 
-Administrator login is available with:
+Your login is available with:
 
 * *User:* {user}
 * *Password:* {password}

content/modules/ROOT/pages/module-01-intro.adoc

@@ -13,18 +13,22 @@ The beginning section of this lab will introduce you to the basics of creating a
 
 As a reminder, here are your credentials for the OpenShift Console:
 
-Your OpenShift cluster console is available {openshift_cluster_console_url}[here^].
+Your OpenShift cluster console is available {console_url}[here^].
 
-Administrator login is available with:
+Your login is available with:
 
-* *User:* {openshift_cluster_admin_username}
-* *Password:* {openshift_cluster_admin_password}
+* *User:* {user}
+* *Password:* {password}
 
 [[create_project]]
 == Create a New Project
 
 Like other objects in OpenShift, Projects (which are an abstraction for Kubnernetes namespaces), are the boundaries for permissions and other aspects of using and manaing the resources. Creating a Project is an important first step for any deployment.
 
+. The first time you log into the console you will see the *Developer* perspective. Click *Skip tour* to dismiss the prompt. Then click on *Developer* and switch to *Administrator*.
++
+image::module-01-intro/00_Admin_Perpspective.png[link=self, window=blank, width=100%]
+
 . Browse to *Virtualization* -> *VirtualMachines* using the left navigation menu:
 +
 image::module-01-intro/01_Left_Menu.png[link=self, window=blank, width=100%]
@@ -37,14 +41,19 @@ The *Virtualization* tab is available only when Red Hat OpenShift Virtualization
 . Examine the *VirtualMachines* dashboard that appears. There are currently several VMs listed, but they are not turned on:
 +
 image::module-01-intro/02_VM_List.png[link=self, window=blank, width=100%]
++
+[NOTE]
+====
+If you don't see any VMs make sure to switch to the project `vmimported-{user}`.
+====
 
 . Before creating a VM we need to create a new project. Virtual machines are deployed to a specific project, or namespace, where by default, users without permission to the namespace cannot access, manage, or control them. Administrators can access all projects, and therefore view all virtual machines, however regular users must be given access to projects as needed.
 +
 .. Click *Project: All Projects* at the lop left of the window and then click *Create Project*.
 +
 image::module-01-intro/02_All_Projects.png[link=self, window=blank, width=100%]
 
-.. In the *Name* field, type *vmexamples* to name the project, then click *Create*.
+.. In the *Name* field, type *vmexamples-{user}* to name the project, then click *Create*.
 +
 image::module-01-intro/03_Create_Project.png[link=self, window=blank, width=100%]
 
@@ -163,6 +172,11 @@ In this section, we will migrate the VM from one OpenShift node to another witho
 . Navigate to the *Overview* tab to see where the worker node is running:
 +
 image::module-01-intro/20_VM_Info_Node.png[link=self, window=blank, width=100%]
++
+[NOTE]
+====
+Only cluster administrators can see the Node - the screenshot is an example of what an admin would see. But you can still migrate the VM - you just won't see the node change.
+====
 
 . Using the *Actions* menu, select the option to *Migrate*.
 +

content/modules/ROOT/pages/module-02-mtv.adoc

@@ -81,7 +81,7 @@ image::module-02-mtv/02_vSphere_Datastore.png[link=self, window=blank, width=100
 The *Migration Toolkit for Virtualization* (*MTV*) uses the VMware Virtual Disk Development Kit (*VDDK*) SDK to transfer virtual disks from VMware vSphere. The VDDK has already been configured for you in this environment.
 
 . Navigate in the left menu to *Migration* -> *Providers for virtualization*
-. Select project *openshift-mtv* (You may need to toggle the *Show default projects* slider.)
+. Select project *mtv-{user}*
 +
 image::module-02-mtv/03_MTV_Providers.png[link=self, window=blank, width=100%]
 +
@@ -121,7 +121,8 @@ image::module-02-mtv/17_VM_Select_VMWARE_Plan.png[link=self, window=blank, width
 Please fill in your migration plan with the following values:
 
 * Plan name: *move-webapp-vmware*
-* Target namespace: *vmexamples*
+* Target provider: *host*
+* Target namespace: *vmexamples-{user}*
 * Network map: *Pod Networking*
 * Storage map: *ocs-external-storagecluster-ceph-rbd*
 +
@@ -135,7 +136,7 @@ image::module-02-mtv/18_Create_Migration_Plan.png[link=self, window=blank, width
 +
 image::module-02-mtv/19_Migration_Plan_Unready.png[link=self, window=blank, width=100%]
 
-. After a few moments the plan will become *Ready*, click on the green "Play" button in the center of the window to start the migration process.
+. After a few moments the plan will become *Ready*, click on the blue "Start Migration" button to start the migration process.
 +
 image::module-02-mtv/20_Migration_Plan_Ready.png[link=self, window=blank, width=100%]
 
@@ -155,7 +156,12 @@ image::module-02-mtv/23_VMs_Migrating_Details.png[link=self, window=blank, width
 +
 image::module-02-mtv/24_VM_Migration_Stages.png[link=self, window=blank, width=100%]
 +
-*IMPORTANT:* Having many participants performing the same task in parallel in a simulated lab environment can cause this task to perform much slower than in a real environment. For this lab instance we have limited the number of in-flight VMs to 2 at a time. Please be patient with this process as it completes. You may continue with other sections in the roadshow as the migrations complete.
+[IMPORTANT]
+====
+Having many participants performing the same task in parallel in a simulated lab environment can cause this task to perform much slower than in a real environment. For this lab instance we have limited the number of in-flight VMs to 2 at a time. Please be patient with this process as it completes. You may continue with other sections in the roadshow as the migrations complete.
+
+Also the Migration Toolkit Documentation suggests at least a 10Gb connection between the data centers - which is not something that is available in this demo.
+====
 
 . After several minutes the migration has completed.
 +