Hi I assume this is not for OS images (the one that runs cloudinit)... For other disks you can take a look at the volatile disk feature. [1]
Volatile disks are created on the target host on-the-fly when the VM is deployed. Note that these disks are volatile and can not be saved. Its primary use is for scratch partitions. [1] http://opennebula.org/documentation:rel3.6:template#volatile_disks Cheers Ruben On Mon, Sep 24, 2012 at 1:01 PM, Ricardo Duarte <[email protected]> wrote: > Hi there, > > I had a look at cloud-init, and also other cloud softwares, and this is > what they do: > > - The images themselves are very small in size > - The size of the root disk is selected when launching a instance, and as > so, it can be part of the service offering (ex.: small 8GB, medium 10GB, > etc). > - The virtual disk is grown to the size selected when launching the > instance. Partition size inside is kept. > - Cloud-init, inside the guest, resizes the partition on first boot, by > using resize2fs. This is just a small command, so it could be done without > cloud-init quite easily > > Is this currently possible to do with existing OpenNebula functionality? > > Thanks, > Ricardo > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > > -- Ruben S. Montero, PhD Project co-Lead and Chief Architect OpenNebula - The Open Source Solution for Data Center Virtualization www.OpenNebula.org | [email protected] | @OpenNebula
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
