sig_cloud/diskimage-builder
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
c41a2b7f84
diskimage-builder/diskimage_builder/elements/yum-minimal/package-installs.yaml

20 lines
493 B
YAML
Raw Normal View History

Add "audit"package to yum-minimal Kernels are built with auditing support, and without the audit deamon logs bubble up to spam the console and /var/log/messages. This package contains the audit daemon that catches these messages. Change-Id: Ie3e216bab33b27f2d67a9379ddc3e89d66449251
2016-08-08 07:54:20 +00:00
audit:
Add a yum-minimal element that just uses yum The centos-minimal approach of using rinse does not, it turns out, work on centos. That's a bummer. It's also rather heavyweight. Instead, with minor machinations, we can just use yum itself pointed at a chroot. Also adding fedora-minimal element which creates a fedora image using the new yum-minimal approach. Co-Authored-By: Gregory Haynes <greg@greghaynes.net> Change-Id: I026fd9d323e786dae5bb67824c6501067e1ceaa3
2015-03-22 14:04:46 +00:00
dracut:
Install dracut-generic-config package dracut has a "hostonly" mode where it builds an initramfs that is suitable for booting the system it is building on. This is on by default, but obviously in our nested multi-platform chroot situation this is fraught with danger. As highlighted by [1] our builds were inadvertently turning off "hostonly" mode when the mountpoints in the chroot were not found. The CentOS 7.3 behaviour change broke this and we ended up with an initramfs with no file-system modules. Iaf2a1e8470f642bfaaaad3f9b7f26cfc8cc445c9 introduced a regeneration of the initramfs, which I think does work as described because it runs in the loopback device. However, dracut includes a package that installs configuration overrides to build a generic initramfs. This is really what we want, and should solve the problem no matter where the initramfs is created. Add this package into yum-minimal and remove the extra re-create call which should not be necessary. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1405238 Change-Id: I5d203f2abe743cb23a44d449850e692a948e7871
2016-12-16 00:10:23 +00:00
dracut-config-generic:
Remove fedora-minimal/install.d/99-ramdisk When the kernel gets installed on Fedora, the rpm post scripts call "/bin/kernel-install" [1] to install it. This is a script provided by systemd. However, in [2], Fedora ships a patch to kernel-install that makes a call-out to /sbin/new-kernel-pkg -- the install script provided by grubby [3] Without grubby installed, systemd's kernel-install script goes off and runs dracut plugins directly [4], which eventually creates the initrd. For reasons that are not clearly explained, the initrd will end up in a a "machine-id" sub-directory of /boot (possibly, so you can symlink it?). It is also called "initrd", even though it's an initramfs, for historical reasons in dracut I think. It is at this point that I think 99-ramdisk has been written to move the generated initrd file back into /boot. Later on, when we build the image, we run grub-install and it picks up the kernel and the initrd and installs everything. grubby's new-kernel-pkg [6] it's very similar -- it uses dracut to make the initramfs ... but in this case it is put in /boot and is actually called initramfs. The subtle change that led me down this path is that dracut has been modified to have a "Recommends" for grubby for >F22 [7]. After discussing this change with the author, it turns out it was *always* intended to use the grubby-based kernel install scripts for Fedora -- our builds have been incorrect in not including the package. The author got sick of people removing the package and making unbootable systems, hence the change. Thus this removes the workarounds in 99-ramdisk and replace it with an install of the grubby package. grubby's kernel install script will put the kernel & generated initramfs in /boot, and it will be installed correctly via the usual grub install later when we build the disk image. I have built F22 & F23 fedora-minimal images with this and they boot. [1] http://pkgs.fedoraproject.org/cgit/kernel.git/tree/kernel.spec#n1832 [2] http://pkgs.fedoraproject.org/cgit/systemd.git/tree/kernel-install-grubby.patch [3] http://linux.die.net/man/8/new-kernel-pkg [4] https://github.com/haraldh/dracut/blob/master/50-dracut.install [5] https://github.com/systemd/systemd/commit/81516adcb71a47837544340f72eb8ee810274119 [6] https://github.com/rhinstaller/grubby/blob/master/new-kernel-pkg [7] https://github.com/haraldh/dracut/commit/47ff68e78b3bbd01367948b5b9fe1cbaeb45f262 Change-Id: I1a6e45d04755515286b3d49f8280c16b527e2f48
2015-11-19 03:51:03 +00:00
grubby:
Add a yum-minimal element that just uses yum The centos-minimal approach of using rinse does not, it turns out, work on centos. That's a bummer. It's also rather heavyweight. Instead, with minor machinations, we can just use yum itself pointed at a chroot. Also adding fedora-minimal element which creates a fedora image using the new yum-minimal approach. Co-Authored-By: Gregory Haynes <greg@greghaynes.net> Change-Id: I026fd9d323e786dae5bb67824c6501067e1ceaa3
2015-03-22 14:04:46 +00:00
kernel:
initscripts:
man-pages:
Install lsb package by map name instead of package name We have a pkg-map entry for lsb_release, but in package-installs.yaml we refer to the actual package name instead. This will happen to work on Red Hat platforms, but it's actually wrong. Change-Id: Idb248f96e75fa1090422fa08e5fbb2385cc1f517
2016-11-11 20:30:21 +00:00
lsb_release:
Uninstall linux-firmware and linux-firmware-whence linux-firmware and linux-firmware-whence (meta package for mostly iwl firmwares) packages account for approx. 289 M install size on a F30 system, and linux-firmware for approx. 176 M on CentOS 7. Users needing these firmwares are eventually baremetal users and are not looking for a very minimal operating system base install like virtual image users are. Thus, a non-minimal OS element is better suited for them. Alternatively, it could be later considered a dedicated firmware element. This is inline with I8ce65e1d357d15e8ed8995ad1dcaea02bbd1986f. Change-Id: If104fc3c1e9349b8d501a2351fff1ab4c0dbc6a4
2019-08-09 07:48:17 +00:00
redhat-rpm-config:
linux-firmware:
uninstall: true
linux-firmware-whence:
uninstall: true
Add NetworkManager and dhcp-client for CentOS 8 As described inline, NetworkManager and dhcp-client make up the basic networking for centos 8 installs; bring them into the base image. Although in infra we then use simple-init, some other users find this helpful. Change-Id: Ib9f32e73bf9109cc1b659fe1deceb1a15301ffeb
2019-10-02 07:18:34 +00:00
# NOTE(ianw) pkg-map restricts this to !rhel/centos 7; in 7
# the "initscripts" package handles basic networking, in
# 8+ it's the role of NetworkManager and dhcp-client. This
# mirrors the default packages installed in upstream cloud images
# to facilitate a basic network.
NetworkManager:
Revert "dib-lint: use yamllint to parse YAML files" This reverts commit 6ee2995214ee5512c64244ce0ccc7fda639c2d36 and e85c2a6f035a016f80de3d5aebc026f28dfb6bc1. I missed that if you pip install and then run dib-lint, it's not going to pick up the .yamllint file shipped here. Thus it gives spurious errors. The reason for this was simply better duplicate key detection in yaml files, which caused us problems with the kernel installs. However, at this point it seems just the old "does it load" test from pyyaml will be enough. Change-Id: I87a9fc9bb119cfeffad48fc0fa0df31f0181825d
2020-05-28 06:41:01 +00:00
dhcp-client:
Reference in New Issue Copy Permalink