systemd in c9s ships with oomd, but it's not terribly useful/usable without its config, so we should ship systemd-oomd-configs too.
Put up https://gitlab.com/redhat/centos-stream/release-engineering/comps/-/merge_requests/42 to add it to comps
As mentioned on the MR, systemd-oomd will not be enabled by default in CentOS Stream or RHEL. We can use this bug to add the package to the compose in other ways if it's something we're going to support at all.
Thanks Josh, how about https://gitlab.com/redhat/centos-stream/release-engineering/pungi-centos/-/merge_requests/42 then to add it to the pungi config for the compose? This won't have any effect unless the daemon is enabled and the package is installed, so it should be fine to do even if oomd isn't going to be enabled by default.
For CentOS Stream and RHEL-9 we are planning to put systemd-oomd to a subpackage alongside the default configuration. Package won't be installed by default and whoever wants it will get the daemon together with the default config after installing systemd-oomd subpackage.
In RHEL we want users to have the option to use it but we don't want oomd present in every environment where systemd rpm is installed (e.g. container images). Hence we need to move systemd-oomd daemon binary to a subpackage and then it make sense to also rename current config subpackage to just say systemd-oomd.
Davide, does this plan work for you?
Yeah, that works -- if we're doing a subpackage for systemd-oomd, we can put the default configs in it too. Thanks!
Put up https://gitlab.com/redhat/centos-stream/rpms/systemd/-/merge_requests/17 for this
Morning all, just added a note to the MR. Looks like there was a minor miss in the scriptlets being added (MR 18).
Adding the note here for visibility.