----- Original Message ----- > From: "seth vidal" <skvidal@xxxxxxxxxxxxxxxxx> > To: "Fedora Cloud SIG" <cloud@xxxxxxxxxxxxxxxxxxxxxxx> > Cc: afazekas@xxxxxxxxxx > Sent: Friday, May 3, 2013 4:20:10 PM > Subject: Re: root filesystem resizeing at boot time > > On Fri, 3 May 2013 09:24:09 -0400 (EDT) > Attila Fazekas <afazekas@xxxxxxxxxx> wrote: > > > Hi All, > > > > Openstack is able to boot the same image with different disk sizes. > > The instance's disk size is depends on the selected flavor type. > > With the default flavor types you can have 20Gib(m1.small), 40Gib > > (m1.medium), 80Gib (m1.large), 160 GiB (m1.xlarge) Disk sizes. > > > > I am looking for an OpenStack friendly Fedora image which is able to > > utilize all space on the first disk(vda), without any additional > > manual steps. The file system should be ready for use before I login > > to the instance. > > > > According to this presentation > > http://www.slideshare.net/openstack/os-summit-portlandimages, the > > best time for resizing the file systems is at the initrd time. > > > > All Fedora jeos images I tried so far just uses maximum 10 GiB even > > on a 160 GiB disk after the first boot. I would like to use the same > > image for all disk sizes. > > > > Do you know about a working auto-resize capable Fedora Image ? > > > > There is a package called cloud-utils-initramfs which does this in the > initramfs. > https://bugzilla.redhat.com/show_bug.cgi?id=916087 > > it should be trickling in and I hope will be into the imgs soon. > > does this help? Probably it will help. Cool. Thank you. > -sv > > > _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud