Merge pull request #1 from rhpds/ac-edits

AC-Edits

README.adoc

@@ -42,9 +42,10 @@ These are the *eight* main sections that will be covered:
 
 This edition of the  OpenShift Virtualization Roadshow has been developed using the following software versions:
 
-* Red Hat OpenShift 4.15.16
-* Red Hat OpenShift Virtualization 4.15.2
-* Red Hat OpenShift Data Foundation 4.15.3
-* Red Hat OADP 1.1.8
-* Red Hat Migration Toolkit for Virtual Machines 2.6.2
+* Red Hat OpenShift 4.16.5
+* Red Hat OpenShift Virtualization 4.16.1
+* Red Hat OpenShift Data Foundation 4.16.0
+* Red Hat OADP 1.4.0
+* Red Hat Migration Toolkit for Virtual Machines 2.6.3
 
+(Accurate as of Aug 16, 2024)

content/modules/ROOT/pages/module-07-tempinst.adoc

@@ -14,7 +14,7 @@ The *Templates* page displays four types of virtual machine templates:
 [[prepare_templates_lab]]
 == Prepare for the lab
 
-The VM you are about to create is a bit larger than previous VMs. To ensure that your environment has enough resources stop all other running VMs.
+. The tasks that we are about to perform will require us to provision a few additional VMs. In preparation we are going to ask that you shut down the existing *fedora01* and *fedora02* virtual machines to ensure that your shared environment has enough resources to complete the lab.
 
 . Navigate to *Virtualization -> Virtualmachines*
 . Make sure you check every project that you have access to to see all VMs in the environment. At a minimum you should check projects `vmimported-{user}` and `vmexamples-{user}`
@@ -25,7 +25,7 @@ Now all VMs should be in *Stopped* state.
 [[clone_customize_template]]
 == Clone and Customize a Template
 
-By default pre-configured templates provided by Red Hat OpenShift Virtualization cannot be customized. However you can clone a template and make adjustments to it for your particular workload in order to make it easier to request specific types of virtual machines for specific workloads. In this section of the lab we are going to do just this, by creating a template that will provide a database server on demand for our end users.
+By default pre-configured the templates provided by Red Hat OpenShift Virtualization cannot be customized. However you can clone a template and make adjustments to it for your particular workload in order to make it easier to request specific types of virtual machines for specific workloads. In this section of the lab we are going to do just this, by creating a template that will provide a preconfigured database server on demand for our end users.
 
 . To begin, navigate to *Virtualization* -> *Templates* and select *openshift* for your project (you may need to open the *Project* drop-down and click the radio button next to *Show default projects*).
 +
@@ -35,9 +35,9 @@ image::module-07-tempinst/01_Template_List.png[link=self, window=blank, width=10
 +
 image::module-07-tempinst/02_Search_Centos9.png[link=self, window=blank, width=100%]
 
-. Select the three-dot menu to the far right, and click on the option to *Clone* from the menu that pops out.
+. Click on the template name for *centos-stream90-server-small*, you will be prompted with a message that default templates cannot be edited and asked if you'd like to clone. Click the *Create a new custom Template* option.
+image::module-07-tempinst/03_Create_Custom_Template.png[link=self, window=blank, width=100%]
 +
-image::module-07-tempinst/03_Clone_Template.png[link=self, window=blank, width=100%]
 
 . A new menu called *Clone template* will appear, fill in the the following values, and when finished click on the *Clone* button.
 +
@@ -51,7 +51,7 @@ image::module-07-tempinst/04_Clone_Template_Options.png[link=self, window=blank,
 +
 image::module-07-tempinst/05_Clone_Details.png[link=self, window=blank, width=100%]
 
-. A new window will pop out where you can edit the amount of CPU and Memory. For our XL template set the value of CPUs to 2, and Memory to 4 GiB, and click the *Save* button.
+. A new window will pop out where you can edit the amount of CPU and Memory. For our custom template set the value of CPUs to 2, and Memory to 4 GiB, and click the *Save* button.
 +
 image::module-07-tempinst/06_Edit_CPU_Mem.png[link=self, window=blank, width=100%]
 
@@ -78,16 +78,16 @@ userData: |-
 image::module-07-tempinst/10_Cloud_Init_Script.png[link=self, window=blank, width=100%]
 
 . Click the *Save* button, followed by the *Apply* button.
-. Now click on the *Virtualization -> Catalog* menu on the left, select the *Template catalog* option and click on *User templates*. You should see our created template available as a tile.
+
+. Now click on the *Virtualization -> Catalog* menu on the left, select the *Template catalog* option. You should see your created template available as a tile with all the others.
 +
 image::module-07-tempinst/11_User_Templates.png[link=self, window=blank, width=100%]
 
 . Click on the tile and you will be prompted with the VM startup screen. Click the *Quick create VirtualMachine* button.
 +
 image::module-07-tempinst/12_Quick_Create_Template.png[link=self, window=blank, width=100%]
 
-. When the virtual machine boots you can see on the *Overview* page that it was created from our template, and has the system resources we defined, and is already attached to the
-Pod network with an assigned IP address.
+. When the virtual machine boots you can see on the *Overview* page that it was created from our template, and has the additional resources we defined. We just need to verify that it installed *MariaDB* for us.
 +
 image::module-07-tempinst/13_VM_From_Template.png[link=self, window=blank, width=100%]