On Thu, Oct 04, 2012 at 12:31:03PM +0100, Nux! wrote:
On 04.10.2012 11:55, Stephen Harris wrote:
On Thu, Oct 04, 2012 at 11:27:40AM +0100, Nux! wrote:
http://li.nux.ro/download/openstack/ks/centos6_x86_64_minimal.ks
Suggestions on how to improve it welcome.
Why do you need to do the "extend filesystem" stuff? Or is this a mis-feature of openstack that you're having to work around?
Stephen,
This ks will generate a template to be used to deploy virtual machine on openstack (well, can be used anywhere kvm+virtio) and as such the template should be able to expand itself on the new virtual disk (it will basically be dd-ed to a new, larger file to be used for a VM). Indeed it's a "misfeature" of openstack as they could have used virt-resize to do all this..
The kickstart entry, as defined, should define a partition of max size 'cos you only have one --grow value part / --fstype=ext4 --asprimary --grow --size=1
In my tests the partition always fills the disk allocated to it, so there's no need to resize after install.
# fdisk -l
Disk /dev/vda: 4294 MB, 4294967296 bytes 16 heads, 63 sectors/track, 8322 cylinders Units = cylinders of 1008 * 512 = 516096 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000666f1
Device Boot Start End Blocks Id System /dev/vda1 * 3 206 102400 83 Linux Partition 1 does not end on cylinder boundary. /dev/vda2 206 1246 524288 82 Linux swap / Solaris Partition 2 does not end on cylinder boundary. /dev/vda3 1246 8323 3566592 83 Linux Partition 3 does not end on cylinder boundary.
Under what circumstances is a resize needed?