Hi,
I'm not sure. We have never hit this problem with DIB-built images before. I know that TripleO uses an even larger image than one we publish on tarballs.o.o.
Dmitry
On Wed, May 12, 2021 at 8:10 PM Vuk Gojnic vuk.gojnic@gmail.com wrote:
Hi Dmitry,
Thanks for additional tipps. When investigating the initrd I have noticed that the most of the space goes on firmware and modules/drivers. If we notice something not working with TinyIPA we can probably cherry-pick the modules that we need and leave everything else out and that way get smaller image.
I have another question though - do you know how could we make Kernel/Grub accept to boot large initrd? How are other folks doing it? I assume not everybody is just using TinyIPA for production...
Tnx!
Vuk
On Wed, May 12, 2021 at 5:36 PM Dmitry Tantsur dtantsur@redhat.com wrote:
I'm glad that it worked for you!
Before others follow your advice: the difference in size in DIB builds
and tinyIPA is mostly because of firmware and kernel modules. If tinyIPA does not work for you or behaves in a weird way (no disks detected, some NICs not detected), then you're stuck with DIB builds.
Vuk, there is one more option you could exercise. IPA-builder supports
an --lzma flag to pack the initramfs with a more efficient algorithm: https://opendev.org/openstack/ironic-python-agent-builder/src/branch/master/... .
Dmitry