On Fri, May 5, 2023 at 8:52 AM Kashyap Chamarthy <kchamart@redhat.com> wrote:
On Thu, May 04, 2023 at 08:49:23AM -0700, Clark Boylan wrote:
On Thu, May 4, 2023, at 5:52 AM, Kashyap Chamarthy wrote:
On Wed, May 03, 2023 at 03:28:00PM +0000, Jeremy Stanley wrote:
[...]
FWIW, I think it is still valuable to have at least the latest Fedora-only image available. Often times kernel and virtualization fixes are first fixed on Fedora -- many upstream kernel developers happen to use Fedora.
Once upon a time we had OpenSUSE Tumbleweed images too. These distros are in theory great for catching problems early, but in practice it seems very few people (if any) have the time and ability to address every problem that comes up in them.
I agree; it's hard to keep up with that grind.
Another reason I wanted to mention is the 'virt-preview' repo[1]. But I see that 'virt-preview' is also available for CentOS stream. So that's a less strong reason.
Right, it seems like CentOS Stream is filling a very similar role these days and importantly with a much longer runway of support. This means there is less work required to keep CentOS Stream images up compared to Fedora images.
Yeah, resorting to CentOS Stream images is a perfectly reasonable compromise.
That said, if dropping Fedora is the compromise we need to make to reduce the workload of "mirroring and image management, then I don't insist.
Currently there isn't anyone volunteering/able to add Fedora 38 images (which is latest). I think if someone wanted to do that we could proceed, but likely without locally hosted package mirrors. That would reduce a lot of the overhead and limit the work required to spinning up images with diskimage-builder. Based on other feedback [2], I suspect that we just don't have any interested users (and consequently no interested volunteers)? That said we'll wait a bit for more feedback and discussion before making a concrete decision.
Fair; Fedora _is_ a "fast moving target" (as noted in that thread) and can be difficult to keep up in terms of testing it. And I can't offer the time to maintain Fedora images myself, afraid. So I'm personally fine to rely on CentOS Stream images.
Thanks for the considered response, as always.
I'm confused why you're mirroring Fedora repos and building custom Fedora images. Is there something we could do on the Fedora Cloud side to make this workload easier? We already produce OpenStack-targeted Fedora Cloud images, as an example. As a member of Fedora Cloud, I would like to see OpenStack support Fedora fully, I just don't know what's going on here... -- 真実はいつも一つ！/ Always, there's only one truth!