maxmem setting for pv xen domu
Heiko Baumann
is it possible to set maxmem for a xen pv domu via ganeti? without it,
its not possible to change mem for a running domu to more than the
initial mem="" setting. i havent found anything in the docs.
regards
heiko
Iustin Pop
It is not, as currently it "breaks" Ganeti if you use DRBD instances.
But otherwise it should be fine, could you please file a request for
this?
thanks,
iustin
Heiko Baumann
what exactly does "break" mean? does this affect the N+1 mem
calculation stuff?
a few minutes ago i've hacked constrants.py and hv_xen.py a little bit
to allow setting of maxmem via gnt-cluster modify -B maxmem="123" and
gnt-instance modify... and it works. :) however i guess this is just a
ugly hack because of my !coding skills ;)
is this the right place for the request? ->
http://code.google.com/p/ganeti/issues/list
regards
heiko
On Wed, 2 Mar 2011 15:55:06 +0100, Iustin Pop <ius...@google.com>
wrote:
Michael Hanselmann
> is this the right place for the request? ->
> http://code.google.com/p/ganeti/issues/list
Yes, it is.
Thanks,
Michael
Iustin Pop
> thanks for the fast reply.
>
> what exactly does "break" mean? does this affect the N+1 mem
> calculation stuff?
Yep. It's not real breakage, hence the quotes. Also, Ganeti won't be
able to check other things (placement using the IAllocator framework
will not be correct, but if you don't use it it's OK).
> a few minutes ago i've hacked constrants.py and hv_xen.py a little
> bit to allow setting of maxmem via gnt-cluster modify -B
> maxmem="123" and gnt-instance modify... and it works. :) however i
> guess this is just a ugly hack because of my !coding skills ;)
If you fill in the contributor license agreement (see the wiki for
Developer Guidelines; sorry for this requirement) you can send the patch
for inclusion - it doesn't have to be perfect, so don't worry!
> is this the right place for the request? ->
> http://code.google.com/p/ganeti/issues/list
Yep!
thanks,
iustin