You can configure the following cluster automation settings listed in this section. What to read next Hardware Version for VFIO PCI DriverVMware Tanzu Kubernetes Grid deploys a template with the virtual machine hardware version 13 by default. If your network function uses the VFIO PCI driver, it requires the hardware version 14 for an Intel-based setup and version 18 for an AMD-based setup. VMware Telco Cloud Automation updates this information to the VMConfig Operator according to the firmware. Currently, VMware Telco Cloud Automation updates the hardware version as 14 assuming that the setup is Intel-based. If you are using an AMD-based setup, use the following API to update the global settings to send the hardware version as 18. Enable Virtual Machine Placement in vSphere DRSDuring customization, the VMConfig plug-in tries to fit the virtual machines to the correct NUMA nodes of the ESXi server based on its SR-IOV, Passthrough, and Pinning specifications. To disable the virtual machine placement operation by the plug-in and enable the virtual machine placement by vSphere DRS, configure the following settings on the node pool before instantiating the network function. Update CPU and Memory Reservation During Virtual Machine PlacementDuring customization, VMware Telco Cloud Automation reserves 2 physical cores (4 Hyper Threads) and 512 MB of memory for the ESXi host while performing the CPU or memory pinning operation on the virtual machines. You can update this default configuration and update the VMware ESXi host information before instantiating your network function. Update Wait Timeout for Customization TasksVMware Telco Cloud Automations posts the customizations to VMConfig and polls for the customization tasks to complete. By default, VMware Telco Cloud Automation waits for 30 minutes before polling at 30-second intervals if the customization is not successful. You can configure this default behavior using the following APIs. Parent topic: Global Settings for Cluster Automation
