From: Philipp Rudo on
gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2917#note_1803...
Regarding why we are doing this here and not in a separate rpm,
@vkuznets
might have a more detailed answer but the main point is that it would be
easier to do it here, because addons are very lightweight and honestly we
don't think we will ship many of them. In addition creating a rpm could be a
more complicated process.
I agree, that handling them here is easier. But I doubt that there will only
be a few addons. There are a ton of debug parameters that at some point in
time will be needed. Plus there are bugs that can be worked around by "setting
the right parameter". Furthermore, we need the ability to disable memory
hungry parameters for the kdump kernel. All in all my expectation is that the
number will increase rapidly once UKIs get used more.
Regarding kernel configs, you mean redhat/build_configs.sh?
Yes. Or just the directory structure in general.
It seems unlikely that we will have kernel version specific addons.
The use
cases discussed thus far all look like global addons. As such I think it is
preferable to treat these as global addons until someone comes along with a
clear use case for a version specific addon.
Not sure if that is a valid scenario for CVMs, but one use case is when you
have multiple UKIs installed that require different `crashkernel=` parameters.
Then you need to be able to install different addons for each UKI. A similar
scenario is when one of the UKIs has a bug that can be worked around by
"setting the right parameter" that is otherwise beneficial. In that case you
want to have version specific addons as well.