Merge pull request #38129 from emarcusRH/1993128

BZ#1993128 add guaranteed memory parameter to RHV Machineset sample YAML

Author: kalexand-rh

modules/machineset-yaml-rhv.adoc

@@ -49,18 +49,19 @@ spec:
             cores: <number_of_cores> <11>
             threads: <number_of_threads> <12>
           memory_mb: <memory_size> <13>
-          os_disk: <14>
-            size_gb: <disk_size> <15>
-          network_interfaces: <16>
-            vnic_profile_id:  <vnic_profile_id> <17>
+          guaranteed_memory_mb:  <memory_size> <14>
+          os_disk: <15>
+            size_gb: <disk_size> <16>
+          network_interfaces: <17>
+            vnic_profile_id:  <vnic_profile_id> <18>
           credentialsSecret:
-            name: ovirt-credentials <18>
+            name: ovirt-credentials <19>
           kind: OvirtMachineProviderSpec
-          type: <workload_type> <19>
-          auto_pinning_policy: <auto_pinning_policy> <20>
-          hugepages: <hugepages> <21>
+          type: <workload_type> <20>
+          auto_pinning_policy: <auto_pinning_policy> <21>
+          hugepages: <hugepages> <22>
           affinityGroupsNames:
-            - compute <22>
+            - compute <23>
           userDataSecret:
             name: worker-user-data
 ----
@@ -102,20 +103,26 @@ If you include this parameter, you do not need to specify the hardware parameter
 
 <13> Optional: Specify the size of a VM's memory in MiB.
 
-<14> Optional: Root disk of the node.
+<14> Optional: Specify the size of a virtual machine's guaranteed memory in MiB. This is the amount of memory that is guaranteed not to be drained by the ballooning mechanism. For more information, see link:https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/administration_guide#memory_ballooning[Memory Ballooning] and link:https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/administration_guide#Cluster_Optimization_Settings_Explained[Optimization Settings Explained].
++
+[NOTE]
+====
+If you are using a version earlier than {rh-virtualization} 4.4.8, see link:https://access.redhat.com/articles/6454811[Guaranteed memory requirements for OpenShift on Red Hat Virtualization clusters].
+====
+<15> Optional: Root disk of the node.
 
-<15> Optional: Specify the size of the bootable disk in GiB.
+<16> Optional: Specify the size of the bootable disk in GiB.
 
-<16> Optional: List of the network interfaces of the VM. If you include this parameter, {product-title} discards all network interfaces from the template and creates new ones.
+<17> Optional: List of the network interfaces of the VM. If you include this parameter, {product-title} discards all network interfaces from the template and creates new ones.
 
-<17> Optional: Specify the vNIC profile ID.
+<18> Optional: Specify the vNIC profile ID.
 
-<18> Specify the name of the secret that holds the {rh-virtualization} credentials.
+<19> Specify the name of the secret that holds the {rh-virtualization} credentials.
 
-<19> Optional: Specify the workload type for which the instance is optimized. This value affects the `{rh-virtualization} VM` parameter. Supported values: `desktop`, `server` (default), `high_performance`. `high_performance` improves performance on the VM, but there are limitations. For example, you cannot access the VM with a graphical console. For more information, see link:https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/virtual_machine_management_guide/index#Configuring_High_Performance_Virtual_Machines_Templates_and_Pools[Configuring High Performance Virtual Machines, Templates, and Pools] in the _Virtual Machine Management Guide_.
-<20> Optional: AutoPinningPolicy defines the policy that automatically sets CPU and NUMA settings, including pinning to the host for this instance. Supported values: `none`, `resize_and_pin`. For more information, see link:https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/virtual_machine_management_guide/index#Setting_NUMA_Nodes[Setting NUMA Nodes] in the _Virtual Machine Management Guide_.
-<21> Optional: Hugepages is the size in KiB for defining hugepages in a VM. Supported values: `2048` or `1048576`. For more information, see link:https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/virtual_machine_management_guide/index#Configuring_Huge_Pages[Configuring Huge Pages] in the _Virtual Machine Management Guide_.
-<22> Optional: A list of affinity group names that should be applied to the VMs. The affinity groups must exist in oVirt.
+<20> Optional: Specify the workload type for which the instance is optimized. This value affects the `{rh-virtualization} VM` parameter. Supported values: `desktop`, `server` (default), `high_performance`. `high_performance` improves performance on the VM, but there are limitations. For example, you cannot access the VM with a graphical console. For more information, see link:https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/virtual_machine_management_guide/index#Configuring_High_Performance_Virtual_Machines_Templates_and_Pools[Configuring High Performance Virtual Machines, Templates, and Pools] in the _Virtual Machine Management Guide_.
+<21> Optional: AutoPinningPolicy defines the policy that automatically sets CPU and NUMA settings, including pinning to the host for this instance. Supported values: `none`, `resize_and_pin`. For more information, see link:https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/virtual_machine_management_guide/index#Setting_NUMA_Nodes[Setting NUMA Nodes] in the _Virtual Machine Management Guide_.
+<22> Optional: Hugepages is the size in KiB for defining hugepages in a VM. Supported values: `2048` or `1048576`. For more information, see link:https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html-single/virtual_machine_management_guide/index#Configuring_Huge_Pages[Configuring Huge Pages] in the _Virtual Machine Management Guide_.
+<23> Optional: A list of affinity group names that should be applied to the VMs. The affinity groups must exist in oVirt.
 
 [NOTE]
 ====