Comment #11 on issue 695 by [email protected]: support kvm
run-time memory changes (ballooning)
http://code.google.com/p/ganeti/issues/detail?id=695
I think it is confusing that gnt-instance returns any backend "memory"
setting, and this was supposed to have been removed in ganeti 2.7:
[lib/client/gnt_instance.py]
# deprecated "memory" value, kept for one version for compatibility
# TODO(ganeti 2.7) remove.
be_actual = copy.deepcopy(instance["be_actual"])
be_actual["memory"] = be_actual[constants.BE_MAXMEM]
As you can see, the "memory" value returned is just a copy of the "maxmem"
value, which is not useful. Maybe now is the time to remove it?
Related: issue #850. The "memory" setting has already been removed from
config.ini when exporting an instance, leaving just "minmem" and "maxmem".
You *can* specify -B memory=xxx when modifying an instance, but as far as I
can see, it just sets -B minmem=xxx,maxmem=xxx
Other comments: it sounds from this ticket that what's wanted is a setting
for "the amount of memory to allocate on instance startup" - but how would
that interact with the current algorithm that picks a value between minmem
and maxmem? Does it essentially become an override for maxmem for all
automatic ballooning operations?
Finally, I guess it would also be useful to have a way to see the *actual*
memory allocated to the VM right now. This is similar to ticket #854, where
the poster wants to be able to see the run-time values of parameters set in
a one-shot way using gnt-instance start [-H/-B], which is different to the
startup values stored against the instance.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
