I wonder if your disk image has a partition set to 20GB. Your instance may get a bigger disk, but the partition is still set to 20G. Try running an “fdisk -l” or something inside the VM to see if the disk itself is actually bigger than the partition you are seeing
There are cloud init scripts that resize these for you, or Kilo has an provisioning-time option to make the disk automatically resize Mike Smith Principal Engineer / Cloud Team Lead Overstock.com<http://Overstock.com> On Sep 24, 2015, at 12:44 PM, Nasir Mahmood <nasir.mahm...@gmail.com<mailto:nasir.mahm...@gmail.com>> wrote: Hi, My openstack KILO version installation is almost production level now, with 3 compute nodes. On a recently added compute node with plenty of disk space, I have tried to add a new flavor with 8 cores, 16 gb ram and 500 gb hard disk space. The instance spins up, but with 20 gb of disk space only, as it happens on others Compute nodes. This new Compute node has a single partition of 3 tb on an hw raid . Any idea.. Regards, Nasir _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org<mailto:openstack@lists.openstack.org> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
