15:04:09 #startmeeting fedora_cloud_meeting 15:04:09 Meeting started Thu Aug 31 15:04:09 2023 UTC. 15:04:09 This meeting is logged and archived in a public location. 15:04:09 The chair is davdunc. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 15:04:09 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:04:09 The meeting name has been set to 'fedora_cloud_meeting' 15:04:18 #topic roll call 15:05:22 .hello2 15:05:23 mhayden: mhayden 'Major Hayden' 15:05:29 #chair mhayden 15:05:29 Current chairs: davdunc mhayden 15:05:34 .hello 15:05:34 nzwulfin: (hello ) -- Alias for "hellomynameis $1". 15:05:42 guys, how may I join the call here? 15:05:45 #chair nzwulfin 15:05:45 Current chairs: davdunc mhayden nzwulfin 15:05:47 .hello nzwulfin 15:05:47 .hello 4sokol 15:05:47 nzwulfin: Sorry, but user 'nzwulfin' does not exist 15:05:50 VSokolenko: 4sokol 'Vladimir Sokolenko' 15:06:04 #chair 4sokol 15:06:04 Current chairs: 4sokol davdunc mhayden nzwulfin 15:06:07 one of these days i'll remember my FAS the first try 15:06:26 VSokolenko you are in! 15:06:32 .hello mmicene 15:06:33 nzwulfin: mmicene 'Matt Micene' 15:07:18 excellent. 15:08:06 #topic actions from last meeting 15:08:34 #action davdunc +friends hackfest on Azure Image support 15:09:03 mhayden: it seems like this is something we should be able to do with os-build now, yes? 15:09:14 or are we still awaiting the btrfs support. 15:09:39 we are still waiting on btrfs support 15:09:51 however, there is a lot of interim work that can be done in the meantime to get things wired up 15:10:12 yep. we can do it with kiwi now and we need that for the WSL as well. 15:11:00 will kiwi handle the upload/import at providers? 15:11:02 let's put some time on the schedule in the next week for the config. 15:11:41 no. We still need work there. 15:12:16 it sounds like pbrobinson has some knowledge here and has given me some tips on things to try 15:12:27 we might be able to send him some cookies in exchange for help 😉 15:12:35 :) sounds good. 15:13:10 I spoke to him the other day about adding composable builds and the btrfs thing. 15:14:17 if that's what gets us a repeatable upload to Azure before F39 release, cookies are just a start! 15:15:47 it sounded like you had some knowledge here that we want to capture as well. 15:15:55 you == mhayden 15:15:58 :) 15:16:14 hah yes, i've done it with image builder myself in Fedora several times, and we have osbuild in koji already 15:16:21 Fedora Azure images, i mean 15:16:39 perfect. Can we just turn it on for the release? 15:17:04 or are you building a different image? 15:17:10 we _could_ generate an Azure-compatible image with osbuild today (ondrej put one in last week) but we're missing btrfs 15:17:14 everything else is fine 15:17:46 pbrobinson said that pungi would poke koji to make the build, but i doubt we can get that in before F39 goes out 15:17:51 unless you know something differently 15:17:58 * mhayden is in two meetings simultaneously 15:18:53 well. . . I think that's a way to do it, but it's also a way for the btrfs support to be de-prioritized. 15:19:55 true. perhaps this is a good thread for the ML and bring in some osbuild folks on that 15:20:06 It seems like we can handle this with the Azure collection in ansible with the btrfs in-tact. 15:21:05 agreed. 15:21:59 I think the ML is a great place to determine what our timeline is on the support. 15:22:41 okay, i can start a thread 15:22:52 super. 15:24:37 Alright. 15:25:25 * upload and test images for Azure Marketplace 15:25:52 i have images for testing with btrfs in my account, but haven't moved them to the Fedora account. 15:26:05 with btrfs, we are good 15:26:57 I am not testing nightlies at the moment though. 15:27:35 I believe also that osbuild has some form of cloud push functionality but I'm far from expert on those bits 15:27:37 👍 15:27:52 definitely does pbrobinson 15:28:13 it's pretty sophisticated in the way that it handles the azure uploads from what I understand 15:28:21 I am actually today looking at some partition related things in osbuild so I'm practically the expert there now (LOL!!!) 15:28:30 haha. 15:28:34 yes, and it's what RHEL uses 15:28:40 yes, i use osbuild-composer to push directly to cloud and it's kinda nifty 15:29:23 well, even if we don't build the image in the os-build, can't we just push it to Azure using the composer? 15:29:37 * davdunc thinks this is the most important topic of the week. 15:30:00 I want to get this resolved and on the happy path for F39. 15:30:13 heyo 15:30:20 there he is! 15:30:28 #chair dustymabe 15:30:28 Current chairs: 4sokol davdunc dustymabe mhayden nzwulfin 15:30:36 * dustymabe also in two meetings - grab my attention if there's something that needs it! 15:31:10 dustymabe: all good. Understand that we can 15:31:38 can't all be where we want to be all the time. :) namely, "in one meeting at a time" 15:32:07 okay, so . . . 15:32:50 #action davdunc to work with mhayden to determine if we can use the composer separately from the image build for the Azure uploads 15:33:53 same thing is applicable to OCI 15:34:25 #action davdunc to work with mhayden to determine if we can use the composer separately from the image build for the OCI uploads. 15:34:31 i believe osbuild/osbuild-composer handles builds/uploads there, but i'd have to double check 15:34:42 our QCOW2 that we publish in the compose works well on OCI 15:34:42 it doesn't handle btrfs. 15:34:46 (without modifications) 15:34:59 right, no btrfs 15:34:59 let's keep our build system if we can until we have btrfs support. 15:35:11 but the qcows we already make are just fine for OCI 15:35:31 yea. they use cloud-config so we are set there. 15:35:51 osbuild/IB doesn't support btrfs because? 15:35:51 OCI is pretty forgiving on the formats they'll take last time i looked at them 15:36:10 dustymabe: just hasn't been prioritized yet since RHEL doesn't have btrfs 15:36:28 but i think someone on the osbuild team has enumerated what needs to be completed 15:36:30 dustymabe: yes. 15:36:38 https://github.com/osbuild/osbuild/blob/main/stages/org.osbuild.mkfs.btrfs exists ? 15:36:43 yes to both statements. 15:36:55 i was told there's a bug in there to fix 15:36:57 it does, but it's not fully functional. 15:37:17 ahh - open issue somewhere maybe? 15:37:30 "fix a bug" is a much lower bar than "implement it from scratch" 15:37:37 #link https://github.com/osbuild/osbuild/blob/main/stages/org.osbuild.mkfs.btrfs 15:37:39 might be this: https://github.com/osbuild/osbuild/issues/517 15:37:53 isn't there an open issue to have workstation use IB for image building? doesn't workstation use btrfs? 15:38:08 let's get an email thread going with a few folks from the osbuild folks and get their input 15:38:12 #link https://github.com/osbuild/osbuild/issues/517 15:38:15 might be able to influence their timelines 😜 15:39:42 yea I think that's the best idea there. I am hoping that someone from Meta will be able to jump on anything related to btrfs directly. 15:40:39 it would be great to have parity. pbrobinson any roadmap on WSL in the tool? 15:41:44 alright. that's probably enough to keep us rolling. 15:43:03 That takes care of two issues in our meetings issues. 15:43:18 #link https://pagure.io/cloud-sig/issue/400 15:43:26 #link https://pagure.io/cloud-sig/issue/399 15:44:19 #topic Provide unversioned cloud images 15:44:32 #link https://pagure.io/cloud-sig/issue/396 15:44:57 What doe you think of a "latest" version? 15:45:17 gonna give this topic 4 minutes at most . 15:45:47 hmm, that's an interesting request, but i don't know how that would work at a cloud provider 15:46:23 I think that having a "latest" is something that just happens on GCP and then Azure Marketplace is the same. 15:46:26 i mean, i like the way it works for containers where i can get quay.io/fedora/fedora:latest 15:46:45 kubevirt works like that too :) 15:46:58 quay.io/fedora/fedora-coreos-kubevirt:stable 15:47:03 the name changes though and I think that the hope was that we could make a single search work. 15:47:08 this one gets tricky since each cloud provider has support for certain things 15:47:19 exactly. 15:47:32 davdunc: what's WSL? 15:47:35 on Amazon EC2, there are AMI public parameters. 15:47:48 WSL = Windows Subsystem for Linux 15:48:36 re: Latest, it could also be a qcow we have in the downloads that always provides the latest release. 15:48:58 as right now, we don't have a naming convention that is just the most recent. 15:49:16 in that case, it could just be a symlink to the file. 15:49:29 looks like someone has already done WSL support, there's at least a WSL image type 15:49:59 we want an official one. It's not one we build 15:50:08 https://github.com/osbuild/images/commit/d7bcb358b0cd33a7b9957ed35fbe93ede676daf5 15:50:14 got bumped by the web chat 😭 15:50:43 LOL! Awesome! 15:51:33 I think it's a big help to have that consistency. I know that you don't have to use it pbrobinson, but I would like to use it and it's not always functional today. 15:52:11 sometimes i have to windoze. 15:52:14 davdunc: I've used it once on arm, but I wanted to check the acronym before I commented 15:52:22 alright. 15:52:30 shouldn't the WSL image be more akin to the Fedora Container image versus the Fedora Cloud image ? 15:52:34 I think the more ways we can allow Fedora to be used, what ever the OS, the better 15:52:56 pbrobinson: +1. 15:53:20 dustymabe: probably, I didn't look at how it was crafted in that commit, just it was there (I saw it earlier digging through other stuff) 15:53:39 dustymabe: the container build should be consistent with the cloud image too. 15:53:55 davdunc: hmm 15:54:10 not in my opinion - for example a container doesn't need cloud-init 15:54:43 right or other tools. 15:54:53 I see what you are driving at. 15:55:03 that's why I was asking :) - just trying to understand what the goal was 15:55:59 yea. WSL doesn't need cloud-init either, but as a team effort, it's a consistent fit with the Cloud Sig goals. 15:56:39 more discussion needed on the latest, but it's something we should look at writing a change proposal to take a look at it in a realistic way. 15:56:57 not going to action it right now, but thought it was worth discussing. 15:57:03 #topic open floor 15:57:39 4sokol this might be a great time to have you introduce yourself 15:57:55 very excited to have you joining us. 15:58:01 * mhayden must depart -- sorry! 15:58:06 bye 15:59:15 I think 4sokol is Matrix only, so probably not getting the ping. 15:59:38 alright. any other topics we need to address or haven't addressed? 16:00:08 anything burning a hole in your pocket or need to get off your chest? 16:00:30 okay. We are out of time. 16:00:35 #endmeeting