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
Update Guaranteed memory when updating VM's memory #9882
Conversation
3ea6845
to
e2338af
Compare
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
e2338af
to
e8bfbce
Compare
Checked commit masayag@e8bfbce with ruby 2.2.5, rubocop 0.37.2, and haml-lint 0.16.1 |
@borod108 looks good to me. Please review. |
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. |
@oourfali @blomquisg should this be backported to Darga? |
@chessbyte yes please. |
…configure_vm Update Guaranteed memory when updating VM's memory (cherry picked from commit 7270d7d)
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) |
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