My bad, you are right. The flag just allows the actual host to be included into the possible-hosts list.
2014-11-26 14:34 GMT-03:00 Mike Smith <[email protected]>: > Note that “allow_resize_to_same_host” doesn’t force it to stay on the > same host, it only allows it to happen. It’s still up to the scheduler as > to where it goes. Because we use shared storage at Overstock, we had to > work around this by disabling all the hypervisors except the one it’s on > before doing a resize. > > We also would love to see a way to prevent copying the disk when the > size doesn’t change. It’s annoying when you just want to make a CPU or RAM > change and have to wait for the disk copy. The other downside of resizing > is that it changes your nice, sparsely-provisioned copy-on-write disk image > into a full size image divorced from the qcow source disk. > > Mike Smith > Principal Engineer, Website Systems > Overstock.com > > > > On Nov 26, 2014, at 10:21 AM, Juan José Pavlik Salles <[email protected]> > wrote: > > In Grizzly there's a flag "allow_resize_to_same_host=True" that at least > shouldn't move the instance from one node to another, but it's not exactly > what you want. > > > 2014-11-26 12:30 GMT-03:00 Mathias Brito <[email protected]>: > >> Hello people, >> >> Is there a away to avoid Openstack of making a copy of the VM when >> resizing it? >> >> Mathias >> >> _______________________________________________ >> OpenStack-operators mailing list >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >> >> > > > -- > Pavlik Salles Juan José > Blog - http://viviendolared.blogspot.com > _______________________________________________ > OpenStack-operators mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > ------------------------------ > > CONFIDENTIALITY NOTICE: This message is intended only for the use and > review of the individual or entity to which it is addressed and may contain > information that is privileged and confidential. If the reader of this > message is not the intended recipient, or the employee or agent responsible > for delivering the message solely to the intended recipient, you are hereby > notified that any dissemination, distribution or copying of this > communication is strictly prohibited. If you have received this > communication in error, please notify sender immediately by telephone or > return email. Thank you. > -- Pavlik Salles Juan José Blog - http://viviendolared.blogspot.com
_______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
