14:00:15 #startmeeting Fedora IoT Working Group Meeting 14:00:15 Meeting started Wed Mar 11 14:00:15 2020 UTC. 14:00:15 This meeting is logged and archived in a public location. 14:00:15 The chair is pwhalen. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:15 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:16 The meeting name has been set to 'fedora_iot_working_group_meeting' 14:00:16 #chair pwhalen pbrobinson bcotton tdawson puiterwijk 14:00:16 #topic roll call 14:00:16 Current chairs: bcotton pbrobinson puiterwijk pwhalen tdawson 14:00:30 * pbrobinson is here 14:00:36 * tdawson is here 14:01:13 * pwhalen gives it a minute for others to join 14:02:07 .hello2 14:02:08 puiterwijk: puiterwijk 'Patrick Uiterwijk' 14:02:39 .hello2 14:02:40 bcotton: bcotton 'Ben Cotton' 14:03:13 #topic 1) ==== Working Group process and admin ==== 14:03:13 #link https://docs.fedoraproject.org/en-US/iot/ 14:04:11 pbrobinson, bcotton do either of you have anything for this topic? 14:04:24 the naming process is ongoing 14:04:27 pwhalen: yes 14:04:29 we have some suggestions 14:04:31 that ^^ 14:04:42 #link https://fedoraproject.org/wiki/IoT/Name 14:04:56 #link https://communityblog.fedoraproject.org/help-us-name-the-fedora-iot-edition/ 14:05:05 * jsmith joins late, as usual 14:05:08 wow! lots of suggestions since I last looked 14:05:09 #info the deadline for submitting name suggestions is Sunday 15 March 14:05:57 wow, there are a lot of names. we'll have to find good excuses to cut some of them down :-) 14:06:38 there's some that are not appropriate for various reasons, eg trade marks etc 14:08:19 i'm going to do a pass through this today or tomorrow and recommend some rejections for things that are not appropriate 14:08:27 (sent to the mailing list) 14:08:52 sounds good. 14:09:16 anything else? 14:09:29 I hadn't looked for a while either. Some of those are quite good. 14:10:09 i'm done until the F32 section 14:10:17 nothing from admin from my PoV other than I have a few tickets I need to follow up on, been drowning a bit the last couple of weeks 14:11:20 #topic 2) ==== Fedora 31 status ==== 14:11:20 #info Latest compose available for testing 14:11:20 #link https://kojipkgs.fedoraproject.org/compose/iot/Fedora-IoT-31-20200223.0/compose/ 14:11:48 Any issues in F31? 14:13:22 #info No issues reported in Fedora 31. 14:14:17 #topic 3) ==== Fedora 32 status ==== 14:14:17 #info Latest compose available for testing 14:14:17 #link https://kojipkgs.fedoraproject.org/compose/iot/Fedora-IoT-32-20200310.0/compose/ 14:14:20 no issues, some possible bug fixes incoming, planning on a new release shortly 14:14:49 o/ 14:15:06 bcotton: go 14:15:23 #link https://fedoraproject.org/wiki/Releases/32/ReleaseBlocking 14:15:46 I added what I understand to be the release blocking images to this page 14:15:54 looks good to me, meant to reply to the email this morning. 14:15:59 pwhalen: thanks! 14:16:16 WOF 14:16:19 EOF, too 14:16:29 do we want any size maximums? 14:17:09 I dont think we need them (yet) 14:17:39 Last week we attempted a test day, it did not go well. 14:18:00 :-( 14:18:17 The disk images had issues, one of which was configuration. No way to configure, nothing documented. 14:18:44 I believe if you tested, and it failed, it is a success, becasue you tested. :) So we had a successful testing, it's just that the checkboxes were marked failed. 14:18:58 tdawson++ 14:18:58 bcotton: Karma for tdawson changed to 7 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 14:19:19 There were some notes about using ignition- which didnt work for me. Perhaps because we lost 'chronyd' and the time wasnt correct when it tried to get the config 14:20:14 those issues are now fixed, the disk images once again have chronyd. However, configuration is still not documented 14:20:41 very good point tdawson :) 14:21:08 installs worked fine, and we had some testing there. I think one bug was also reported about wifi not working after install. 14:22:10 I would like to run another test day after Beta 14:22:26 +1 14:23:39 we'll need better documentation on using Zezere. I am also unclear on how it will work with the disk images. 14:24:12 +1 on test day 14:24:27 +1 for documentation as well ... sorry, a little slow today. 14:25:48 puiterwijk, any update on Zezere? 14:26:27 pwhalen: I've fixed a bunch of the issues ew found last week, and am now implementing support for disk image bsaed provisioning 14:27:16 awesome, I'll need to work on some documentation for it, once you have something I can test 14:27:56 it looks like we'll slip for unresolved blockers/no RC 14:29:19 pwhalen: yes, the lack of provisioning of disk images came up when we were testing on test day and I opened a bunch of issues as part of that process 14:29:42 we should have a 0.3 release tagged RSN with those issues fixed and a bunch of others 14:29:57 we also have an issue with podman that should be fixed, btu I've not be able to test it. I hope to do that today 14:30:44 #info Pull fails with: Image architecture mismatch: image uses "aarch64", expecting "arm64" 14:30:51 #link https://bugzilla.redhat.com/show_bug.cgi?id=1793927 14:31:30 way late, time change threw me off, but /me is here 14:31:45 howdy coremodule! 14:33:42 anyone with anything else for F32? 14:34:45 nothing from me, things are getting there 14:34:59 #topic 4) ==== Open Floor ==== 14:36:10 Nothing from me 14:36:10 anything for open floor today? 14:36:25 nothing here... 14:36:31 not from me 14:37:20 #endmeeting