VM disk size is fixed by the template, when the template is created as 20GB, the VM has it as 20GB. Setting disk offering does not change it at all. It is the ROOT disk we are talking about, for DATA disk, it does work.
On 13 March 2015 at 15:41, Andrija Panic <andrija.pa...@gmail.com> wrote: > I dont expect your partitions and file system will be resized here... > > give us fdisk -l and you should see bigger disk than original. > > Or maybe I'm wrong - some of the developers might confirm...we had > discussion about weather CS will also resize partition and FS - which is I > guess not the case... > > On 13 March 2015 at 16:36, Dan Dong <dongda...@gmail.com> wrote: > > > Hi, All, > > I found when I create a new VM from a template, no matter how I set > disk > > offering, the created new VM always has the same original size. For > > Example, although I specified 100GB of hard disk, > > the actual disk size remains ~20GB, which should come with the template > > itself: > > > > name = Large > > id = a4d52dbd-abea-452f-a8e2-bc13c661f516 > > created = 2014-12-08T09:47:59-0600 > > disksize = 100 > > displayoffering = True > > displaytext = Large Disk, 100 GB > > iscustomized = False > > storagetype = shared > > > > cloudmonkey deploy virtualmachine ... > > diskofferingid=a4d52dbd-abea-452f-a8e2-bc13c661f516 ... > > > > ubuntu@node100GB:~$ df -h > > Filesystem Size Used Avail Use% Mounted on > > /dev/sda1 9.9G 762M 8.7G 8% / > > none 4.0K 0 4.0K 0% /sys/fs/cgroup > > udev 3.9G 4.0K 3.9G 1% /dev > > tmpfs 799M 336K 799M 1% /run > > none 5.0M 0 5.0M 0% /run/lock > > none 3.9G 0 3.9G 0% /run/shm > > none 100M 0 100M 0% /run/user > > > > Is there a way to let the disk offering take effect? > > > > Cheers, > > Dan > > > > > > -- > > Andrija Panić >
