On Wed, Feb 10, 2021, at 13:17, redbaronbrowser via CentOS-devel wrote:
On Wednesday, January 20, 2021 9:31 AM, Mike McGrath mmcgrath@redhat.com wrote:
I've confirmed with the team, the git repo is going to be all the normal git patches you would expect (IE: not arbitrarily munged together in some way). There's one or two more things they're configuring with gitlab and they expect to have an actual repo that you can look at / poke at to validate what I'm saying in a few weeks.
-MikeMike, is there any status update on individual patches applied to Stream's kernel?
Can we move forward with this SIG so I can publish the information I already have?
What about a Stream Plus kernel? The directory for Stream still has no packages at all.
Or delivering kpatch live security updates without a reboot?
I am ready to move forward immediately if the SIG is approved. Is there a reason to wait another "few weeks"? _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
I see your questions roughly grouped in 3 categories, correct me if I've misinterpreted:
- How do I get patches into the Stream kernel *now*? Have you submitted any bugs against CentOS Stream on bugzilla.redhat.com with your patches? I want to make sure, first, that we have an actual answer because some of them may indeed be workable for inclusion in RHEL.
All contributions for RHEL/Stream 8 (not just the kernel) are flowing through this bugzilla process for right now.
- When can we see the new kernel workflows? I don't have specific date/time when we expect to see the new-way of doing kernel repos but I would check https://gitlab.com/redhat/ towards the end of the month. Those will be targeted at RHEL/Stream 9 kernels. I'm asking around about some of the work we're doing to make the Stream 8 kernel sources more accessible in a format that isn't just tarballs.
- How do I get kernels that are not shipped in-distro? Here's the problem as it exists right now, Kernels typically need secureboot signatures on them, and we don't have the infrastructure we need to make those signatures happen in the community build system. We're talking about ways to enable that directly in CBS, but in the meantime we plan to take community-based kernels and assist with getting builds done on infrastructure that can do signing. Note: this affects other packages like fwupd, grub, etc. We are absolutely open to continuing to build the Plus kernel. Would it make sense to get yourself, @toracat for the Plus kernel, and whoever else is interested in building kernels together on IRC to talk about how to handle coordination here?
With regard to distributing kpatch updates, I'd advise caution here. I get the sense that there may be problems building and testing all of the combinations of kpatches that a SIG might want to ship.
Let me know if there's anything else I can help with.
--Brian