From e93ca51a4427a6002119ae843e2df11727d03cc9 Mon Sep 17 00:00:00 2001 From: Xphyr Date: Mon, 24 Feb 2025 14:30:46 -0500 Subject: [PATCH] fixing a few gramatical errors and updating some highlighting for more consistency --- content/modules/ROOT/pages/02-aap-smart-inventory.adoc | 2 +- content/modules/ROOT/pages/03-vm-management.adoc | 6 +++--- content/modules/ROOT/pages/04-vm-patching.adoc | 8 ++++---- content/modules/ROOT/pages/06-vm-backup.adoc | 4 ++-- 4 files changed, 10 insertions(+), 10 deletions(-) diff --git a/content/modules/ROOT/pages/02-aap-smart-inventory.adoc b/content/modules/ROOT/pages/02-aap-smart-inventory.adoc index b23b82f..a04c716 100644 --- a/content/modules/ROOT/pages/02-aap-smart-inventory.adoc +++ b/content/modules/ROOT/pages/02-aap-smart-inventory.adoc @@ -110,7 +110,7 @@ vms-aap-day2-rhel9-vm3 | SUCCESS => { You may also confirm the VMs are running using the **OpenShift UI** dashboard {openshift_cluster_console_url}: -Virtualization -> VirtualMachines within the `vms-aap-day2` project. +**Virtualization -> VirtualMachines** within the `vms-aap-day2` project. image::vms-ocp-dashboard.png[title='Virtual Machines Running on OpenShift', link=self, window=blank] diff --git a/content/modules/ROOT/pages/03-vm-management.adoc b/content/modules/ROOT/pages/03-vm-management.adoc index 73b55d0..3ab0d8a 100644 --- a/content/modules/ROOT/pages/03-vm-management.adoc +++ b/content/modules/ROOT/pages/03-vm-management.adoc @@ -86,7 +86,7 @@ image::new_file.png[title='New File Creation', link=self, window=blank] Explanation of the Task: + * The `kubevirt_vm` module that is part of the `redhat.openshift_virtualization` collection is used to modify a VM - * The `name` parameter uses a user defined variable named `vm_name` to specify which VM to stop + * The `name` parameter uses a user defined variable named `vm_name` to specify which VM to stop * The `run_strategy: Halted` ensures the VM is not running * The `wait: true` ensures the next Ansible task isn't triggered until the stop is complete + @@ -221,7 +221,7 @@ image::stop_vms_multiple.png[title='Stopping the VMs', link=self, window=blank] In this lab exercise, you will build on your knowledge of managing multiple VMs by creating a task to start your VMs within the `vm_management` role. This task -will be added to the tasks directory in a file named `start_vm.yml`. +will be added to the `tasks` directory in a file named `start_vm.yml`. The following steps will guide you in creating the `start_vm.yml` file. @@ -280,7 +280,7 @@ To execute the `manage_vm_playbook.yml` within Ansible Automation Platform, crea + . Once the `Start VMs` Job Template is created, select the **Launch Template** button on the top right corner to run the job. + -. Head to the OpenShift UI dashboard, you can verify the VMs are running within the Virtualization -> Virtual Machines section. +. Head to the OpenShift UI dashboard, you can verify the VMs are running within the **Virtualization -> Virtual Machines** section. === Restart VM Task diff --git a/content/modules/ROOT/pages/04-vm-patching.adoc b/content/modules/ROOT/pages/04-vm-patching.adoc index 5a55dbd..14df763 100644 --- a/content/modules/ROOT/pages/04-vm-patching.adoc +++ b/content/modules/ROOT/pages/04-vm-patching.adoc @@ -57,15 +57,15 @@ image::new_file.png[title='New File Creation', link=self, window=blank] + . Re-sync the `Workshop Project` with your latest updates within the Ansible Automation Platform UI + -** Navigate to Automation Execution → Projects and select `Workshop Project` +** Navigate to **Automation Execution → Projects** and select `Workshop Project` + -** On the top right, select the `Sync Project` button and wait for `Last job status` to provide the status of `Success`. +** On the top right, select the **Sync Project** button and wait for `Last job status` to provide the status of `Success`. === Create & Run Update Security Packages Job Template with Ansible Automation Platform To execute the `patch_vm_playbook.yml` within Ansible Automation Platform, create a Job Template as follows: -. Navigate to Automation Execution → Templates, click the **Create template** button, and choose **Create job template**. +. Navigate to **Automation Execution → Templates**, click the **Create template** button, and choose **Create job template**. + . Fill out the following details: + @@ -92,7 +92,7 @@ To execute the `patch_vm_playbook.yml` within Ansible Automation Platform, creat + image::patch_vm.png[title='Patch VM', link=self, window=blank] + -This gives a breakdown of all the taks that ran and a play recap of the changes +This gives a breakdown of all the tasks that ran and a play recap of the changes made to the different hosts. If you take a closer look at the `Update security-related packages on all hosts` task, you can drill into specific host details on what was installed on the system(s). diff --git a/content/modules/ROOT/pages/06-vm-backup.adoc b/content/modules/ROOT/pages/06-vm-backup.adoc index 897d218..adf828f 100644 --- a/content/modules/ROOT/pages/06-vm-backup.adoc +++ b/content/modules/ROOT/pages/06-vm-backup.adoc @@ -355,11 +355,11 @@ One key difference during the creation of the `VirtualMachineRestore` using the `vm_snapshots: ` |=== -WARNING: Replace with the name of your snapthot created previously. +WARNING: Replace with the name of your snapshot created previously. Launch the template. -Once the Job completes successfully, confirm the restoration of the Snapshot was applied to the `rhel9-vm1` by navigating to the OpenShift UI, Virtualization -> VirtualMachines within the `vms-aap-day2` project. +Once the Job completes successfully, confirm the restoration of the Snapshot was applied to the `rhel9-vm1` by navigating to the OpenShift UI, **Virtualization -> VirtualMachines** within the `vms-aap-day2` project. Select the `rhel9-vm1` instance and then select the *Snapshots* tab. Locate the Snapshot created previously and notice the date and time within the _Last restored_ column indicating that the Snapshot was successfully restored against the Virtual Machine instance.