Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1027948

Summary: [RFE] Apply "Enable Memory Balloon Optimization" change right after the confirmation.
Product: Red Hat Enterprise Virtualization Manager Reporter: Amador Pahim <asegundo>
Component: ovirt-engineAssignee: Nobody <nobody>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3.3.0CC: acathrow, iheim, lpeer, lsvaty, Rhev-m-bugs, sherold, yeylon
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: 3.4.0   
Hardware: All   
OS: Linux   
Whiteboard: sla
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-13 17:58:00 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: 1020228    
Attachments:
Description Flags
Sync MoM Policy none

Description Amador Pahim 2013-11-07 13:32:11 UTC 
"Enable Memory Balloon Optimization" is a cluster level configuration and it is applied only in next Host change to "Up" state. As the change for Up state isn't something regular in a stable datacenter, users need to change Hosts to maintenance and then back to Up again, migrating running VMs during the process, to have the change in balloon configuration applied.
There is an emergency option in vdsClient command which can be used to disable/enable balloon in each host, but vdsClient is not supported and using this method can be painful in large deployments.

Please apply changes in  "Enable Memory Balloon Optimization" option as soon as users click in "OK" on Cluster/Edit/Optimization window.
Comment 1 Scott Herold 2014-01-13 17:57:10 UTC 
Created attachment 849511 [details]
Sync MoM Policy
Comment 2 Scott Herold 2014-01-13 17:58:00 UTC 
There is a workaround in RHEV 3.3 that enables an admin to Synchronize the MoM Policy on a Host by Host basis without the need to place the host into maintenance mode, migrate VMs, remove from maintenance, then migrate VMs again.  See attached screenshot for details.

We will not be moving this to a fully automated policy due to potential overhead and performance degradation from a Disk I/O and other resource perspective.