On Tue, Jun 17, 2014 at 04:32:36PM +0100, Pádraig Brady wrote: > On 06/13/2014 02:22 PM, Day, Phil wrote: > > I guess the question I’m really asking here is: “Since we know resize down > > won’t work in all cases, > > and the failure if it does occur will be hard for the user to detect, > > should we just block it at the API layer and be consistent across all > > Hypervisors ?” > > +1 > > There is an existing libvirt blueprint: > https://blueprints.launchpad.net/nova/+spec/libvirt-resize-disk-down > which I've never been in favor of: > https://bugs.launchpad.net/nova/+bug/1270238/comments/1
All of the functionality around resizing VMs to match a different flavour seem to be a recipe for unleashing a torrent of unfixable bugs, whether resizing disks, adding CPUs, RAM or any other aspect. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev