2025-04-09 16:30:04 <@siosm:matrix.org> !startmeeting fedora_coreos_meeting

2025-04-09 16:30:14 <@meetbot:fedora.im> Meeting started at 2025-04-09 16:30:04 UTC
2025-04-09 16:30:14 <@meetbot:fedora.im> The Meeting name is 'fedora_coreos_meeting'
2025-04-09 16:30:37 <@siosm:matrix.org> !topic roll call
2025-04-09 16:30:40 <@ydesouza:fedora.im> !hi
2025-04-09 16:30:42 <@zodbot:fedora.im> Yasmin Valim de Souza (ydesouza)
2025-04-09 16:31:10 <@hricky:fedora.im> !hi
2025-04-09 16:31:11 <@zodbot:fedora.im> Hristo Marinov (hricky) - he / him / his
2025-04-09 16:31:14 <@siosm:matrix.org> !hi
2025-04-09 16:31:16 <@jbtrystram:matrix.org> !hi @
2025-04-09 16:31:17 <@zodbot:fedora.im> Timothée Ravier (siosm) - he / him / his
2025-04-09 16:31:19 <@zodbot:fedora.im> Sorry, but Fedora Accounts user '@' does not exist
2025-04-09 16:31:25 <@jbtrystram:matrix.org> !hi :) 
2025-04-09 16:31:27 <@marmijo:fedora.im> !hi
2025-04-09 16:31:30 <@zodbot:fedora.im> Sorry, I can only look up one username at a time
2025-04-09 16:31:30 <@zodbot:fedora.im> Michael Armijo (marmijo)
2025-04-09 16:31:47 <@nemric:relativit.fr> hello
2025-04-09 16:32:10 <@tlbueno:fedora.im> !hi
2025-04-09 16:32:11 <@zodbot:fedora.im> Tiago Bueno (tlbueno)
2025-04-09 16:32:29 <@jbtrystram:matrix.org> !hi
2025-04-09 16:32:31 <@zodbot:fedora.im> Jean-Baptiste Trystram (jbtrystram) - he / him / his
2025-04-09 16:32:33 <@dustymabe:matrix.org> !hi
2025-04-09 16:32:35 <@zodbot:fedora.im> Dusty Mabe (dustymabe) - he / him / his
2025-04-09 16:33:22 <@nemric:relativit.fr> !hi
2025-04-09 16:33:23 <@zodbot:fedora.im> No Fedora Accounts users have the @nemric:relativit.fr Matrix Account defined
2025-04-09 16:33:30 <@mnguyen:fedora.im> !hi mnguyen
2025-04-09 16:33:31 <@zodbot:fedora.im> Michael Nguyen (mnguyen)
2025-04-09 16:33:41 <@siosm:matrix.org> Make sure to add the meeting tags to topics that you want to discuss. We only have one right now
2025-04-09 16:34:05 <@aaradhak:matrix.org> !hi aaradhak 
2025-04-09 16:34:12 <@zodbot:fedora.im> Sorry, I can only look up one username at a time
2025-04-09 16:34:14 <@ravanelli:matrix.org> !hi ravanelli
2025-04-09 16:34:17 <@zodbot:fedora.im> Renata Ravanelli (ravanelli)
2025-04-09 16:35:31 <@siosm:matrix.org> !topic Action items from last meeting
2025-04-09 16:35:45 <@siosm:matrix.org> I don't see any actions in the last meeting log
2025-04-09 16:35:48 <@siosm:matrix.org> !link https://discussion.fedoraproject.org/t/fedora-coreos-community-meeting-minutes-2025-04-02/148466
2025-04-09 16:36:12 <@siosm:matrix.org> !topic Review Fedora 42 Release Schedule
2025-04-09 16:36:18 <@siosm:matrix.org> !link https://fedorapeople.org/groups/schedule/f-42/f-42-key-tasks.html
2025-04-09 16:36:55 <@siosm:matrix.org> We are in final freeze. Does anyone has anything in mind that we need to do?
2025-04-09 16:37:47 <@dustymabe:matrix.org> !info we are releasing `next` weekly now that we are in Final Freeze 
2025-04-09 16:38:14 <@dustymabe:matrix.org> We probably need a representative to join the Go/No Go meetings on Thursdays 
2025-04-09 16:38:35 <@siosm:matrix.org> Ah yes, indeed
2025-04-09 16:39:00 <@siosm:matrix.org> From https://github.com/coreos/fedora-coreos-tracker/issues/1851, it looks like we did not yet set a barrier release for the last N-1 next release
2025-04-09 16:39:12 <@dustymabe:matrix.org> Hypothetically F42 could GA next Tuesday
2025-04-09 16:39:33 <@dustymabe:matrix.org> hmm travier I did that, but maybe I forgot to update something 
2025-04-09 16:39:33 <@siosm:matrix.org> https://github.com/coreos/fedora-coreos-streams/pull/1039 > looks like we did, ticking the bix
2025-04-09 16:39:40 <@siosm:matrix.org> https://github.com/coreos/fedora-coreos-streams/pull/1039 > looks like we did, ticking the box
2025-04-09 16:39:48 <@dustymabe:matrix.org> https://github.com/coreos/fedora-coreos-streams/pull/1039
2025-04-09 16:39:58 <@marmijo:fedora.im> I can attend the go/no-go meetings
2025-04-09 16:41:00 <@dustymabe:matrix.org> One thing we haven't done this cycle (all the way at the top of the rebase tracker ticket) is do an evaluation of the package additions/removals
2025-04-09 16:41:10 <@ydesouza:fedora.im> I will be doing the next FCOS release. Since its tha F42 GA, there is any concerns or things that I should know about it?
2025-04-09 16:41:12 <@dustymabe:matrix.org> while that's not strictly necessary, it is a nice sanity check
2025-04-09 16:41:27 <@dustymabe:matrix.org> Yasmin Valim de Souza: it *may* be F42 GA, we don't know yet
2025-04-09 16:41:42 <@dustymabe:matrix.org> if it is, we'll partner with you heavily 
2025-04-09 16:42:05 <@ydesouza:fedora.im> Nice! Thank you!
2025-04-09 16:43:18 <@siosm:matrix.org> Is anyone up to doing an update from F41 to F42 to get a list of packages to investigate?
2025-04-09 16:43:46 <@siosm:matrix.org> I've created https://github.com/coreos/fedora-coreos-tracker/issues/1921
2025-04-09 16:43:47 <@siosm:matrix.org> !link https://github.com/coreos/fedora-coreos-tracker/issues/1921
2025-04-09 16:44:23 <@dustymabe:matrix.org> I can get the additions/removals list pretty easily. The harder part is going through them to evaluate 
2025-04-09 16:44:37 <@dustymabe:matrix.org> marmijo: may have the list handy too :) 
2025-04-09 16:45:03 <@siosm:matrix.org> I can help with the evaluation :)
2025-04-09 16:45:17 <@marmijo:fedora.im> I'm sure I can get that fairly easily. I can help with this!
2025-04-09 16:45:54 <@zodbot:fedora.im> dustymabe has already given cookies to marmijo during the F41 timeframe
2025-04-09 16:46:01 <@zodbot:fedora.im> dustymabe has already given cookies to siosm during the F41 timeframe
2025-04-09 16:46:17 <@zodbot:fedora.im> jbtrystram gave a cookie to dustymabe. They now have 190 cookies, 2 of which were obtained in the Fedora 41 release cycle
2025-04-09 16:46:22 <@dustymabe:matrix.org> Foo. Zodbot, cookies should be an infinite resource
2025-04-09 16:46:37 <@zodbot:fedora.im> ravanelli gave a cookie to siosm. They now have 33 cookies, 4 of which were obtained in the Fedora 41 release cycle
2025-04-09 16:46:37 <@zodbot:fedora.im> ravanelli gave a cookie to dustymabe. They now have 191 cookies, 3 of which were obtained in the Fedora 41 release cycle
2025-04-09 16:46:40 <@zodbot:fedora.im> ravanelli gave a cookie to marmijo. They now have 10 cookies, 4 of which were obtained in the Fedora 41 release cycle
2025-04-09 16:46:58 <@jbtrystram:matrix.org> why not do that instead of the community meeting next week ?
2025-04-09 16:46:59 <@siosm:matrix.org> :)
2025-04-09 16:47:02 <@zodbot:fedora.im> jbtrystram gave a cookie to marmijo. They now have 11 cookies, 5 of which were obtained in the Fedora 41 release cycle
2025-04-09 16:47:04 <@zodbot:fedora.im> jbtrystram gave a cookie to siosm. They now have 34 cookies, 5 of which were obtained in the Fedora 41 release cycle
2025-04-09 16:47:16 <@zodbot:fedora.im> marmijo gave a cookie to dustymabe. They now have 192 cookies, 4 of which were obtained in the Fedora 41 release cycle
2025-04-09 16:47:16 <@zodbot:fedora.im> marmijo gave a cookie to siosm. They now have 35 cookies, 6 of which were obtained in the Fedora 41 release cycle
2025-04-09 16:47:30 <@siosm:matrix.org> we need to do that before next week in case F42 is GA next week
2025-04-09 16:47:44 <@jbtrystram:matrix.org> wow, Dusty got 2 cookies this cycles, for 190 cookies total. That means you have been there since fedora -52 !
2025-04-09 16:47:47 <@siosm:matrix.org> Ideally this is a "now" thing as the no/no-go is tomorrow
2025-04-09 16:47:51 <@jbtrystram:matrix.org> (on average)
2025-04-09 16:48:17 <@zodbot:fedora.im> ydesouza has already given cookies to marmijo during the F41 timeframe
2025-04-09 16:48:19 <@zodbot:fedora.im> ydesouza gave a cookie to siosm. They now have 36 cookies, 7 of which were obtained in the Fedora 41 release cycle
2025-04-09 16:49:39 <@siosm:matrix.org> ok, let's move to the next topic
2025-04-09 16:49:49 <@siosm:matrix.org> !topic coordination with Fedora Infrastructure on datacenter move in June 2025
2025-04-09 16:49:54 <@siosm:matrix.org> !link https://github.com/coreos/fedora-coreos-tracker/issues/1919
2025-04-09 16:50:07 <@dustymabe:matrix.org> 👋 nirik 
2025-04-09 16:50:09 <@siosm:matrix.org> nirik is here if we have questions :)
2025-04-09 16:50:19 <@nirik:matrix.scrye.com> hello
2025-04-09 16:50:51 <@siosm:matrix.org> We can probably move "as soon as" the new cluster is up?
2025-04-09 16:50:53 <@nirik:matrix.scrye.com> I think basically the choices are a) move in late may, or b) move in mid june.
2025-04-09 16:50:58 <@nirik:matrix.scrye.com> yeah...
2025-04-09 16:51:10 <@siosm:matrix.org> but we need access to the builders
2025-04-09 16:51:26 <@nirik:matrix.scrye.com> How do you access builders currently?
2025-04-09 16:51:30 <@dustymabe:matrix.org> let's dig into this just a little more 
2025-04-09 16:51:49 <@dustymabe:matrix.org> in the new DC I think we might have enough hardware to get a dedicated ppc64le machine? 
2025-04-09 16:52:04 <@dustymabe:matrix.org> if that's the case we could have it set up and use when we do the migration 
2025-04-09 16:52:17 <@dustymabe:matrix.org> if that's the case we could have it set up and use when we do the migration (could be May) 
2025-04-09 16:52:55 <@nirik:matrix.scrye.com> no. In the new datacenter we are hoping to have power10's... but there will be only 2 of them for a bunch of uses. We can (and I was planning on) giving you a lpar on one...
2025-04-09 16:53:02 <@nirik:matrix.scrye.com> but you can't have an enitre machine. ;)
2025-04-09 16:53:38 <@dustymabe:matrix.org> hmm i'm still pretty ignorant about the architecture I guess. I thought lpar was a s390x thing 
2025-04-09 16:53:39 <@nirik:matrix.scrye.com> some of this is handwavy, because I don't have access to the new machines yet. ;) But this is my planning at least
2025-04-09 16:54:24 <@nirik:matrix.scrye.com> I think its a ibm thing. ;)
2025-04-09 16:54:49 <@dustymabe:matrix.org> anyway - the way we connect to different things is via SSH so hypothetically our ppc64le builder could remain in place where it is and our pipeline could move to the new DC
2025-04-09 16:54:56 <@dustymabe:matrix.org> as long as SSH still worked 
2025-04-09 16:55:43 <@nirik:matrix.scrye.com> we could possibly make that work. A new power10 lpar would be nicer of course (I would hope it would be a faster for one thing)
2025-04-09 16:56:23 <@nirik:matrix.scrye.com> are your builds cpu or i/o bound? or both like other builds?
2025-04-09 16:56:26 <@dustymabe:matrix.org> 1. coreos-ostree-importer
2025-04-09 16:56:26 <@dustymabe:matrix.org> 2. fedora-ostree-pruner
2025-04-09 16:56:26 <@dustymabe:matrix.org> the only other question I have is related to our few "agents" that run and do access the OSTree repo
2025-04-09 16:56:26 <@dustymabe:matrix.org> 
2025-04-09 16:56:44 <@dustymabe:matrix.org> nirik: on ppc - i'm not actually sure 
2025-04-09 16:57:12 <@dustymabe:matrix.org> the tests are probably more I/O bound than CPU bound (we test installs which involves a lot of disk I/O) 
2025-04-09 16:57:41 <@nirik:matrix.scrye.com> yeah, so storage. If we moved you, we would move storage to the new place too... I should perhaps look at that and see if it has any entanglements with non moved stuff.
2025-04-09 16:58:23 <@ravanelli:matrix.org> Does this p10 support kvm?
2025-04-09 16:58:36 <@dustymabe:matrix.org> it's a unified OSTree repo
2025-04-09 16:58:36 <@dustymabe:matrix.org> "move storage"
2025-04-09 16:58:36 <@dustymabe:matrix.org> 
2025-04-09 16:58:36 <@dustymabe:matrix.org> but we aren't the only users of that storage ?
2025-04-09 16:58:36 <@dustymabe:matrix.org> 
2025-04-09 16:58:59 <@nirik:matrix.scrye.com> it's complicated. ;) You mean for nested virt?
2025-04-09 16:59:39 <@ravanelli:matrix.org> Yeah! I don't know how the new p10 are supporting it, if it is a matter of firmware our p10 model
2025-04-09 16:59:43 <@nirik:matrix.scrye.com> yeah, thinking about it, storage might mess this early plan up. ;( Since we still need it in the old dc for atomic desktops, etc
2025-04-09 17:00:10 <@dustymabe:matrix.org> nirik: the early plan can still happen, we just need to leave those two services where they currently are until storage moves 
2025-04-09 17:00:17 <@dustymabe:matrix.org> everything else can move 
2025-04-09 17:00:37 <@nirik:matrix.scrye.com> nested virt should work. The layers are a but confusing with power stuff... there are layers
2025-04-09 17:01:12 <@nirik:matrix.scrye.com> dustymabe: but you need to write your composes? or ?
2025-04-09 17:01:30 <@nirik:matrix.scrye.com> or the importer does that work?
2025-04-09 17:02:04 <@dustymabe:matrix.org> nirik: we shove everything in s3 first and then send a fedmsg that the coreos-ostree-importer picks up and processes.. it pulls the commit from s3 and imports it into the ostree repo 
2025-04-09 17:02:19 <@nirik:matrix.scrye.com> ah ha. great. then yes...
2025-04-09 17:02:21 <@dustymabe:matrix.org> so our pipeline can actually live in a different place than the importer 
2025-04-09 17:03:19 <@nirik:matrix.scrye.com> ok, cool. So from my perspective, I would like to move anything thats independent as soon as I can/before the switch... that will mean less stuff in the move week to worry about.
2025-04-09 17:03:32 <@dustymabe:matrix.org> 
2025-04-09 17:03:32 <@dustymabe:matrix.org> https://fedoraproject.org/wiki/Changes/CoreOSStopPublishingOSTree
2025-04-09 17:03:32 <@dustymabe:matrix.org> i'll note that in F43+ we'll no longer be pushing to the OSTree repo
2025-04-09 17:04:09 <@dustymabe:matrix.org> nirik: at what point do you think the new openshift cluster will be up and ready for workloads? 
2025-04-09 17:04:19 <@ravanelli:matrix.org> Yeah, nested virt is a new thing for P10s, before it did not support it at all, but now it does. How? I don't know, my guess is only a matter of firmware
2025-04-09 17:05:02 <@nirik:matrix.scrye.com> I am hoping early mayish... but it's subject to my getting access to the hardware, getting enough infra setup to install, etc...
2025-04-09 17:05:28 <@nirik:matrix.scrye.com> nested virt should be working for you with power9 as well... you just have to tweak the xml to allow it...
2025-04-09 17:05:29 <@dustymabe:matrix.org> +1 - keep us in the loop
2025-04-09 17:05:39 <@dustymabe:matrix.org> we're happy to start moving stuff over 
2025-04-09 17:05:44 <@nirik:matrix.scrye.com> definitely can do.
2025-04-09 17:07:59 <@nirik:matrix.scrye.com> will circle back when I know more.
2025-04-09 17:08:09 <@nirik:matrix.scrye.com> should I update that issue/keep it?
2025-04-09 17:08:53 <@dustymabe:matrix.org> I just posed an update to the issue. Ping us back there when you have updates 
2025-04-09 17:09:10 <@dustymabe:matrix.org> if you get access to the p10 we can probably go ahead and start playing with it too 
2025-04-09 17:09:24 <@dustymabe:matrix.org> I just posted an update to the issue. Ping us back there when you have updates 
2025-04-09 17:09:56 <@nirik:matrix.scrye.com> ok. Note there is a ppc64le-test02.fedorainfracloud.org that maintainers have access to if you want to look at anything power10 beforehand.
2025-04-09 17:10:51 <@dustymabe:matrix.org> ehh. I'm more interested in getting FCOS installed on top of it 
2025-04-09 17:10:58 <@nirik:matrix.scrye.com> yeah, fair
2025-04-09 17:10:58 <@dustymabe:matrix.org> which is the OS we use for our builders 
2025-04-09 17:12:01 <@nirik:matrix.scrye.com> Happy to answer any other questions as they occur to you all.
2025-04-09 17:12:09 <@ravanelli:matrix.org> dustymabe:   I'm also curious to see a benchmark with  a P9 build
2025-04-09 17:12:32 <@dustymabe:matrix.org> like comparing performance between p9 and p10 ? 
2025-04-09 17:12:37 <@ravanelli:matrix.org> Yeah
2025-04-09 17:13:08 <@nirik:matrix.scrye.com> at the very least our power9's have slow spinning disk and the power10's should be all ssd.
2025-04-09 17:13:42 <@ravanelli:matrix.org> Seems this nested virt is some kind of emulation on top of the power hypervisor 
2025-04-09 17:14:39 <@ravanelli:matrix.org> Just curious to see, we can also ask Mick helps, he was working I guess to test it as well vs P9
2025-04-09 17:14:52 <@nirik:matrix.scrye.com> yeah, there's a aix like hypervisor -> lpars -> etc...
2025-04-09 17:15:11 <@nirik:matrix.scrye.com> but it's all a bit murky without the actual hardware to look at.
2025-04-09 17:21:14 <@siosm:matrix.org> OK, looks like there is plenty to do but no immediate blockers
2025-04-09 17:21:20 <@nirik:matrix.scrye.com> anyhow thats all I had. :) thanks for hearing me out
2025-04-09 17:21:28 <@siosm:matrix.org> Coordinating in the issue tracker is best 
2025-04-09 17:21:45 <@siosm:matrix.org> Thanks for keeping the infra working for all of us!
2025-04-09 17:22:00 <@siosm:matrix.org> Coordinating the next steps in the issue tracker is best 
2025-04-09 17:22:20 <@zodbot:fedora.im> siosm gave a cookie to kevin. They now have 724 cookies, 32 of which were obtained in the Fedora 41 release cycle
2025-04-09 17:22:26 <@zodbot:fedora.im> ravanelli gave a cookie to kevin. They now have 725 cookies, 33 of which were obtained in the Fedora 41 release cycle
2025-04-09 17:22:32 <@zodbot:fedora.im> jbtrystram gave a cookie to kevin. They now have 726 cookies, 34 of which were obtained in the Fedora 41 release cycle
2025-04-09 17:22:51 <@siosm:matrix.org> !topic Open Floor
2025-04-09 17:23:25 <@zodbot:fedora.im> tlbueno gave a cookie to kevin. They now have 727 cookies, 35 of which were obtained in the Fedora 41 release cycle
2025-04-09 17:23:39 <@siosm:matrix.org> I had a good discussion with a person from Akamai Cloud (formerly Linode) so we may get some credits and could start making image for this cloud as well. We'll see how this goes.
2025-04-09 17:26:00 <@siosm:matrix.org> !link https://github.com/coreos/fedora-coreos-tracker/issues/1701
2025-04-09 17:30:00 <@siosm:matrix.org> Alright, if there is nothing else, I'll close this one
2025-04-09 17:30:11 <@siosm:matrix.org> !endmeeting