2025-02-12 16:31:19 <@apiaseck:matrix.org> !startmeeting fedora_coreos_meeting
2025-02-12 16:31:21 <@meetbot:fedora.im> Meeting started at 2025-02-12 16:31:19 UTC
2025-02-12 16:31:22 <@meetbot:fedora.im> The Meeting name is 'fedora_coreos_meeting'
2025-02-12 16:32:01 <@marmijo:fedora.im> !hi
2025-02-12 16:32:03 <@zodbot:fedora.im> Michael Armijo (marmijo)
2025-02-12 16:32:08 <@jdoss:beeper.com> !hi
2025-02-12 16:32:09 <@siosm:matrix.org> !hi
2025-02-12 16:32:10 <@zodbot:fedora.im> Joe Doss (jdoss)
2025-02-12 16:32:18 <@zodbot:fedora.im> Timothée Ravier (siosm) - he / him / his
2025-02-12 16:32:21 <@hricky:fedora.im> !hi
2025-02-12 16:32:23 <@zodbot:fedora.im> Hristo Marinov (hricky) - he / him / his
2025-02-12 16:32:31 <@nemric:relativit.fr> hi :)
2025-02-12 16:32:41 <@apiaseck:matrix.org> !topic roll call
2025-02-12 16:32:49 <@jdoss:beeper.com> The reports of my death are greatly exaggerated. /waves
2025-02-12 16:32:55 <@dustymabe:matrix.org> !hi
2025-02-12 16:32:57 <@zodbot:fedora.im> Dusty Mabe (dustymabe) - he / him / his
2025-02-12 16:34:11 <@apiaseck:matrix.org> Hey all! Let's start with Action items from the last meeting...
2025-02-12 16:34:15 <@apiaseck:matrix.org> !topic Action items from last meeting
2025-02-12 16:34:39 <@aaradhak:matrix.org> !hi aaradhak
2025-02-12 16:34:41 <@zodbot:fedora.im> Aashish Radhakrishnan (aaradhak)
2025-02-12 16:35:04 <@apiaseck:matrix.org> I don't think there are any, so we have this box ticked. ✅️
2025-02-12 16:35:26 <@apiaseck:matrix.org> !topic Review Fedora 42 Release Schedule
2025-02-12 16:35:33 <@apiaseck:matrix.org> !link https://fedorapeople.org/groups/schedule/f-42/f-42-all-tasks.html
2025-02-12 16:36:32 <@jbtrystram:matrix.org> !hi
2025-02-12 16:36:34 <@zodbot:fedora.im> Jean-Baptiste Trystram (jbtrystram) - he / him / his
2025-02-12 16:36:49 <@apiaseck:matrix.org> Since this updated topic comes from dustymabe I will ask if you'd like to introduce this by any chance?
2025-02-12 16:38:02 <@apiaseck:matrix.org> ...or anyone else for that matter? :) 
2025-02-12 16:38:30 <@dustymabe:matrix.org> 👋
2025-02-12 16:38:47 <@dustymabe:matrix.org> This is a task and a proposal.
2025-02-12 16:39:30 <@dustymabe:matrix.org> The proposal is that we add this to our meeting checklist such that we review the current schedule for the Fedora Release under development each week to see if there is anything coming up that we need to do. 
2025-02-12 16:40:01 <@dustymabe:matrix.org> The task is checking the schedule and discussing what we need to do next and if we should find any volunteers to do it.
2025-02-12 16:40:49 <@dustymabe:matrix.org> So right now we are right around item 73
2025-02-12 16:41:11 <@dustymabe:matrix.org> hmm. maybe this link would be a better view: https://fedorapeople.org/groups/schedule/f-42/f-42-devel-tasks.html 
2025-02-12 16:41:23 <@dustymabe:matrix.org> much more succinct :) 
2025-02-12 16:41:48 <@siosm:matrix.org> https://fedorapeople.org/groups/schedule/f-42/f-42-key-tasks.html I generally use the key one
2025-02-12 16:42:22 <@marmijo:fedora.im> +1 from me on adding it to the meeting checklist so we can review the dates and not miss important ones
2025-02-12 16:42:33 <@dustymabe:matrix.org> Change Checkpoint: 100% Code Complete Deadline 	Tue 2025-02-18
2025-02-12 16:42:33 <@dustymabe:matrix.org> ```
2025-02-12 16:42:33 <@dustymabe:matrix.org> ```
2025-02-12 16:42:33 <@dustymabe:matrix.org> 
2025-02-12 16:42:33 <@dustymabe:matrix.org> so right now I think the next thing we need to address is
2025-02-12 16:42:40 <@siosm:matrix.org> +1 to adding to the checklist
2025-02-12 16:43:07 <@dustymabe:matrix.org> Beta Freeze (starts at 1400 UTC) 	Tue 2025-02-18
2025-02-12 16:43:07 <@dustymabe:matrix.org> ```
2025-02-12 16:43:07 <@dustymabe:matrix.org> 
2025-02-12 16:43:07 <@dustymabe:matrix.org> and:
2025-02-12 16:43:07 <@dustymabe:matrix.org> ```
2025-02-12 16:43:52 <@dustymabe:matrix.org> so.. to those who have changes outstanding - it would be nice to get the dev work merged soon
2025-02-12 16:43:57 <@jbtrystram:matrix.org> let's add that to the begin of the meeting schedule so it does not get pushed out if 1 topic takes a bunch of the discussion
2025-02-12 16:45:29 <@marmijo:fedora.im> Beta freeze will happen before the next meeting. It doesn't look like there are any items to be done in the rebase checklist, only at actual beta
2025-02-12 16:46:22 <@apiaseck:matrix.org> !proposal We will add the https://fedorapeople.org/groups/schedule/f-42/f-42-key-tasks.html to the beginning of the meeting schedule
2025-02-12 16:46:22 <@apiaseck:matrix.org> Let's vote on that.
2025-02-12 16:46:50 <@dustymabe:matrix.org> marmijo: right.. but I think it would be good to watch the beta processes closely so that we are really ready.. once they start to get to a point where their confidence level is higher then we should go ahead and prep some things so it's not a rush on Thursday->Monday 
2025-02-12 16:47:00 <@dustymabe:matrix.org> +1 for the proposed 
2025-02-12 16:47:03 <@siosm:matrix.org> +1
2025-02-12 16:47:15 <@aaradhak:matrix.org> +1
2025-02-12 16:47:53 <@apiaseck:matrix.org> Any other votes?
2025-02-12 16:48:03 <@marmijo:fedora.im> +1
2025-02-12 16:48:14 <@ravanelli:matrix.org> !hi ravanelli
2025-02-12 16:48:16 <@zodbot:fedora.im> Renata Ravanelli (ravanelli)
2025-02-12 16:49:06 <@apiaseck:matrix.org> Thank you for the votes.
2025-02-12 16:49:09 <@jbtrystram:matrix.org> +1
2025-02-12 16:49:14 <@apiaseck:matrix.org> !agreed We will add the https://fedorapeople.org/groups/schedule/f-42/f-42-key-tasks.html to the beginning of the meeting schedule
2025-02-12 16:49:35 <@dustymabe:matrix.org> apiaseck: any chance you'd want to PR the fcos meeting action repo to implement that proposal? 
2025-02-12 16:49:45 <@apiaseck:matrix.org> Absolutely
2025-02-12 16:50:00 <@apiaseck:matrix.org> That's now on my TODO list
2025-02-12 16:50:30 <@dustymabe:matrix.org> !action apiaseck to update fcos meeting action to add FN release schedule item on weekly meeting
2025-02-12 16:52:04 <@apiaseck:matrix.org> Shall we discuss the main topic any further, or can we move on?
2025-02-12 16:53:27 <@apiaseck:matrix.org> Ok, moving on...
2025-02-12 16:53:31 <@apiaseck:matrix.org>  !topic Implement Proxmox VE (proxmoxve) Support 
2025-02-12 16:53:38 <@apiaseck:matrix.org> 
2025-02-12 16:53:38 <@apiaseck:matrix.org> 
2025-02-12 16:53:38 <@apiaseck:matrix.org>     !link https://github.com/coreos/fedora-coreos-tracker/issues/1652
2025-02-12 16:53:44 <@jdoss:beeper.com> ‼️
2025-02-12 16:54:01 <@apiaseck:matrix.org> !link https://github.com/coreos/fedora-coreos-tracker/issues/1652
2025-02-12 16:54:32 <@dustymabe:matrix.org> This make me think of [Metal Gear Solid](https://metalgear.fandom.com/wiki/Exclamation_point)
2025-02-12 16:54:41 <@jdoss:beeper.com> You understand me Dusty.
2025-02-12 16:55:56 <@jdoss:beeper.com> I think Proxmox support for FCOS is close. There are just a few things to sort out.
2025-02-12 16:56:33 <@apiaseck:matrix.org> I wasn't here last week, but AFAIK also dustymabe, Jonathan Lebon and jbtrystram did some work on the subject
2025-02-12 16:57:06 <@jdoss:beeper.com> I have an open PR https://github.com/coreos/ignition/pull/2014 that I'd like to get merged. We need to figure out how to do static networking from cloud-init data in the cidata disk. And then I think it is just documentation.
2025-02-12 16:58:52 <@jdoss:beeper.com> and I am willing to do most of the work here but the static networking stuff most likely has to happen in afterburn and my Rust is terrible. 
2025-02-12 16:59:41 <@dustymabe:matrix.org> cc spresti Jonathan Lebon travier 
2025-02-12 16:59:41 <@dustymabe:matrix.org> it seems the open question is whether or not that implementation is something we want to actually do?
2025-02-12 16:59:41 <@dustymabe:matrix.org> 
2025-02-12 16:59:43 <@jdoss:beeper.com> and I am sure I can work with Bri too on things. They have taken this a long way with their work in the tracker ticket.
2025-02-12 17:00:34 <@jdoss:beeper.com> I highly advocate for supporting static networking in Proxmox. It is very normal to set the network configs via cloud-init. Flatcar supports writing out the systemd networkd units from this data. 
2025-02-12 17:01:17 <@jbtrystram:matrix.org> ahem, not for me
2025-02-12 17:02:26 <@siosm:matrix.org> I'm not familiar with the quirks of that platform and there have been a lot of discussions about it in the past so it would be good to review those to make sure thing make sense
2025-02-12 17:02:54 <@jlebon:fedora.im> !hi
2025-02-12 17:02:56 <@zodbot:fedora.im> None (jlebon)
2025-02-12 17:03:03 <@siosm:matrix.org> Ideally, we should document how we are adding support for it in Ignition/Afterburn and the specialties
2025-02-12 17:03:39 <@jdoss:beeper.com> I spent a decent amount of time trying to see if I could use networking settings in kargs and there isn't any support for that in Proxmox unfortunately. Not having networking during the first boot configuration prevents the usage of any ignition over the wire. 
2025-02-12 17:04:12 <@jdoss:beeper.com> so this leaves configuring the network via afterburn with NetworkManger configs unless there is a better way.
2025-02-12 17:04:49 <@jlebon:fedora.im> I haven't looked at the latest discussions in that ticket but https://github.com/coreos/ignition/pull/2014 feels quite odd at first glance
2025-02-12 17:05:14 <@jlebon:fedora.im> i suspect in your workflow, you have full control over the vendor data?
2025-02-12 17:05:37 <@jdoss:beeper.com> So cloud init data normally lives in user-data. Afterburn can get info out of there if we don't clobber it with ignition json
2025-02-12 17:06:01 <@jlebon:fedora.im> yeah... that itself was a compromise given the circumstances
2025-02-12 17:06:48 <@jdoss:beeper.com> vendor-data can be used and has been supported by proxmox. In order to not break flatcar using user-data, we check that file first for json data and use that for ignition things. If it containe the Yamls we check vendor-data next.
2025-02-12 17:06:48 <@jlebon:fedora.im> jdoss: i think it'd be helpful to have a high-bandwidth meeting with folks interested in Proxmox to get agreement on the strategy there
2025-02-12 17:08:11 <@jlebon:fedora.im> I'm wary of continuing to add more Ignition-specific semantics of Proxmox's provisioning mechanisms
2025-02-12 17:08:53 <@dustymabe:matrix.org> I imagine we would want to invite bri? 
2025-02-12 17:09:04 <@jlebon:fedora.im> yeah, that would be great
2025-02-12 17:09:24 <@jdoss:beeper.com> yeah I think they are invested in getting this over the line.
2025-02-12 17:10:15 <@jdoss:beeper.com> I don't think it will take much to sort this out and get some PRs to support static networking.
2025-02-12 17:10:17 <@dustymabe:matrix.org> !action jdoss to organize high bandwidth meeting with jlebon travier spresti and bri to discuss next steps for ignition/afterburn and proxmox static networking
2025-02-12 17:10:43 <@apiaseck:matrix.org> :) I was just typing in the action... thanks 
2025-02-12 17:10:50 <@dustymabe:matrix.org> would we need to include any flatcar folks? 
2025-02-12 17:10:59 <@dustymabe:matrix.org> sorry I should have let you do it! 
2025-02-12 17:11:27 <@jdoss:beeper.com> I mean this is mostly FCOS related. The ignition change doesn't impact their usage because the behavior is the same.
2025-02-12 17:12:09 <@jdoss:beeper.com> and honestly using vendor-data over user-data is better. vendor-data is totally empty and we don't clobber cloud-init data in user-data.
2025-02-12 17:12:12 <@apiaseck:matrix.org> :) I was just typing in the action... thanks!
2025-02-12 17:12:23 <@jlebon:fedora.im> dustymabe: we could extend the invitation, but i think Enix folks might also be interested
2025-02-12 17:12:50 <@jdoss:beeper.com> can people DM me their preferred email addresses to coordinate an invite? 
2025-02-12 17:13:07 <@jdoss:beeper.com> I will track down Bri's email.
2025-02-12 17:15:48 <@apiaseck:matrix.org> Found it on he's gh:  https://www.ibeep.com/contact/
2025-02-12 17:16:04 <@jdoss:beeper.com> Thanks apiaseck 😄
2025-02-12 17:16:39 <@apiaseck:matrix.org> The least I could do :) 
2025-02-12 17:17:11 <@dustymabe:matrix.org> Nice work coordinating multiple upstreams jdoss 
2025-02-12 17:17:20 <@jdoss:beeper.com> I got your email don't worry Dusty...
2025-02-12 17:17:42 <@apiaseck:matrix.org> I think we can move to Open Floor
2025-02-12 17:18:06 <@jdoss:beeper.com> travier spresti anyone have their email addresses?
2025-02-12 17:18:24 <@siosm:matrix.org> I'll send you a dm
2025-02-12 17:18:55 <@jdoss:beeper.com> Thanks!
2025-02-12 17:19:02 <@apiaseck:matrix.org> !topic Open Floor
2025-02-12 17:19:16 <@dustymabe:matrix.org> !info FCOS node count is now over 100k
2025-02-12 17:19:19 <@dustymabe:matrix.org> !link https://discussion.fedoraproject.org/t/fedora-coreos-numbers-02-2025-edition/144475/2
2025-02-12 17:19:54 <@jdoss:beeper.com> That is 🔥
2025-02-12 17:20:35 <@dustymabe:matrix.org> Also FYI I created https://discussion.fedoraproject.org/t/fedora-coreos-numbers-02-2025-edition/144475/2 since we decided last year to implement it and IIUC all that's really left is mostly dotting i's and crossing t's 
2025-02-12 17:21:07 <@dustymabe:matrix.org> I've got a local image building and I'll open a COSA PR soon - maybe I can get travier to test it for me with his docs and the hcloud-image-uploader tool? 
2025-02-12 17:21:27 <@jdoss:beeper.com> I have been running FCOS in production for my personal side projects and we use it at my fulltime job to ship an onprem appliance of our SaaS in a box for Enterprise customers. 
2025-02-12 17:21:33 <@dustymabe:matrix.org> Also FYI I created https://github.com/coreos/fedora-coreos-tracker/issues/1874 since we decided last year to implement it and IIUC all that's really left is mostly dotting i's and crossing t's 
2025-02-12 17:23:29 <@dustymabe:matrix.org> !info watch travier's presentation from FOSDEM 2025: https://floss.social/@siosm/113985367091475495
2025-02-12 17:24:09 <@jdoss:beeper.com> I think Bootc is so cool. 
2025-02-12 17:24:55 <@siosm:matrix.org> I can do that :)
2025-02-12 17:25:26 <@jdoss:beeper.com> I would love to move to a signed image for my work appliance. travier I might pick your brain here 😉
2025-02-12 17:25:57 <@siosm:matrix.org> signed image?
2025-02-12 17:26:17 <@siosm:matrix.org> ah, you mean the FOSDEM talk?
2025-02-12 17:26:25 <@jdoss:beeper.com> Yep!
2025-02-12 17:26:46 <@siosm:matrix.org> it's not ready for FCOS but we are working on it :)
2025-02-12 17:27:10 <@jdoss:beeper.com> I offer myself as tribute for testing.
2025-02-12 17:28:15 <@apiaseck:matrix.org> We are slowly running out of time folks, great conversations - thank you all for attending!
2025-02-12 17:28:52 <@apiaseck:matrix.org> Is there anything else or can we close for today?
2025-02-12 17:29:18 <@apiaseck:matrix.org> !endmeeting