16:30:40 #startmeeting fedora_coreos_meeting 16:30:40 Meeting started Wed Sep 23 16:30:40 2020 UTC. 16:30:40 This meeting is logged and archived in a public location. 16:30:40 The chair is dustymabe. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:30:40 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:30:40 The meeting name has been set to 'fedora_coreos_meeting' 16:30:44 #topic roll call 16:30:46 .hello2 16:30:47 dustymabe: dustymabe 'Dusty Mabe' 16:31:07 .hello sohank2602 16:31:08 skunkerk: sohank2602 'Sohan Kunkerkar' 16:31:20 .hello2 16:31:21 lucab: lucab 'Luca Bruno' 16:31:36 .hello2 16:31:37 lorbus: lorbus 'Christian Glombek' 16:31:45 .hello2 16:31:46 bgilbert: bgilbert 'Benjamin Gilbert' 16:32:55 .hello2 16:32:56 darkmuggle: darkmuggle 'None' 16:33:12 .hello2 16:33:13 nasirhm: nasirhm 'Nasir Hussain' 16:33:17 .hello2 16:33:18 jlebon: jlebon 'None' 16:35:27 #chair skunkerk lucab lorbus bgilbert darkmuggle nasirhm jlebon 16:35:27 Current chairs: bgilbert darkmuggle dustymabe jlebon lorbus lucab nasirhm skunkerk 16:35:32 .hello2 16:35:34 nasirhm: good to see you :) 16:35:35 walters: walters 'Colin Walters' 16:35:39 #chair walters 16:35:39 Current chairs: bgilbert darkmuggle dustymabe jlebon lorbus lucab nasirhm skunkerk walters 16:35:49 #topic Action items from last meeting 16:35:54 * jlebon to create a tracking ticket to move the rpm database from bdb 16:35:56 to sqlite in a barrier release in the f33 time frame 16:36:22 #info jlebon filed https://github.com/coreos/fedora-coreos-tracker/issues/623 16:36:28 dustymabe: Thank you, Work's stabilizing at my side and am now resuming where I left off at fedora :) 16:37:31 yay 16:37:34 thanks jlebon 16:37:42 moving on to the next topic 16:37:50 #topic Need dnsmasq for podman to create CNI networks 16:37:55 #link https://github.com/coreos/fedora-coreos-tracker/issues/519 16:38:12 this is an older topic but it came up recently because of some changes in podman 2.1.0 16:38:36 in podman 2.1.0 dnsmasq is a hard requirement of podman-plugins 16:38:47 and podman-plugins is a hard requirement of podman 16:39:14 it turns out that dnsmasq *should* be a hard requirement of podman-plugins because the dns bit is all that podman-plugins does (at least currently) 16:39:40 though it's not clear if we can relax the hard requirement of podman -> podman-plugins itself 16:40:19 sounds like the functionality is broken now, though? 16:40:38 since the package is missing 16:40:50 cyberpear: yes, if you want that "networking" bit where you can refer to containers by name, then it doesn't work currently 16:41:22 i think it's ok if we make it a weak dep and dnsmasq gets pulled in when users layer it 16:41:35 `podman-plugins is a hard requirement of podman` what? 16:41:52 walters: at least that is my experience 16:41:59 Seems like it, as it's a hard dep there 16:42:07 nothing provides podman-plugins = 2:2.1.0-1.fc33 needed by podman-2:2.1.0-1.fc33.x86_64 16:42:23 yeah I wasn't questioning the finding but more why is it that way? 16:42:34 oh, yeah. so do we want to: 16:42:42 A) passively accept the change 16:42:55 B) try to get the dep relaxed and encourage users to package layer it if they want it? 16:43:16 since package layering is going to be more reliable soon, B is a more viable option 16:43:22 i just filed https://src.fedoraproject.org/rpms/podman/pull-request/38 16:43:43 B++ :) 16:43:48 podman-plugins was a dep of podman for a while, but only recently was the podman-plugins -> dnsmasq dep fixed 16:44:05 we have podman-plugins in FCOS right now 16:44:05 B 16:44:25 Are we ok dropping podman-plugins? The functionality seems quite niche 16:44:28 our selling point is containers, so I'd say ship the functionality... otherwise, I'd advocate dropping docker 16:44:34 anybody want to advocate for a path other than B? 16:44:57 walters: the thing is it doesn't work right now anyway. so strictly speaking, we're not regressing :) 16:45:04 cyberpear: can you elaborate ? 16:45:05 yep, right 16:45:44 I'm fine relaxing to Recommends for Minimization purposes, but I think we should ship all features of the container engines we ship 16:46:13 so you're advocating for A then? 16:46:14 this very functionality was a big conflict though with Kubernetes in the past IIRC 16:46:20 C) actually implement the wanted logic in the CNI plugin 16:46:33 Though I guess that was more the way it was implemented in docker 16:47:05 can we split the dnsmasq package and depend only on what we need? 16:47:16 lucab: I can't make anyone do C) and I don't know of anybody willing to work on it. Do you? 16:47:28 cyberpear: there's nothing else in there right now 16:47:48 dnsmasq package or podman-plugins package ? 16:49:11 I was thinking to split dnsmasq, but haven't looked inside... that's why we removed the capability right? to get rid of it 16:49:46 yeah, we were trying to keep it out of the base in the past (i.e. this ticket) 16:50:13 I haven't looked at splitting the package, but that's also more work to do and not clear if there are real benefits. 16:50:50 * cyberpear reads ticket history 16:52:19 * dustymabe just read ticket history again too 16:53:36 ok so we have A) B) C) and then cyberpear is talking about maybe splitting packages to maybe make things better (D?) 16:53:47 do we want to discuss any of them further? 16:54:31 can we do B while continuing to discuss upstream re. C ? 16:54:38 I think lucab's reference to C was maybe the ideal scenario, but we don't really have control of that. 16:54:45 https://github.com/coreos/fedora-coreos-tracker/issues/186 16:54:45 https://github.com/coreos/fedora-coreos-tracker/issues/186 16:54:49 We're explicitly shipping dnsmasq, which seems like it could go. 16:54:50 jlebon: yep we can definitely 16:54:56 that was a quite 16:55:00 quote 16:55:32 cyberpear: yeah, it was probably inherited from FAH 16:55:47 jlebon: +1 for B while waiting for C. 16:55:49 removed in https://github.com/coreos/fedora-coreos-config/pull/98 16:56:12 cyberpear: https://pagure.io/fedora-atomic/blob/master/f/fedora-atomic-host.json#_93 16:56:38 #proposed We'll try to get the podman team to break the hard requirement of podman on podman plugins and continue the discussion upstream about potentially using a CNI plugin for this. 16:56:55 +1 16:57:00 this is a CNI plugin 16:57:27 lucab: so I should reword to "about potentially using this as a CNI plugin" ? 16:57:48 sorry I'm not fully versed in that realm so my terms are a bit off 16:57:54 it's just one that took the shortcut of shelling out to dnsmasq instead of implementing networking/naming logic 16:58:27 "about potentially revisiting CNI plugin design" 16:58:33 sometimes shortcuts are necessary. we do it all the time :( 16:58:36 lucab: ok let me update 16:58:52 #proposed We'll try to get the podman team to break the hard requirement of podman on podman plugins and continue the discussion upstream about potentially revisiting CNI plugin design. 16:59:28 +1 16:59:36 short term seems most expeditious to maybe split just the dnsmasq binary to its own package and depend on that? then users who need it for something else can later the full package? 17:00:04 I'm not opposed to #proposed, but sounds like more work 17:00:27 cyberpear: which part? the first part is already done if they accept https://src.fedoraproject.org/rpms/podman/pull-request/38# 17:01:11 the "redesign plugin" 17:01:32 to get the functionality without needing dnsmasq 17:02:21 cyberpear: yeah, maybe we can discuss more to see if that would help (i.e. not full dnsmasq package being installed) some of the concerns 17:03:07 either way let's move forward with #proposed for now because we're technically not regressing anything by removing the podman-plugins package 17:03:21 +1 17:03:45 lucab: bgilbert: skunkerk: etc.. anyone else want to +1 -1 ? 17:03:53 +1 17:04:10 ack 17:04:24 #agreed We'll try to get the podman team to break the hard requirement of podman on podman plugins and continue the discussion upstream about potentially revisiting CNI plugin design. 17:04:58 #topic tracker: Fedora 33 rebase work 17:05:03 #link https://github.com/coreos/fedora-coreos-tracker/issues/609 17:05:17 Just popping in on this to see if there is anything new from anyone 17:05:34 I'd like to give an update on f33 progress for the `next` stream 17:05:46 i'm able to do a local build (will post up a PR later today) 17:05:56 systemd-resolvd seems to be working fine 17:06:22 for some reason console-login-helper messages gets in a boot loop so I had to remove those packages in order to continue testing 17:06:54 for some reason zincati wasn't in the f33 repos, but there is a new rpm build that needs to be done for the release that went out yesterday so I'm just going to wait on that 17:07:29 other than that most things look good. Did notice some selinux denials, but that's probably just "early in the release cycle" stuff 17:07:39 nice 17:08:51 oh.. and I opened this bug against networkmanager 17:08:53 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/539 17:08:55 once you have the PR up i can help chase down hiccups 17:09:10 definitely a change or two in the nm-initrd-generator that we need to make sure don't cause regressions 17:10:07 anything else for this topic? 17:11:15 #topic open floor 17:12:26 #info the stable stream release 32.20200907.3.0 went out this morning with recent kernel fixes 17:12:34 thanks cverna for running the release 17:12:42 thanks lucab for reviews 17:12:53 cverna++ lucab++ 17:12:53 jlebon: Karma for cverna changed to 26 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 17:12:55 with turbo-boost 17:13:01 "went out with a bang" 17:13:10 jlebon: haha, certainly did 17:13:28 cverna++ 17:14:00 any other topics before we close out the meeting? 17:14:33 this ticket came in yesterday: https://github.com/coreos/fedora-coreos-tracker/issues/628 17:15:05 and i think most of those we don't want, though i do feel like strace would be worth shipping 17:15:26 this came up in the past too. but anyway, we can discuss in the ticket 17:15:45 (for comparison, RHCOS does ship strace) 17:15:54 jlebon: +1 17:15:58 +1 should I add a meeting label for next week or do you want to bring it up today? 17:16:16 let's discuss in ticket for now? 17:16:18 maybe next week since it just came in? 17:16:24 SGTM 17:17:48 bgilbert: should we maybe discuss https://github.com/coreos/fedora-coreos-tracker/issues/625 ? 17:18:15 I don't think there's much to discuss there? 17:18:46 the biggest thing to me is.. is there agreement on whether we should or shouldn't have a "latest" link ? 17:18:55 I wasn't sure 17:19:01 depends what you mean by "link" 17:19:15 a forwarder for iPXE makes some sense to me 17:19:21 anyone could actually write that, it doesn't have to be us 17:19:39 if we publish one, we're responsible for its uptime, though 17:19:47 i.e. if it goes down, boots will fail 17:19:51 would this be something useful for packet, or do they mirror our artifacts? 17:20:03 I believe they mirror 17:20:09 they did for CL anyway 17:20:45 seems like it could be valuable... then you could probably link it into something like netboot.xyz 17:20:58 bgilbert: so if I just wanted to wget http://foo.com/get-latest-fcos-stable-qcow2 (not using coreos-installer), would you support that? 17:21:05 even if it redirected 17:21:49 with the redirection I guess you'd get the versioned filename 17:22:18 right, unless there is an option to your client to specify the name of the output file curl > foo.qcow2 17:22:45 we did this for RHCOS for a while, and honestly it's kinda messy 17:23:00 curl has --remote-name 17:23:06 jlebon: how so? 17:23:06 I just wasn't sure if it's something we wanted to do and just haven't done it yet, or if there were good reasons not to 17:23:22 well it was messier there, because we also made curl decompress on the fly 17:23:37 we can't do that here because of signing 17:23:39 yeah, that was the confusing part ^^ 17:24:23 we'd want to design the URL layout thoughtfully, and we'd be responsible for the uptime, but... 17:24:28 yeah, I think it could make sense 17:24:33 +1 17:24:41 * cyberpear often uses curl -R in other contexts 17:25:12 how hard to make it part of the release process to set a static redirect? 17:25:14 cyberpear: ouuh neat, TIL 17:25:44 so more or less "We'd like to do this in the future and we'll need to put some thought into the design and then implement it in collaboration with Fedora's infrastructure team" 17:25:48 cyberpear: I'm hesitant to have multiple sources of truth 17:25:58 better to have a service that reads the single source of truth 17:26:03 as e.g. the download page does now 17:26:34 dustymabe: sgtm 17:26:39 +1 17:26:53 well that was a good use of the extra time I'd say. :) 17:26:59 anything else before I close out the meeting? 17:27:07 i'd be interested to see a use case outside of iPXE where it wouldn't be trivial to just pull down the JSON and parse it from there 17:27:19 right, that's the other side of it 17:27:25 it'd be nifty for sure. but how necessary is it? 17:27:28 jlebon: digital ocean? 17:27:30 for downloadable artifacts we should generally be encouraging `coreos-installer download` 17:27:34 anyway, we can chat in the ticket 17:27:37 because it verifies sigs 17:27:52 +1 for signature verification 17:27:58 so actually, yeah, I'll walk my sgtm back a bit 17:28:00 lucab: can you comment in the ticket? 17:28:20 so I *shouldn't* post that to the ticket? 17:28:25 we can start with use cases where it clearly makes sense, with room to expand, but maybe not implement for all artifacts up front 17:28:27 jlebon: I think we are on a topic not very different from https://github.com/coreos/coreos-installer/issues/202#issuecomment-683647313 17:29:19 although, with a completely different usecase 17:29:21 lucab: yeah, kinda 17:29:27 bgilbert: +1 17:29:34 i.e. pinned vs free-floating the latest version 17:29:36 dustymabe: feel free to post, let's just keep that caveat 17:30:06 bgilbert: what's the caveat specifically? I'll add it 17:30:19 oh that we encourage coreos-installer download? 17:30:34 the caveat is: let's start by implementing redirectors for resources where GPG/hash verification cannot happen 17:30:41 e.g. iPXE and DO 17:30:56 but for now, not implement it for cases where we'd prefer people use `c-i download` 17:31:15 ok i'll try to reflect that 17:31:18 +1 17:31:37 ok i'll close things out now. thanks all for coming! 17:31:40 #endmeeting