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.

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

Update Guaranteed memory when updating VM's memory #9882

Merged

Conversation

masayag
Copy link
Contributor

@masayag masayag commented Jul 18, 2016

There is a coupling between the Guaranteed memory to the VM memory:
Guaranteed cannot exceed the VM memory, and the VM memory cannot
be set to a lower value than the guaranteed memory. Therefore the
order of updating the vm's memory is considered at update.

http://bugzilla.redhat.com/1356193

@masayag masayag force-pushed the support_decreasing_memory_in_reconfigure_vm branch 2 times, most recently from 3ea6845 to e2338af Compare July 19, 2016 06:37
There is a coupling between the Guaranteed memory to the VM memory:
Guaranteed cannot exceed the VM memory, and the VM memory cannot
be set to a lower value than the guaranteed memory. Therefore the
order of updating the vm's memory is considered at update.

http://bugzilla.redhat.com/1356193
@masayag masayag force-pushed the support_decreasing_memory_in_reconfigure_vm branch from e2338af to e8bfbce Compare July 19, 2016 08:36
@miq-bot
Copy link
Member

miq-bot commented Jul 19, 2016

Checked commit masayag@e8bfbce with ruby 2.2.5, rubocop 0.37.2, and haml-lint 0.16.1
2 files checked, 0 offenses detected
Everything looks good. 🏆

@oourfali
Copy link

@borod108 looks good to me. Please review.

@borod108
Copy link

borod108 commented Jul 19, 2016

Looks good to me according to the current style.

Maybe it would be nice to change the "memory = value" to "update_memory_to(value)" some day because it is not obvious that "rhev_vm.memory = value" actually updates the remote object, therefore it looks a bit confusing. But this is not for this PR. In this PR it is nicely explained in the comment which is the best option in my opinion.

@blomquisg blomquisg merged commit 7270d7d into ManageIQ:master Jul 28, 2016
@blomquisg blomquisg added this to the Sprint 44 Ending Aug 1, 2016 milestone Jul 28, 2016
@chessbyte
Copy link
Member

@oourfali @blomquisg should this be backported to Darga?

@oourfali
Copy link

@chessbyte yes please.

chessbyte pushed a commit that referenced this pull request Aug 30, 2016
…configure_vm

Update Guaranteed memory when updating VM's memory
(cherry picked from commit 7270d7d)
@chessbyte
Copy link
Member

Darga Backport details:

$ git log
commit 4322408030cec7c833292158c99b690b83dec1a7
Author: Greg Blomquist <blomquisg@gmail.com>
Date:   Thu Jul 28 13:20:54 2016 -0400

    Merge pull request #9882 from masayag/support_decreasing_memory_in_reconfigure_vm

    Update Guaranteed memory when updating VM's memory
    (cherry picked from commit 7270d7d4036ebdeff94354ec40d7457940c26009)

@masayag masayag deleted the support_decreasing_memory_in_reconfigure_vm branch June 27, 2018 20:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants