Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support kpatch #118

Open
cgwalters opened this issue Mar 23, 2015 · 1 comment
Open

Support kpatch #118

cgwalters opened this issue Mar 23, 2015 · 1 comment

Comments

@cgwalters
Copy link
Member

cgwalters commented Mar 23, 2015

As of recently, rpm-ostree supports live updates ( #639 ) particularly for "pure package additions".

kpatch is logically a pure package addition.

RHEL spends a lot of effort on generating kpatches, and we should support their use on rpm-ostree systems too.

Currently admins install RPMs (but yum plugin has been prototyped). These RPMs include a kernel module that is loaded; the data is dropped in /var/lib/kpatch (SCAP knows to scan there).

The RPM also regenerates the initramfs to ensure that the kpatch is also applied on the next boot (but that's optional).

I think the most important thing to happen here is to figure out the desired administrator UX, as well as what the update provider supports. There are a lot of fundamental questions.

The RPM-delivery model has kpatches as distinct stream of RPMs (yum repository). Perhaps the simplest start is to just match the kpatch-rpm experience via something like:

$ rpm-ostree install -A "kpatch-patch = $(uname -r)"

(This also heavily intersects with #2883 in that we can make it literally the same command)

There's a bunch of other tweaks to do; ideally rpm-ostree status shows you the kpatches that are applied)

@cgwalters
Copy link
Member Author

The daemon mode in #157 needs to land first for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants