From 635e5190ac0823bf317304a27dc792a3b40e356a Mon Sep 17 00:00:00 2001 From: Juliano Mohr <1110178+juliaaano@users.noreply.github.com> Date: Mon, 16 Dec 2024 15:32:41 +0000 Subject: [PATCH] Update VM hot-add and backup instructions --- content/modules/ROOT/pages/05-vm-hot-add.adoc | 3 ++- content/modules/ROOT/pages/06-vm-backup.adoc | 4 +++- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/content/modules/ROOT/pages/05-vm-hot-add.adoc b/content/modules/ROOT/pages/05-vm-hot-add.adoc index a464689..63b9a12 100644 --- a/content/modules/ROOT/pages/05-vm-hot-add.adoc +++ b/content/modules/ROOT/pages/05-vm-hot-add.adoc @@ -75,7 +75,7 @@ cd collections/ansible_collections/redhatone/vm_management/roles/vm_management/t touch hot_plug.yml ---- + -. Open the `hot_plug.yml` File in Your Favorite Editor and Add the Following Tasks: +. Open the `hot_plug.yml` File in VSCode and add the either of the following tasks based on the VM configuration: === Using the `instance_type` (Recommended) @@ -183,6 +183,7 @@ reusability and standardization. Understanding both methods equips you with the knowledge to handle scenarios where instance types may not be available. Through this lab, you have learned how to: + - Identify whether a VM uses an instance type or a template. - Use the *instance type* method to dynamically add resources to VMs. - Understand the limitations and applications of the legacy method. diff --git a/content/modules/ROOT/pages/06-vm-backup.adoc b/content/modules/ROOT/pages/06-vm-backup.adoc index 688ee07..0e9ad90 100644 --- a/content/modules/ROOT/pages/06-vm-backup.adoc +++ b/content/modules/ROOT/pages/06-vm-backup.adoc @@ -78,7 +78,7 @@ This is a fairly complex task, so let's break it down: A task file beginning with an underscore (`_`) indicates that it is included within another task file. While still within the _tasks_ folder, perform the following steps: -. Create the `snapshot_vms.yml` File: +. Create the `_snapshot_vm.yml` File: + ---- touch _snapshot_vm.yml @@ -373,6 +373,8 @@ One key difference during the creation of the `VirtualMachineRestore` using the `vm_snapshots: ` |=== +WARNING: Replace with the name of your snapthot created previously. + 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.