Red Hat Bugzilla – Bug 1300405
[RFE] Ability to partition /dev/sda on overcloud nodes
Last modified: 2016-11-25 09:23:28 EST
Description of problem:
We would like to be able to customize the partitioning of /dev/sda when imaging an overcloud node in such a way that we can do the following:
10% of /dev/sda for /var/log
40% of /dev/sda for /home
50% of /dev/sda for /
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Image a node and see 100% allocated for /dev/sda2 on /
Image a node and see 100% allocated for /dev/sda2 on /
Able to customize it
Some company policies requires /var/log to be on a different filesystem. This might as well be the case for /var/lib/mysql
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
Thanks for the RFE, Ironic is the software creates the basic partition layout and it's very opinionated about it, mostly because Ironic just writes to the disk a ready-to-deploy image and also does not touch any files inside the tenant's image (such as /etc/mtab). This is how image based deployed is envisioned which is different than an OS install deployment (such as anaconda) which gives you more flexibility about how to create the partition layout at deployment time.
Now, there are ways of doing it. If you want it at deploy time Ironic is able to deploy "whole disk images", which are an image that contains a partition table already.
Or, this can be achieved in the post-deployment phase, at the first time the node boots the post-deploy scripts are responsible for creating such partitions and configuring the OS to use them (such as modifying /etc/mtab).
Hope that helps,
I had a discussion at summit about this and the thought was that we could approach this with a post-config script, but it would require changing some of how we're doing deployments.
Currently, we're auto-resizing the image when we deploy from is default size of 4GB (I think that's its size) to fill the disk and mount it at /.
We would need to deploy it without that resize, then have postconfig setup the partitioning layout and resize / appropriately.
Do we have progress on this topic?
A customized partitioning layout is one of the important requirements we have at customers for security reasons.
This emphasizes the need for this feature.
Hi! The only way out right now is to use whole disk images, see http://docs.openstack.org/project-install-guide/baremetal/newton/configure-integration.html#create-and-add-images-to-the-image-service for how to create them. Otherwise advanced partitioning is planned (RFE 1381111), but is targeted to Pike (OSP 12).
*** This bug has been marked as a duplicate of bug 1381111 ***