Fedora CoreOS Meeting Minutes 2020-05-27
by Dusty Mabe
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-05-27/fedora_core...
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2020-05-27/fedora_core...
Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-05-27/fedora_core...
========================================
#fedora-meeting-1: fedora_coreos_meeting
========================================
Meeting started by lucab at 16:30:56 UTC. The full logs are available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-05-27/fedora_core...
.
Meeting summary
---------------
* roll call (lucab, 16:31:30)
* Action items from last meeting (lucab, 16:35:31)
* bgilbert PR'd signing key to c-i, dustymabe PR'd to f-c-c
(bgilbert, 16:37:41)
* F32 rebase (lucab, 16:42:27)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/372
(lucab, 16:42:35)
* no technical blocker to rebase testing to F32 (lucab, 16:51:58)
* Fedora Test day for our `next` stream (Fedora 32) (lucab, 16:52:20)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/491
(lucab, 16:52:28)
* tentatively scheduled test day on June 8th (lucab, 17:01:51)
* network interface name (lucab, 17:06:19)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/484
(lucab, 17:06:30)
* barrier for netnames pinning script should better be in place for
mid-July for OKD GA (lucab, 17:23:26)
* Open Floor (lucab, 17:23:51)
Meeting ended at 17:28:35 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* lucab (79)
* jlebon (30)
* zodbot (18)
* kparal (17)
* lorbus (10)
* cyberpear (9)
* bgilbert (6)
* sumantro (4)
* coremodule (3)
* slowrie (3)
* jdoss (1)
* skunkerk (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
3 years, 4 months
Fedora CoreOS LTS commitment
by Akshay Shah
Hi,
I have been recently experimenting with the stable stream of FCOS.
I just wanted to confirm: is there a LTS commitment for Fedora CoreOS. Before using it in production want to be sure it will be supported for a considerable amount of time. Like Project Atomic and Container Linux if there is chance of project being dropped then it becomes risky to consider it for production. Can you confirm what is the minimum support commitment for Fedora CoreOS?
Thanks.
3 years, 4 months
Fedora CoreOS Meeting Minutes 2020-05-20
by Dusty Mabe
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-05-20/fedora_core...
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2020-05-20/fedora_core...
Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-05-20/fedora_core...
========================================
#fedora-meeting-1: fedora_coreos_meeting
========================================
Meeting started by dustymabe at 16:30:20 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-05-20/fedora_core...
.
Meeting summary
---------------
* roll call (dustymabe, 16:30:24)
* Action items from last meeting (dustymabe, 16:33:51)
* dustymabe created a intermediate testing release with podman fix
(31.20200505.2.1). That fix just landed in stable yesterday
(31.20200505.3.0) (dustymabe, 16:35:27)
* dustymabe created a ticket to further the barrier discussion #480
(dustymabe, 16:36:00)
* ACTION: lorbus to try out OKD on our `next` stream so we can work
out any kinks before switching `stable` to f32 (dustymabe,
16:36:30)
* meeting agenda (dustymabe, 16:37:03)
* F32 rebase tracker for changes discussion (dustymabe, 16:39:32)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/372
(dustymabe, 16:39:39)
* we decided to delay the F32 transition into `testing` until the next
release cycle because of an issue where clients could get stuck in a
"trying upgrade" loop
https://github.com/coreos/fedora-coreos-tracker/issues/481
(dustymabe, 16:40:52)
* Fedora 32 samba-client-libs now pulls in Unicode data (dustymabe,
16:44:18)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/452
(dustymabe, 16:44:23)
* ACTION: cyberpear to take a look to see if we can change the libicu
dep in samba-client-libs to a recommends (#452) (dustymabe,
16:52:33)
* update barrier approach to major upgrades (dustymabe, 16:53:02)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/480
(dustymabe, 16:53:07)
* AGREED: in the interest of signing keys we'll retrofit a barrier for
N-1 -> N at the N+1 point. i.e., 6 months after N came out.
(dustymabe, 17:10:38)
* 2020-05-20: gather status update for Fedora Council (dustymabe,
17:12:56)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/486
(dustymabe, 17:13:03)
* open floor (dustymabe, 17:22:43)
* LINK:
https://github.com/coreos/fedora-coreos-config#moving-to-a-new-major-vers...
(jlebon, 17:25:01)
* ACTION: bgilbert to PR c-i and f-c-c SOP for new signing key
(bgilbert, 17:26:31)
* IDEA: fedora-coreos-rojig.src.rpm, imports the fedora-coreos-config
in Sources, then runs cosa in an rpmbuild, to result in a small
rojig binary RPM, built in Koji -- then only the other artifacts
than the OSTREE need be built in the external-to-compose pipeline
(cyberpear, 17:28:23)
Meeting ended at 17:32:51 UTC.
Action Items
------------
* lorbus to try out OKD on our `next` stream so we can work out any
kinks before switching `stable` to f32
* cyberpear to take a look to see if we can change the libicu dep in
samba-client-libs to a recommends (#452)
* bgilbert to PR c-i and f-c-c SOP for new signing key
Action Items, by person
-----------------------
* bgilbert
* bgilbert to PR c-i and f-c-c SOP for new signing key
* cyberpear
* cyberpear to take a look to see if we can change the libicu dep in
samba-client-libs to a recommends (#452)
* **UNASSIGNED**
* lorbus to try out OKD on our `next` stream so we can work out any
kinks before switching `stable` to f32
People Present (lines said)
---------------------------
* dustymabe (111)
* bgilbert (28)
* jlebon (27)
* cyberpear (27)
* zodbot (20)
* lucab (13)
* walters (5)
* miabbott (4)
* davdunc (4)
* darkmuggle (1)
* abai (1)
* skunkerk (1)
* slowrie (1)
* x3mboy (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
3 years, 4 months
Fedora CoreOS Meeting Minutes 2020-05-13
by Dusty Mabe
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-05-13/fedora_core...
Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2020-05-13/fedora_core...
Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2020-05-13/fedora_core...
========================================
#fedora-meeting-1: fedora_coreos_meeting
========================================
Meeting started by dustymabe at 16:30:19 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-1/2020-05-13/fedora_core...
.
Meeting summary
---------------
* roll call (dustymabe, 16:30:36)
* Action items from last meeting (dustymabe, 16:33:47)
* topics for this meeting (dustymabe, 16:34:07)
* F32 rebase tracker for changes discussion (dustymabe, 16:36:11)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/372
(dustymabe, 16:36:15)
* ACTION: lorbus to try out OKD on our `next` stream so we can work
out any kinks before switching `stable` to f32 (dustymabe,
16:42:33)
* LINK:
https://github.com/coreos/fedora-coreos-streams/issues/99#issuecomment-62...
(jlebon, 16:47:06)
* ACTION: dustymabe to create a ticket where we discuss appropriate
update barrier approach for major upgrades (dustymabe, 17:16:39)
* podman corner case bug: when do we backport fix problems ?
(dustymabe, 17:17:01)
* LINK: https://github.com/containers/libpod/issues/5950 (dustymabe,
17:17:13)
* LINK:
https://github.com/containers/libpod/issues/5950#issuecomment-625450333
(dustymabe, 17:18:35)
* ACTION: dustymabe to get new podman release into testing release so
we can fix stable in next weeks releases (dustymabe, 17:29:44)
* open floor (dustymabe, 17:30:09)
Meeting ended at 17:43:41 UTC.
Action Items
------------
* lorbus to try out OKD on our `next` stream so we can work out any
kinks before switching `stable` to f32
* dustymabe to create a ticket where we discuss appropriate update
barrier approach for major upgrades
* dustymabe to get new podman release into testing release so we can fix
stable in next weeks releases
Action Items, by person
-----------------------
* dustymabe
* dustymabe to create a ticket where we discuss appropriate update
barrier approach for major upgrades
* dustymabe to get new podman release into testing release so we can
fix stable in next weeks releases
* lorbus
* lorbus to try out OKD on our `next` stream so we can work out any
kinks before switching `stable` to f32
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* dustymabe (129)
* bgilbert (87)
* cyberpear (26)
* lucab (26)
* zodbot (15)
* jlebon (12)
* lorbus (10)
* jdoss (3)
* walters (3)
* gilliard__ (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
3 years, 4 months
Fedora CoreOS on multi-arch
by Jakub Cajka
Hello,
I have pushed out first batch of Fedora CoreOS images for
non-x86_64. You can run it on your own locally, both resulting images
and even rebuild them on your own. Please note those images are
unofficial, built outside of Fedora infrastructure.
Place to grab them is
https://fedorapeople.org/groups/fcos-images/builds/. Quick start
information are present in
https://fedorapeople.org/groups/fcos-images/README based on the official
FCOS
quickstart(https://docs.fedoraproject.org/en-US/fedora-coreos/getting-sta....
Blog post format of them is pending release on Fedora community blog. I
would much appreciate any feedback and testing.
More onto the "boring" technical details, if you are user you can skip
rest of the email.
I have been working on building Fedora CoreOS for non-86_64
architectures for several past months. I'm currently in stage that most
of the basic building is working along with kola tests for QEMU target.
I'm also running nightly builds of the CoreOS Assembler container in
Jenkins and push it in to quay.io and docker hub(not yet manifested, due
to some tools issues).
quay.io/jcajka/coreos-assembler:latest[arm64.ppc64le,s390x]
docker.io/jcajka/coreso-assembler:latest[arm64.ppc64le,s390x]
Along with that I do build of FCOS. I still manually push images on to
the fedorapeople.org, I would like to change that eventually.
There is slight deviation on ppc64le as due to some bugs in virt stack,
I have to use more recent qemu&co for coreos-assembler image, that has
AFAIK no impact on the resulting images and slightly relaxed filtered
out packages on s390x(initscripts, config issue pending).
With this announcement I would like to start discussion on how to bring
all of this on the the official Fedora infrastructure and get official
multi-arch builds of FCOS out.
I think that coreos-assembler images is best place to start. Move build
of it from quay to the FCOS Jenkins and source HW for the FCOS Jenkins
instance so we can run the build on all arches and push out the results
manifest listed to the chosen container repositories.
I'm looking forward to your feedback. Thanks to all in Fedora CoreOS for
help.
JC
3 years, 4 months
Re: Fedora CoreOS on multi-arch
by Jakub Cajka
----- Original Message -----
> From: "Alex Perez" <aperez(a)alexperez.com>
> To: coreos(a)lists.fedoraproject.org
> Sent: Saturday, May 9, 2020 2:49:17 AM
> Subject: Re: Fedora CoreOS on multi-arch
>
> Jakub,
>
> How difficult would it be to add armhfp to the CoreOS builds? If you're
> interested in the use case, it's for the third and fourth generation
> OLPC laptops, the XO-1.75 and XO-4, both of which are based on Marvell
> MMP, and are 32-bit, with ~1GB RAM. As of Fedora 32, stock Fedora armhfp
> kernels boot and userland runs, unmodified, on the XO-1.75.
>
> Regards,
> Alex Perez
>
>
I think that it is kind of technically possible, but not that simple. IMHO possibly harder, at least from my perspective, than ppc64le, aarch64 and s390x together. To elaborate even aarch64 will work currently only on UEFI(qemu somewhat tested only). I'm not really sure if there is even some that generic way to do it for armhfp(VMs or boards). My current understanding is that even for aarch64 there will be need to alter the produced "bare-metal" images for the target "non standard" HW/board. Something similar to the arm-image-installer(hopefully just patch for it).
For starting to enable the FCOS you will have to look in the coreos-assembler(https://github.com/coreos/coreos-assembler). Either fully build it on armhfp(IMO easier), although I believe we aren't building Fedora base container image for it or cross build from(aarch64,hard or other system via full emulation hardest). You should be able just start by following the README(IMO it is extremely easy to build Fedore CoreOS locally, on x86_64) and see what will break. One thing is sure that the armhfp will need patches for https://github.com/coreos/coreos-assembler/blob/master/src/cmd-buildexten... and few other place at minimum.
Actually one blocking point might be that you need nested virt working due to the way how the assembler works currently. So not really that easy and I have definitively forgotten some other possible pain points.
For me, from arm side, I hope that I will be able to have time to look in to running FCOS on baremetal aarch64 RPI4(VM runs on rawhide Fedora fine for me ;) ) and RockPro64.
JC
3 years, 4 months
ANNOUNCEMENT: next stream now available (based on Fedora 32)
by Dusty Mabe
*NOTE*: If you are an early adopter of the `next` stream and are
currently running `32.20200416.1.0` there is an issue [1].
Please follow the instructions at the bottom of this email
or your system won't auto update.
We are happy to inform you that the Fedora CoreOS `next` stream
is now available for use. The `next` stream is one of our three
automatically updating production streams for our community to
choose from. The `next` stream is currently based on Fedora 32 [2]
and will soon be rolling into `testing` and eventually `stable`.
Utilizing the `next` stream *now* gives users the opportunity to
find issues and help the community fix them before they enter the
other streams and cause regressions there.
Artifacts that were built from the `next` stream content are
available on the download page [3].
For more information about streams and about switching between
them see the Fedora CoreOS documentation[4].
The Fedora CoreOS Team
[1] https://github.com/coreos/fedora-coreos-tracker/issues/473
[2] https://fedoramagazine.org/announcing-fedora-32/
[3] https://getfedora.org/en/coreos/download?stream=next
[4] https://docs.fedoraproject.org/en-US/fedora-coreos/update-streams/
------------------------------------------------------------
## Fixing `32.20200416.1.0` systems
If you are currently running Fedora CoreOS `32.20200416.1.0` please
run the following to re-enable automatic updates on your system:
```
sudo rm -f /etc/fedora-coreos-pinger/config.d/90-disable-on-non-production-stream.toml
sudo rm -f /etc/zincati/config.d/90-disable-on-non-production-stream.toml
sudo systemctl restart zincati.service
```
3 years, 4 months
