Ramdisk for overcloud image shall include lvm, crypt drivers , or add the possibility to include extra ones
Bug #1655681 reported by
Yolanda Robla
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Undecided
|
Yolanda Robla |
Bug Description
When testing with whole disk images (to start using volumes and encryption on images), I had to rebuild the ramkdisk of the overcloud-full image to add modules that are quite generic, such as lvm or crypt.
Another use case that I found, is the need of having iscsi as well.
The process for building the image shall include the most used modules , and also it shall provide a mechanism for people rebuilding the images to easily customize it , to include the modules they need on demand.
Changed in tripleo: | |
assignee: | nobody → Yolanda Robla (yolanda.robla) |
status: | New → In Progress |
Changed in tripleo: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
I did some testing with diskimage-builder, to start using dracut instead of busybox, as this element claims. I saw that lvm and crypt modules were properly added to the ramdisk (had to install cryptsetup and lvm2 packages as well) . But the problem i see with that, is that this elements generates an independent ramdisk file, instead of updating the ramdisk used in the /boot directory.
We cannot use it in TripleO like that, because we extract initrd and vmlinuz from boot directory (or use whole disk images, just consuming the qcow2) . So that extra generated file is not consumed by TripleO, and the modules are not loaded.