Bug 1090576

Summary: Cluster -> Memory Optimization screen requires cleaner language
Product: Red Hat Enterprise Virtualization Manager Reporter: Scott Herold <sherold>
Component: ovirt-engine-webadmin-portalAssignee: Martin Sivák <msivak>
Status: CLOSED CURRENTRELEASE QA Contact: Michael Burman <mburman>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.4.0CC: dfediuck, ecohen, gklein, iheim, lpeer, mavital, mburman, rbalakri, Rhev-m-bugs, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: sla
Fixed In Version: org.ovirt.engine-root-3.5.0-14 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 17:16:25 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:
Bug Depends On:    
Bug Blocks: 1156162    
Attachments:
Description Flags
Cluster Optimization in RHEV 3.4 none

Description Scott Herold 2014-04-23 16:17:56 UTC 
Created attachment 889006 [details]
Cluster Optimization in RHEV 3.4

Description of problem:

Enhancements in 3.4 to Enable/Disable KSM have introduced confusion regarding terminology being used in the Cluster -> Optimization screen.  Historically, we have had settings for "Memory Optimization" which provide options of None, For Server Load, and For Desktop Load", which apply various "memory page sharing" values.  I believe "memory page sharing" is an improper term, as to me, and several customers, relate that to VMware's feature of "Transparent Page Sharing", which is equivilent to our KSM.  Now that we have added the option to Enable/Disable KSM, this becomes confusing, as it seems like we can modify the same concept in two different locations.


How reproducible:
100% in RHEV 3.4

Steps to Reproduce:
1.  Create or Edit a Cluster
2.  Click on the "Optimization" tab


Actual results:
As defined above

Expected results:
We should look to modify the terminology of the Memory Optimization setting to more accurately reflect what it is controlling, which, as far as I can tell, is Consumed Memory Over-Commit, or how much we can over-commit a cluster or host in the cluster based on the idea that it is possible to Allocate more memory to VMs that exist in the source host.

Memory Page Sharing should not be used, as it causes confusion agains what KSM actually does... which is physical page sharing.

Additional info:
See BZ 1072030 for how this is already causing confusion in RHEV 3.3 without the KSM Control option
Comment 1 Eyal Edri 2014-10-07 07:13:03 UTC 
this bug status was moved to MODIFIED before engine vt5 was built,
hence moving to on_qa, if this was mistake and the fix isn't in,
please contact rhev-integ
Comment 2 Michael Burman 2014-10-22 13:38:51 UTC 
Verified on - 3.5.0-0.15.beta.el6ev
Comment 3 Eyal Edri 2015-02-17 17:16:25 UTC 
rhev 3.5.0 was released. closing.