Status: New
Owner: ----
New issue 863 by [email protected]: -B memory=default doesn't act
as expected
http://code.google.com/p/ganeti/issues/detail?id=863
[ganeti 2.10.5 from wheezy-backports]
Here's an instance which is getting minmem/maxmem from cluster-wide
defaults.
# gnt-instance info netdot14.ws.nsrc.org | grep mem
mem_path: default ()
maxmem: default (512)
memory: default (512)
minmem: default (256)
# gnt-instance modify -B memory=384 netdot14.ws.nsrc.org
# gnt-instance info netdot14.ws.nsrc.org | grep mem
mem_path: default ()
maxmem: 384
memory: default (384)
minmem: 384
<< so -B memory=xxx is like -B minmem=xxx,maxmem=xxx >>
# gnt-instance modify -B memory=default netdot14.ws.nsrc.org
# gnt-instance info netdot14.ws.nsrc.org | grep mem
mem_path: default ()
maxmem: 384
memory: default (384)
minmem: 384
Oops! What I expected was minmem and maxmem to be set back to defaults.
Instead it has done nothing.
To get the expected behaviour you have explicitly set minmem and maxmem:
# gnt-instance modify -B minmem=default,maxmem=default netdot14.ws.nsrc.org
# gnt-instance info netdot14.ws.nsrc.org | grep mem
mem_path: default ()
maxmem: default (512)
memory: default (512)
minmem: default (256)
--
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