Bug 999539

Summary: scheduling policy: please rename the predefined Functions / Weights Modules / Factors
Product: [oVirt] ovirt-engine Reporter: Einav Cohen <ecohen>
Component: Frontend.WebAdminAssignee: Doron Fediuck <dfediuck>
Status: CLOSED WONTFIX QA Contact: Artyom <alukiano>
Severity: medium Docs Contact:
Priority: unspecified    
Version: ---CC: bugs, istein, mavital, mgoldboi, rbalakri, yeylon, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-3.4.0-alpha1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-06 11:39:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screen-shot: New/Edit Policy Dialog none

Description Einav Cohen 2013-08-21 13:59:28 UTC 
Description of problem:

The predefined Functions / Weights Modules / Factors in the scheduling policy context are a bit confusing - they seem to describe a policy, rather than a weight function. 
Moreover, their names are currently identical to the load balancing Parameters / Properties, so it creates even more confusion.
Having said that, we don't want to change the names too much, in order to be user-friendly to those who are familiar with the old policy configuration process.

My suggestion:

Rename "PowerSaving" to "OptimalForPowerSaving"
Rename "EvenDistribution" to "OptimalForEvenDistribution"
Comment 1 Einav Cohen 2013-08-21 14:03:51 UTC 
Created attachment 788891 [details]
screen-shot: New/Edit Policy Dialog
Comment 3 Sandro Bonazzola 2014-01-13 13:57:00 UTC 
oVirt 3.4.0 alpha has been released including the fix for this issue.
Comment 4 Artyom 2014-02-13 09:41:49 UTC 
How I understand you needed rename just weight modules and not Load Balancer:
weight -> OptimalForPowerSaving, LoadBalancer -> PowerSaving
Now when you change names of two of them to OptimalForPowerSaving you stay with the same confusion.
Checked on ovirt-engine-3.4.0-0.5.beta1.el6.noarch
Comment 5 Sandro Bonazzola 2014-03-04 09:19:19 UTC 
This is an automated message.
Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.
Comment 6 Sandro Bonazzola 2014-05-08 13:55:43 UTC 
This is an automated message.

oVirt 3.4.1 has been released.
This issue has been retargeted to 3.5.0 since it has not been marked as high priority or severity issue, please retarget if needed.
Comment 7 Red Hat Bugzilla Rules Engine 2015-10-19 11:02:14 UTC 
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 9 Doron Fediuck 2016-04-06 11:39:17 UTC 
Closing old issues based on capacity.
Please re-open only if relevant and needed.