XenCenter 2023.x.x is currently in preview and is not supported for production use. Note that any future references to production support apply only when XenCenter 2023.x.x and XenServer 8 go from preview status to general availability.
You can use XenCenter 2023.x.x to manage your XenServer 8 and Citrix Hypervisor 8.2 CU1 non-production environments. However, to manage your Citrix Hypervisor 8.2 CU1 production environment, use XenCenter 8.2.7. For more information, see the XenCenter 8.2.7 documentation.
You can install XenCenter 8.2.7 and XenCenter 2023.x.x on the same system. Installing XenCenter 2023.x.x does not overwrite your XenCenter 8.2.7 installation.
The settings in the Advanced dialog primarily fine-tune how Workload Balancing applies recommendations when it is running in automated mode.
After Workload Balancing is running for a period, if you do not receive optimal placement recommendations, evaluate your performance thresholds as described in the Workload Balancing documentation. It is critical to set Workload Balancing to the correct thresholds for your environment or its recommendations might not be appropriate.
When WLB runs in automated mode, the frequency of optimization and consolidation recommendations and how soon they are automatically applied is a product of multiple factors. These factors include:
- VM migration interval: How long you specify Workload Balancing waits before applying another optimization recommendation.
- Recommendation count: The number of recommendations Workload Balancing must make before applying a recommendation automatically
- Recommendation severity: The severity level a recommendation must achieve before the optimization is applied automatically
- Optimization aggressiveness: The level of consistency in recommendations (recommended virtual machines to move, destination hosts) Workload Balancing requires before applying recommendations automatically
VM migration interval
You can specify how many minutes WLB waits after the last time a particular VM was moved, before it generates another optimization recommendation that includes that particular VM.
The recommendation interval is designed to prevent Workload Balancing from generating recommendations for artificial reasons (for example, if there was a temporary utilization spike).
When Automation is configured, it is especially important to be careful when modifying the recommendation interval. If an issue occurs that leads to continuous, recurring spikes, increasing the frequency (that is, setting a lower number) can generate many recommendations and, therefore, relocations.
Setting a recommendation interval does not affect how long Workload Balancing waits to factor recently rebalanced servers into recommendations for Start-On Placement, Resume, and Maintenance Mode.
Every two minutes, Workload Balancing checks to see if it can generate recommendations for the pool it is monitoring. When you enable Automation, you can specify the number of times a consistent recommendation must be made before Workload Balancing can automatically apply the recommendation. To do so, you configure a setting known as the Recommendation Count. The Recommendation Count and the Optimization Aggressiveness setting let you fine-tune the automated application of recommendations in your environment.
As described in the overview section, Workload Balancing uses the similarity of recommendations to perform the following checks:
- Vet if the recommendation is truly needed
- Determine if the destination host has stable enough performance over a prolonged period to accept a relocated VM (without needing to move it off the host again shortly).
Workload Balancing uses the Recommendation Count value to determine a recommendation must be repeated before Workload Balancing automatically applies the recommendation.
Workload Balancing uses this setting as follows:
- Every time Workload Balancing generates a recommendation that meets its consistency requirements, as indicated by the Optimization Aggressiveness setting, Workload Balancing increments the Recommendation Count. If the recommendation does not meet the consistency requirements, Workload Balancing can reset the Recommendation Count to zero, depending on the factors described in the Workload Balancing documentation
- When Workload Balancing generates enough consistent recommendations to meet the value for the Recommendation Count, as specified in the Recommendations text box, it automatically applies the recommendation.
If you choose to modify this setting, the value to set varies according to your environment. Consider these scenarios:
- If server loads and activity increase quickly in your environment, you can increase the value for the Recommendation Count. Workload Balancing generates recommendations every two minutes. For example, if you set this interval to
3, then six minutes later Workload Balancing applies the recommendation automatically.
- If server loads and activity increase gradually in your environment, you can decrease the value for the Recommendation Count.
Accepting recommendations uses system resources and affects performance when Workload Balancing is relocating the virtual machines. Increasing the Recommendation Count increases the number of matching recommendations that must occur before Workload Balancing applies the recommendation. This setting encourages Workload Balancing to apply more conservative, stable recommendations and can decrease the potential for spurious virtual machine moves. However, the Recommendation Count is set to a conservative value by default.
Because of the potential impact adjusting this setting might have on your environment, change it with extreme caution. We advise that you test and iteratively change the value, or change it under the guidance of Citrix Technical Support.
All optimization recommendations include a severity rating (Critical, High, Medium, Low) that indicates the importance of the recommendation. Workload Balancing bases this rating on a combination of factors including the configuration options you set, such as:
- Thresholds and metric tunings
- Resources available for the workload
- Resource-usage history.
When you configure Workload Balancing to apply optimization recommendations automatically, you can set the minimum severity level to associate with a recommendation before Workload Balancing automatically applies it.
To provide more assurance when running in automated mode, Workload Balancing has consistency criteria for accepting optimizations automatically to prevent moving VMs due to spikes and anomalies. In automated mode, Workload Balancing does not accept the first recommendation it produces. Instead, Workload Balancing waits to automatically apply a recommendation until a host or VM exhibits consistent behavior over time. The phrase “consistent behavior over time” refers to factors such as whether a host continues to trigger recommendations and whether the same VMs on that host continue to trigger recommendations.
Workload Balancing determines if a behavior is consistent by using criteria for consistency and by having criteria for the number of times the same recommendation is made (that is, the Recommendation Count). You can configure how strictly you want Workload Balancing to apply the consistency criteria using an Optimization Aggressiveness setting.
While Citrix primarily designed the Optimization Aggressiveness setting for demonstration purposes, you can use this setting to control the amount of stability you want in your environment before Workload Balancing applies an optimization recommendation. The most stable setting (Low aggressiveness) is configured by default. In this context, the term “stable” refers to the similarity of the recommended changes over time, as explained throughout this section.
Workload Balancing uses up to four criteria to ascertain consistency. The number of criteria that must be met varies according to the level you set in the Optimization Aggressiveness setting. The lower the level (for example, Low or Medium) the less aggressively Workload Balancing is in accepting a recommendation. In other words, Workload Balancing is stricter about requiring criteria to match (or less cavalier or aggressive) about consistency when the aggressiveness is set to Low.
For example, if the aggressiveness level is set to Low, Workload Balancing requires that each criterion for Low is met the number of times specified in the Recommendations box (where you specify the Recommendation Count value) before automatically applying the recommendation.
For example, if you set the Recommendation Count to
3, Workload Balancing waits until it sees all the criteria for Low are met and repeated in three consecutive recommendations. This behavior helps ensure that the VM actually needs to be moved and that the destination host Workload Balancing recommends has consistently stable resource utilization over a longer period. It reduces the potential for a recently moved virtual machine to be moved off a host due to host performance changes after the move. By default, this setting is set to a conservative setting (Low) to encourage stability.
For information about the criteria for the Low aggressiveness level, see Workload Balancing documentation.
Citrix does not recommend increasing the Optimization Aggressiveness to increase the frequency with which your hosts are being optimized. If you feel that your hosts are not being optimized quickly or frequently enough, try adjusting the Critical thresholds, as described in Changing the Critical Thresholds.
For details about the consistency criteria associated with the different levels of aggressiveness, see the Workload Balancing documentation.
If you find that Workload Balancing is not automatically applying optimization recommendations frequently enough, you might want to increase the aggressiveness setting. However, Citrix strongly recommends reviewing the information in the Workload Balancing documentation before doing so.
To configure virtual machine recommendation intervals
- Select the pool in the Infrastructure view, select the WLB tab, and then select Settings.
- In the left pane, select Advanced.
In the VM Migration Interval section, do one or more of the following:
In Minutes to wait, enter the number of minutes you want Workload Balancing to wait before making another optimization recommendation on a newly rebalanced server.
In the Recommendation Count box, type a value for the number of optimization recommendations you want Workload Balancing to make before it applies an optimization recommendation automatically.
From the Recommendation Severity list, select a minimum severity level before optimizations are applied automatically.
From the Optimization Aggressiveness list, specify how aggressively Workload Balancing automatically applies optimization recommendations.
Pool audit trail granularity
Workload Balancing enables you to specify the amount of data to be collected in the Pool Audit Trail report. This functionality also allows you to search and filter the audit trail logs by specific users, objects, and by time.
Pool Audit Trail Granularity is set to Minimum by default. This option captures limited amount of data for specific users and object types. You can modify the setting at any time based on the level of detail you would require in your report. For example, set the granularity to Medium for a user-friendly report of the audit log. If you require a detailed report, set the option to Maximum.
Setting the Pool Audit Trail Granularity to Maximum can cause the Workload Balancing server to use more disk space and memory. If you choose to set the granularity to Maximum, it is recommended that you carefully monitor the WLB server for disk space, memory usage, and CPU usage. If you think the WLB Server is under resource pressure, you can take one of the following actions:
- Change the granularity setting to Medium or Minimum.
- Consider expanding your WLB server’s memory.
- Consider expanding the size of the hard disk.