openstack: compute node image free space and deployment

Various components (such as rabbitmq) have checks for minimum amounts
of free space on a image. If those checks fail, the service exits in
a hard to debug manner. To ensure that these services run, and meet
typical usage scenarios, we increase the free space in the image to 3G.

Finally, we inherit openstack-image-base, to trigger simple rootfs
configuration and deployment.

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>

1 files changed, 4 insertions, 1 deletions

diff --git a/meta-openstack/recipes-extended/images/openstack-image-compute.bb b/meta-openstack/recipes-extended/images/openstack-image-compute.bb
index 632b21b..2ddce67 100644
--- a/meta-openstack/recipes-extended/images/openstack-image-compute.bb
+++ b/meta-openstack/recipes-extended/images/openstack-image-compute.bb
@@ -10,7 +10,10 @@ IMAGE_INSTALL = " \
 IMAGE_FEATURES += "ssh-server-openssh"
 
 inherit core-image
+inherit openstack-base
 
-#IMAGE_ROOTFS_EXTRA_SPACE = "41943040"
+# Ensure extra space for guest images, and rabbit MQ has a hard coded
+# check for 2G of free space, so we use 3G as a starting point.
+IMAGE_ROOTFS_EXTRA_SPACE = "3000000"
 
 ROOTFS_POSTPROCESS_COMMAND += "remove_packaging_data_files ; "