openstack team mailing list archive

[Owen Synge <osynge@xxxxxxxxxxxxxx>]

Dear Davide,

Please dont use LVM in cloud images unless you want to encrypt the
content and then please use a very unique volume group name. Reason follows.

If you want to allow the mangement domain to mount your partitons and
make edits then the management domain must first use something like
kpartx which allows you to present virtual disk partitons. These virtual
disk partitions can then be mounted if its a normal file system, but if
you used LVM, the partitions must be scanned by your system and added to
your systems volume group space, if these volume groups names clash with
volume groups being used on the management domain their can be problems
for the management domain to release the resources.

I should report this issue to LVM one day and see if they think it could
be fixed some how. I have found xfs to be very good, and but for a
virgin project /I think//Btrfs/ might be worth investigation what it
brings to the table as it should be available without special measures
in all future operating systems.

Regards

Owen



On 08/02/13 09:55, Davide Guerri wrote:
> Hi all,
> I'm preparing some cloud images for the major Linux distributions and I'd like they to grow their root fs on boot (to use all the available space).
>
> Ubuntu cloud images (http://cloud-images.ubuntu.com) use initramfs-growroot but installing it (and maintaining it across kernel upgrade) could be tricky -at least for me- on redhat derived like centos or fedora. 
>
> So my question is: what are pros and cons of using an ext3/4 root-fs and initramfs-growroot, or LVM (with a custom script that runs on first boot)?
>
> Thanks,
>  Davide.
>  
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp