On 3/17/20 2:01 PM, Adam Williamson wrote: Hey Adam, <snip> > > 3) CoreOS - CoreOS is just a *whole* other thing. It is not built like > the rest of Fedora at all. It's not built as Pungi composes, whatever > compose process it does have doesn't run alongside our other compose > processes or output to the same locations, it's like a whole other > product. It also doesn't seem to be terribly well documented (I can't > find any detail on the wiki, docs sites, or any of the git repos I > happen to know of) or even introspectable - for instance, ISO locations > look like > https://builds.coreos.fedoraproject.org/prod/streams/stable/builds/31.20200223.3.0/x86_64/fedora-coreos-31.20200223.3.0-live.x86_64.iso > , but if you try and browse around that tree by visiting URLs like > https://builds.coreos.fedoraproject.org/prod/streams/ , you just > get 'Access Denied'. So if the process appears to have broken down and > some poor monkey like me is left trying to help people figure out where > they can get a 'Fedora CoreOS 32' image to try - it isn't very easy. > Right now I simply have no clue if there is something you could > reasonably call 'Fedora CoreOS 32 Beta' or a decent analogue of it. You have reasonable points here. I do agree that the current state of integration between Fedora CoreOS and the rest of Fedora is not quite complete. Part of the reason for this is that we've been working hard on building Fedora CoreOS from the ground up and getting it out the door. There are two things here worth being explicit about: 1. Fedora CoreOS is today not composed by pungi on Fedora infra. It is composed using coreos-assembler[1] in CentOS CI. I think this fundamental difference is the root to a lot of the mystery here surrounding FCOS. People integrated into Fedora processes are familiar with pungi and how it works. OTOH, I'm sure not many of us are familiar with coreos-assembler. 2. Fedora CoreOS follows a rolling release model, where by design, we don't want people to care about whether they're on f31 or f32 (at least in principle). For FCOS, the f32 update just goes out like any other update when we're ready to do the cutover. Thus, sentences like "Fedora CoreOS 32" don't have quite the same meaning as for e.g. Workstation or Server. That said, Fedora CoreOS does have more streams than just stable and testing, and one of those streams should be $((N+1))-based. So we definitely could have some marketing/banners/whatever to point people at. Right now there is not yet a F32 based coreos, but there will be soon as part of our `next` stream [2]. That said, we know there is work to do to make things better understood and more predictable from the rest of Fedora's point of view. Note that there was a lot of hard work to integrate and participate in more Fedora processes as Fedora Atomic Host matured. Know that this work will come as we finish building out the more foundational pieces of Fedora CoreOS. We have opened a discussion ticket [3] for this in our issue tracker, which is where our meeting topics get sourced from and our discussions generally take place. [1] https://github.com/coreos/coreos-assembler [2] https://github.com/coreos/fedora-coreos-tracker/issues/283 [3] https://github.com/coreos/fedora-coreos-tracker/issues/426. _______________________________________________ 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
