Change in ovirt-engine[master]: core: set max memory on the fly for existing vm pools

[Code Review]

>From Arik Hadas <ahadas at redhat.com>:

Arik Hadas has submitted this change and it was merged.

Change subject: core: set max memory on the fly for existing vm pools
......................................................................


core: set max memory on the fly for existing vm pools

Existing VM pools that are missing the setting of max memory cannot be
updated (since the default value of max memory is 0). This patch
solves this by setting the max memory to the maximum value allowed for
the pool (according to its operating system) when editing such a pool.

Change-Id: Ic2939483f48609d8ede8794c04f982285409365c
Bug-Url: https://bugzilla.redhat.com/1408577
Signed-off-by: Arik Hadas <ahadas at redhat.com>
---
M backend/manager/modules/bll/src/main/java/org/ovirt/engine/core/bll/UpdateVmPoolCommand.java
1 file changed, 12 insertions(+), 0 deletions(-)

Approvals:
  Shahar Havivi: Looks good to me, approved
  Jenkins CI: Passed CI tests
  Arik Hadas: Verified



-- 
To view, visit https://gerrit.ovirt.org/69229
To unsubscribe, visit https://gerrit.ovirt.org/settings

Gerrit-MessageType: merged
Gerrit-Change-Id: Ic2939483f48609d8ede8794c04f982285409365c
Gerrit-PatchSet: 2
Gerrit-Project: ovirt-engine
Gerrit-Branch: master
Gerrit-Owner: Arik Hadas <ahadas at redhat.com>
Gerrit-Reviewer: Arik Hadas <ahadas at redhat.com>
Gerrit-Reviewer: Jenkins CI
Gerrit-Reviewer: Shahar Havivi <shavivi at redhat.com>
Gerrit-Reviewer: gerrit-hooks <automation at ovirt.org>