diff --git a/content/modules/ROOT/assets/images/module-01-intro/02_VM_List.png b/content/modules/ROOT/assets/images/module-01-intro/02_VM_List.png index ee702bc..ef22263 100644 Binary files a/content/modules/ROOT/assets/images/module-01-intro/02_VM_List.png and b/content/modules/ROOT/assets/images/module-01-intro/02_VM_List.png differ diff --git a/content/modules/ROOT/pages/module-01-intro.adoc b/content/modules/ROOT/pages/module-01-intro.adoc index 8dbb69e..46a88bd 100644 --- a/content/modules/ROOT/pages/module-01-intro.adoc +++ b/content/modules/ROOT/pages/module-01-intro.adoc @@ -38,18 +38,15 @@ image::module-01-intro/01_Left_Menu.png[link=self, window=blank, width=100%] The *Virtualization* tab is available only when Red Hat OpenShift Virtualization is installed and properly configured. In this lab environment the installation and configuration has already been performed for us. ==== +. From the *Projects* dropdown switch to the project `vmimported-{user}`. + . 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*. +.. Click *Project: vmimported-{user}* 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%] diff --git a/content/modules/ROOT/pages/module-02-mtv.adoc b/content/modules/ROOT/pages/module-02-mtv.adoc index 435beda..0b558ec 100644 --- a/content/modules/ROOT/pages/module-02-mtv.adoc +++ b/content/modules/ROOT/pages/module-02-mtv.adoc @@ -59,7 +59,7 @@ NOTE: You will not need to migrate the HAproxy (load balancer) VM because OpenSh To help understand the process of mapping resources, such as datastores and port groups, from vSphere into OpenShift's equivalents, storage classes and network attachment definitions, let's begin by reviewing the source environment for the migrations. . Navigate to VMware vCenter: https://{vcenter_console}[vCenter Console^] - +. Click on *Launch vSphere Client* . Login with the following credentials: - *User:* {vcenter_full_user} - *Password:* {vcenter_password}