Skip to content

Commit

Permalink
fixing typo
Browse files Browse the repository at this point in the history
  • Loading branch information
rlopez133 committed Dec 10, 2024
1 parent b924c49 commit e677ce3
Showing 1 changed file with 7 additions and 7 deletions.
14 changes: 7 additions & 7 deletions content/modules/ROOT/pages/05-vm-hot-add.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -76,14 +76,14 @@ touch hot_plug.yml
----
+
. Open the `hot_plug.yml` File in Your Favorite Editor and Add the Following Tasks:
+

=== Using the `instance_type` (Recommended)

The `instance_type` method is the recommended approach for hot-plugging
resources into a VM. It ensures consistent and reusable resource configurations
across multiple VMs while leveraging the powerful features of OpenShift
Virtualization.
+

----
- name: Swap Instance Type to add more Resources
redhat.openshift_virtualization.kubevirt_vm:
Expand All @@ -94,20 +94,20 @@ Virtualization.
name: "{{ instance_type }}"
revisionName: ""
----
+

**Explanation of the Task:**
+

- *redhat.openshift_virtualization.kubevirt_vm*: Specifies the module used to manage VMs in OpenShift Virtualization.
- *name*: The name of the VM to which the new resources will be applied.
- *namespace*: The namespace in which the VM resides.
- *state*: Ensures the VM is present and available.
- *instancetype*: Defines the instance type for the VM, allowing you to use pre-configured or custom resource settings.
- *name*: The name of the instance type to be applied.
- *revisionName*: Optionally specifies the exact revision of the instance type, ensuring compatibility with the VM. Typically auto-generated, thus left empty.
+

WARNING: VMs must be created using Instance Types for this task method to work. Otherwise use Legacy method.
+
. After making and saving the changes, ensure you commit and push them to your Gitea repository. For detailed instructions, refer to the Appendix: <<appendix-vscode-commit-push>>.

After making and saving the changes, ensure you commit and push them to your Gitea repository. For detailed instructions, refer to the Appendix: <<appendix-vscode-commit-push>>.

=== Legacy Method: Modifying the Resources via Spec

Expand Down

0 comments on commit e677ce3

Please sign in to comment.