14:01:02 #startmeeting Fedora IoT Working Group Meeting 14:01:02 Meeting started Wed Oct 3 14:01:02 2018 UTC. 14:01:02 This meeting is logged and archived in a public location. 14:01:02 The chair is pbrobinson. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:02 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:01:02 The meeting name has been set to 'fedora_iot_working_group_meeting' 14:01:02 #chair pwhalen pbrobinson bcotton 14:01:02 Current chairs: bcotton pbrobinson pwhalen 14:01:02 #topic roll call 14:01:08 * pwhalen is here 14:01:12 morning folks 14:01:13 .hello2 14:01:14 bcotton: bcotton 'Ben Cotton' 14:01:15 who is here? 14:01:16 * ipcloud here 14:01:24 Tim Jones 14:02:30 We'll give people another minute 14:03:21 #topic 1) ==== Working Group process and admin ==== 14:03:27 #link https://fedoraproject.org/wiki/InternetOfThings/PRD 14:03:38 #info last week we approved the IoT PRD 14:04:21 #action please give it a final review and I'll open a ticket to get the council to review and accept it 14:05:09 does anyone have anything they wish to discuss on the PRD, any queries or things they'd like to highlight? 14:05:34 * bcotton has something unrelated to the PRD but still in the general umbrella of process and admin 14:06:00 bcotton: go for it 14:07:27 pbrobinson: relrod still needs a download URL afaik 14:07:47 bcotton: that's actually on my todo list for this afternoon 14:07:54 awesome! 14:08:16 * pbrobinson has been swamped with last minute pre freeze requests 14:09:39 anyone else with any PRD, WG or general admin style queries/requests etc? 14:10:07 #topic 2) ==== Nightly builds ==== 14:11:01 I've turned these off for a day or two, they'll be running again from tomorrow, I need to fix up a few bits around re-distribution which it seems I missed for F-29+ 14:11:21 I'll send an email out to the list with details 14:11:36 #topic 3) ==== Fedora 29 status for IoT ==== 14:11:47 so I think we're looking OK here 14:12:03 ipcloud I know I have some follow up to do around your install issues 14:12:38 and from a technical PoV i need to finalise how the release process happens 14:13:35 does anyone else have any F-29 points to bring up? 14:14:07 do we have release criteria for f29? 14:14:08 * ipcloud should I hold off for a new update? What is the preferred setup I should have ? 14:14:50 ipcloud: the main thought I had with your issue, not had a chance to look at the logs, was were you doing any fancy storage config? 14:14:57 pwhalen: good point 14:15:15 #info what should our release criteria be 14:15:27 * ipcloud no - both the machines with local disk 14:15:52 at this point I've basically gone for "run on supported platforms, be able to apply updates, be able to run containers" 14:15:56 * ipcloud take this topic to later? 14:16:27 ipcloud: probably best discussed in #fedora-iot out of meeting really 14:16:44 right, upgrades/downgrades, containers, layered packages 14:18:21 pwhalen: want to put together an initial wiki page for release criteria in the http://fedoraproject.org/wiki/InternetOfThings/ subset and set it out to the list for review? 14:18:54 pbrobinson, sure, will d 14:18:57 *do 14:20:06 also of note we should have OOTB WiFi support for Raspberry Pi 3+/3B+ in Fedora 29/IoT (it's in kernel-4.18.11-301.fc29 linux-firmware-20180913-87.git44d4fca9.fc29) 14:20:23 most excellent :) 14:20:23 tim-jones: I suspect you'll be interested in ^^ 14:20:59 absolutely - thanks :-) 14:21:28 tim-jones: feedback welcome with testing, should be in IoT composes probably Friday 14:21:30 So is the 3B+ equally well supported as the 3B now? 14:22:12 tim-jones: in what context, it's been pretty damn close since F-28, apart from some stability around the wired NIC 14:23:53 I'd held back using as I had heard that there were issues with networking on the B+, which were fine on the B - good to hear thanks 14:25:09 tim-jones: I think in F-29 it's much better, both wired and wireless, but please do test and let me know if you see issues, can't fix them if we don't know of them ;-) 14:25:28 anything else for f29? 14:25:32 OK will do 14:25:54 #action pwhalen to put together an initial wiki page for release criteria in the http://fedoraproject.org/wiki/InternetOfThings/ subset and set it out to the list for review? 14:26:13 ack 14:26:23 #action pbrobinson to send out details of the latest F-29 for wider testing to the list 14:27:24 #topic 4) ==== Fedora 30 planning ==== 14:27:30 #undo 14:27:30 Removing item from minutes: 14:28:16 #info please provide feedback on staging IoT landing site https://iot.stg.fedoraproject.org/ 14:28:33 #topic 4) ==== Fedora 30 planning ==== 14:28:59 #info Fedora 30 will be the First core release as an edition 14:29:51 #info plan on doing releases between F-29 GA and F-30 so it'll be more of a marker as hopefully by then have a lot of the process in place 14:30:18 we need to start defining what will be core parts of this release 14:30:43 ARMv7 (arm32) will definitely be there, as will multi arch containers from the build pipeline 14:30:52 provisioning tools using ignition 14:31:06 tightened security around seccomp 14:31:44 a bunch of CI/CD for automated testing 14:32:32 does anyone have any queries, suggestions? 14:33:30 lots to do 14:34:23 query: what is the intended mechanism to add packages to fedora-iot? (container, add package to custom tree config...) 14:34:57 tim-jones: depends on the package. The main intended way to add functionality is containers 14:35:43 but if it's something needed in the base level such as storage or network level config it might be to add it to the base image or via a layer 14:35:49 that's what I thought - but one of my colleagues (Tim Coote, whom you know) seems to have an aversion to containers 14:36:06 also planned is an "IoT Toolbox container" 14:36:29 No definitely not OS extensions - custom services - the sort we build to integrate to various different sorts of devices 14:36:29 tim-jones: well it depends on what you wish to do 14:37:00 (Don't want to drag the meeting off topic) 14:37:13 tim-jones: that would definitely be a container, also things like integration with say Azure IoT/Google IoT/AWS IoT would be cotnainers 14:38:01 That's what I thought - I just wanted to confirm 14:38:10 Thanks 14:39:20 tim-jones: it enables it to be upgraded at a different variance to the base OS, have different versions of libraries than the base OS etc. IE be more isolated and independent 14:40:23 anything else for F-30 / Fedora Edition topic? 14:42:08 #info ARMv7 (arm32) will definitely be there, as will multi arch containers from the build pipeline 14:42:08 #info multi arch container build pipeline with a number of containers available 14:42:08 #info also planned is an "IoT Toolbox container" 14:42:08 #info provisioning tools using ignition 14:42:08 #info tightened security around seccomp 14:42:09 #info a bunch of CI/CD for automated testing 14:42:18 just so those are noted in the minutes 14:42:47 #topic 5) ==== Open Floor ==== 14:42:56 anything for open floor? 14:46:01 I'll give you all a few more mins, please just ask if you have anything to discuss 14:50:52 thank you all 14:50:53 #endmeeting