Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

frontend: Update scheduling policy weights modules tooltip #534

Merged
merged 1 commit into from
Jul 20, 2022
Merged

frontend: Update scheduling policy weights modules tooltip #534

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .../webadmin/src/main/resources/org/ovirt/engine/ui/webadmin/ApplicationConstants.properties
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -251,7 +251,7 @@ clusterPolicyPropertiesLabel=Properties
clusterPolicySchedulePolicyPanelTitle=Scheduling Policy
clusterPolicySelectPolicyLabel=Select Policy
clusterPolicySubTabLabel=Policy
clusterPolicyWeightFunctionInfo=Weights represent soft constraints for running a VM. Note\: in a weighting system, lower score is considered better. So a host with the lowest score (weight) is the one the scheduler will choose. Each weight module scores any given host based on an optimization logic the module implements. For example, if we want to optimize for CPU load, the module will score each host based on its known CPU load. Weight modules scores are being summed, so it is possible to have more than one weight module. The way to prioritize modules is by increasing / decreasing a factor.
clusterPolicyWeightFunctionInfo=Weights represent soft constraints for running a VM. Note\: in a weighting system, lower score is considered better. So a host with the lowest score (weight) is the one the scheduler will choose. Each weight module scores any given host based on an optimization logic the module implements. For example, if we want to optimize for CPU load, the module will score each host based on its known CPU load. It is possible to have more than one weight module, then host scores are ranked in each of the modules, the ranks of the modules are summed up and the host with the best accumulated rank is selected. The way to prioritize modules is by increasing / decreasing a factor.
clusterPopupArchitectureLabel=CPU Architecture
clusterPopupBandwidthLabel=Bandwidth
clusterPopupBiosTypeLabel=Chipset/Firmware Type
Expand Down