Bug 1477921 - [RFE] diskimage-builder shall support creating images with volumes
[RFE] diskimage-builder shall support creating images with volumes
Product: Red Hat OpenStack
Classification: Red Hat
Component: diskimage-builder (Show other bugs)
13.0 (Queens)
Unspecified Unspecified
medium Severity medium
: Upstream M1
: 13.0 (Queens)
Assigned To: Yolanda Robla
: FutureFeature, Triaged
Depends On: 1563774
  Show dependency treegraph
Reported: 2017-08-03 04:43 EDT by Yolanda Robla
Modified: 2018-04-17 18:15 EDT (History)
9 users (show)

See Also:
Fixed In Version: diskimage-builder-2.10.2-0.20180123051718.7e7186a.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
OpenStack gerrit 472065 None master: MERGED diskimage-builder: LVM support for dib-block-device (Ibd624d9f95ee68b20a15891f639ddd5b3188cdf9) 2018-02-07 09:04 EST

  None (edit)
Description Yolanda Robla 2017-08-03 04:43:05 EDT
Description of problem:

In order to create security hardened images, it was important to have different directories on different filesystems. On Pike, support for partitions was added. Now we are willing to create volumes on top of them, for Queens.
Using volumes instead of partitions, will give us more flexibility in terms of sizing and scaling.
Comment 3 Ramon Acedo 2017-10-31 06:25:00 EDT
Ideally we should verify if LVM can be configured with PVs in multiple local disks instead of just partitions in one disk.
Comment 5 Yolanda Robla 2017-11-09 11:55:20 EST
I tested creating the image with multiple disks in diskimage-builder and that's not supported. If you'd like to work with multiple PVs in multiple disks, this needs to be done manually. The current volume creation in diskimage-builder/tripleo is just thought for a single disk
Comment 13 mlammon 2018-04-06 12:51:30 EDT
This was tested with osp13 latest.  Looking at one of nodes (controller) which was deployed using whole disk image. 


We can see the volumes
[root@controller-0 files]# lsblk
NAME                                          MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
vda                                           252:0    0   40G  0 disk
├─vda1                                        252:1    0 21.4G  0 part
│ ├─vg-lv_root                                253:0    0    6G  0 lvm  /
│ ├─vg-lv_tmp                                 253:1    0  876M  0 lvm  /tmp
│ ├─vg-lv_var                                 253:2    0  8.6G  0 lvm  /var
│ ├─vg-lv_log                                 253:3    0  4.9G  0 lvm  /var/log
│ ├─vg-lv_audit                               253:4    0  876M  0 lvm  /var/log/audit
│ └─vg-lv_home                                253:5    0  216M  0 lvm  /home
└─vda2                                        252:2    0   64M  0 part
loop2                                           7:2    0   16G  0 loop
├─cinder--volumes-cinder--volumes--pool_tmeta 253:6    0   16M  0 lvm
│ └─cinder--volumes-cinder--volumes--pool     253:8    0 15.2G  0 lvm
└─cinder--volumes-cinder--volumes--pool_tdata 253:7    0 15.2G  0 lvm
  └─cinder--volumes-cinder--volumes--pool     253:8    0 15.2G  0 lvm
Comment 15 Bob Fournier 2018-04-16 11:38:00 EDT
Mike - I believe fix for 1563774 is available in the latest puddle.
Comment 16 mlammon 2018-04-17 18:15:55 EDT
This can now be moved to verified with bz 1563774 being verified today in osp 13 2018-04-13.1

Note You need to log in before you can comment on or make changes to this bug.