Bug 891350 - Use virt-resize on disk images instead of just manually extending the raw disk and using resize2fs directly
Summary: Use virt-resize on disk images instead of just manually extending the raw dis...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 2.0 (Folsom)
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: beta
: ---
Assignee: Pádraig Brady
QA Contact: Jaroslav Henner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-02 16:51 UTC by Perry Myers
Modified: 2016-01-04 14:42 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-18 16:50:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Perry Myers 2013-01-02 16:51:56 UTC
Description of problem:
Currently Nova extends only raw disk images and can on deal with resizing partitions of type ext2/3/4 (or unpartitioned space).

If we utilize virt-resize from libguestfs we can handle resizing VGs/LVM and other types of filesystems.

virt-resize also does better error checking to make sure the operation succeeded.

Comment 1 seth vidal 2013-02-22 06:43:34 UTC
looking in folsom - it seems like qcow2 and raw images get extended - but unless we have an initramfs doing a growroot then it won't work w/o a reboot of the instance.

Comment 2 Pádraig Brady 2013-04-02 16:45:24 UTC
Upstream are leaning towards (newer) cloud-init doing this within the image,
rather than externally with virt-resize.

Comment 4 Pádraig Brady 2013-06-18 16:50:51 UTC
For more concrete details on using cloud-utils to auto resize from within the guest on boot, see:
http://lists.openstack.org/pipermail/openstack-operators/2013-June/003131.html


Note You need to log in before you can comment on or make changes to this bug.