On Mon, 2025-03-10 at 19:48 +0000, Zbigniew Jędrzejewski-Szmek wrote: > On Mon, Mar 10, 2025 at 11:56:43AM -0400, Stephen Smoogen wrote: > > Having tried to dive into Konflux for a bit, I think the major problem is > > that it keeps getting referred to in the wrong format. It isn't a koji > > replacement, it is a Fedora Build System replacement. > > Yes, 100%. But I think this is a direct consquence of how Konflux is > being presented. There have been a few talks about building containers > and a few talks about building rpms, but very little discussion of how > the other parts would be provided, e.g. display of test results or tracking > of update status… I would guess that that functionality is actually much > more complex then just building things. > > > The idea for 'Konflux' is to try and redesign the factory by first making > > everything 'visible' and using the same backbone resources. As I read > > through various things, I see certain parallels between it and microkernel > > operating systems. If my view is somewhat correct, then Konflux is a > > micro-kernel which will primarily do the low level resource and message > > passing that the various internal services are plumbed into. Other parts > > would be done in purpose written services which are meant to do one thing > > only. Some other tooling inside would be checking in/out source code, > > setting up builders, sending source and different spec files to the > > builder, sending the outputs to a testing system, getting the passed > > material to its next 'destinations'. These would all be 'registered' and > > their interactions should be 'visible' so that if XYZ is broken we know > > that ABC may still work but EDF won't > > Yes, that description makes a lot of sense. I would love to see > presentations about Konflux at this level. Ideally, with a lot more > details, incl. what parts are supposed to stay and what is intended > to be rewritten from scratch. So I think one big issue here is that what Konflux is *right now*, more or less, is a tekton pipeline that can make container images. It does that already! RH is using it to build container images for RHEL. What we could do with it *right now* for Fedora is...build some container images with it. I think it would be a fine idea to do that, just to see how it works. Maybe even some of the ones we ship! (But I don't think that hard enough to do the work myself). What Konflux is *envisaged to be* is an all-singing, all-dancing Distribution Construction Kit that does all of the above and also makes your tea. RH has some really...optimistic...ideas about when it can be that. But it's *not* that yet. As others have noted, it can't even really build RPMs properly yet. So what we have is sort of, on the one hand, a real tool with modest real capabilities, and on the other, a Grand Vision with some extremely heroic mooted timelines, and whenever I'm talking to someone about Konflux I'm not quite sure which one I'm talking about. So if the question is "when is the right time to build some containers with Konflux as an experiment?" I'd say the answer is "right now". If the question is "when do we shut down Koji and Bodhi and punt the datacenter into space?", I'd say "more data needed". -- Adam Williamson (he/him/his) Fedora QA Fedora Chat: @adamwill:fedora.im | Mastodon: @adamw@xxxxxxxxxxxxx https://www.happyassassin.net -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
