14:09:24 <pwhalen> #startmeeting Fedora IoT Working Group Meeting
14:09:24 <zodbot> Meeting started Wed Dec 16 14:09:24 2020 UTC.
14:09:24 <zodbot> This meeting is logged and archived in a public location.
14:09:24 <zodbot> The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:09:24 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:09:24 <zodbot> The meeting name has been set to 'fedora_iot_working_group_meeting'
14:09:24 <pwhalen> #chair pwhalen pbrobinson bcotton tdawson puiterwijk coremodule
14:09:24 <zodbot> Current chairs: bcotton coremodule pbrobinson puiterwijk pwhalen tdawson
14:09:24 <pwhalen> #topic roll call
14:10:07 * cyberpear listens in
14:10:27 * tdawson is here
14:10:52 * defolos is around
14:10:57 * pbrobinson o/
14:11:22 <pbrobinson> cyberpear: feel free to participate ;-)
14:11:33 <pwhalen> #topic 1) ==== Working Group process and admin  ====
14:11:33 <pwhalen> #link https://docs.fedoraproject.org/en-US/iot/
14:11:52 <pbrobinson> So we have aarch64 container build components now
14:12:03 <pwhalen> w00t!
14:12:18 <tdawson> Ya!!
14:12:22 <pbrobinson> I'm still working out how all that works but it means we can start to build application stack more easily for x86_64 and aarch64
14:12:53 <defolos> 🎉
14:13:11 <pbrobinson> #info container building now support for aarch64 alongside existing x86_64 support
14:13:20 <pbrobinson> #link https://osbs.readthedocs.io/en/latest/users.html#
14:13:29 <pbrobinson> #link https://docs.pagure.org/releng/layered_image_build_service.html
14:13:43 <pbrobinson> thanks to the CPE team for getting this done!
14:14:13 <pwhalen> thanks for the links
14:15:03 <pwhalen> Anything else for admin?
14:15:13 <pbrobinson> not for this topic
14:16:06 <pwhalen> #topic 2) ==== Fedora 33 status ====
14:16:27 <pbrobinson> #info Fedora-IoT-33-20201215.0 compose going out as stable this afternoon
14:16:33 <pwhalen> #info Latest - Fedora-IoT-33-20201215.0
14:16:33 <pwhalen> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=33&build=Fedora-IoT-33-20201215.0&groupid=1
14:17:12 <pwhalen> Looks good. Has anyone hit any issues?
14:18:18 <pwhalen> I saw mail from the list we lost clout-utils? Person having issues with growpart not being on the image.
14:18:26 <pwhalen> cloud-utils
14:19:28 <pwhalen> We need to update the docs minimally
14:19:43 <pwhalen> Anything else for F33?
14:20:08 <pwhalen> #topic 3) ==== Fedora 34 (Rawhide) status ====
14:20:32 <pwhalen> #info Latest compose - Fedora-IoT-34-20201216.0
14:20:32 <pwhalen> #link https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=34&build=Fedora-IoT-34-20201216.0&groupid=1
14:20:46 <pwhalen> Hot off the presses, still working its way through openqa
14:20:59 <pbrobinson> pwhalen: I don't ever remember us shipping cloud-utils, and I think systemd has a grow partition utility
14:21:16 <pbrobinson> pwhalen: we've basically mostly used the arm-image-installer functionality
14:21:45 <pwhalen> ok, it seems its in our docs, I'll take a look and update
14:22:43 <pwhalen> #info rpm-ostree crashes on armhfp when installing some packages ( https://bugzilla.redhat.com/show_bug.cgi?id=1906184 )
14:23:20 <pwhalen> that looks to be fixed, but waiting on a build
14:25:06 <pwhalen> Anything else we want to discuss for F34?
14:25:48 <pwhalen> #topic 4) ==== Open Floor ====
14:26:26 <pwhalen> #info Fedora-IoT 34 RC 20201216.0 nightly compose nominated for testing
14:26:47 <pwhalen> #link https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_34_RC_20201216.0_Summary
14:27:18 <cyberpear> I'm curious what's the overlap between IoT and CoreOS and when might I want IoT? (I'm very familiar w/ Fedora CoreOS)
14:29:42 <cyberpear> or if the two might share more (e.g., build) tooling in the future?
14:29:43 <pbrobinson> cyberpear: what overlap, IoT is focused on IoT and Edge user cases, CoreOS is focused on k8s
14:30:14 <pbrobinson> cyberpear: they both use rpm-ostree but that's like asking why the overlap between Workstation and KDE because they both use dnf
14:30:37 <cyberpear> RHCOS is k8s-only, but Fedora CoreOS tries to be more generic
14:31:11 <smooge> pbrobinson, I have a point for open floor
14:31:16 <cyberpear> (but fair enough that the overlap is small)
14:31:33 <cyberpear> smooge: go for it!
14:31:51 <smooge> there may be an un-foreseen problem with container builds on aarch64 currently
14:32:33 <smooge> the team set it up using Fedora 33 and OKD and there are a couple of config differences between that and the EL7-OSBS that x86_64 has
14:32:50 <pbrobinson> cyberpear: it's FCOS is still focused as a k8s distribution, just not only openshift
14:33:31 <pbrobinson> smooge: unforseen as in it's going to be fixed, or you want eyes out and reports if there's problems seen?
14:33:40 <smooge> one of those was how layering is done with the default with F33/OKD being overlays and EL7-x86_64 with devicemapper
14:33:57 <smooge> the first problem that has been run into is that the overlays does not allow for hardlinks
14:34:23 <smooge> so certain builds are failing because they untar and hardlink
14:34:48 <smooge> i lost the ticket.. one sec
14:35:11 <smooge> https://pagure.io/fedora-infrastructure/issue/9532
14:35:34 <smooge> the fix seems to require rerolling out the infrastructure in places
14:35:48 <smooge> it will be looked at in the new year
14:36:18 <smooge> that is all I know but I didn't want you to run into it this break without knowing at least that amount
14:36:30 <pwhalen> thanks smooge
14:36:50 <cyberpear> pbrobinson: FCOS runs any generic workload that can run inside a container, including k8s.  FCOS ships both docker and podman so users can choose their preference. Users can also layer rpm-ostree packages, but the marketing/support team heavily encourages folks to do it in containers instead
14:37:06 <pbrobinson> smooge++ thanks
14:37:06 <zodbot> pbrobinson: Karma for smooge changed to 9 (for the current release cycle):  https://badges.fedoraproject.org/tags/cookie/any
14:37:49 <pbrobinson> cyberpear: sure, I used the term focused for a reason!
14:37:50 <smooge> no problem. I am going to spend this break trying to catch up on all of this
14:38:03 <pwhalen> that doesnt sound like a break
14:40:24 <pwhalen> #info The next Fedora IoT meeting will be January 6th, 2021
14:40:46 <pwhalen> Have a nice break everyone! See you next year
14:40:48 <pwhalen> #endmeeting