14:02:08 <spotz[m]> #startmeeting RDO meeting - 2025-01-22
14:02:09 <opendevmeet> Meeting started Wed Jan 22 14:02:08 2025 UTC and is due to finish in 60 minutes.  The chair is spotz[m]. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:02:09 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:02:09 <opendevmeet> The meeting name has been set to 'rdo_meeting___2025_01_22'
14:02:22 <spotz[m]> #topic Roll Call
14:02:56 <karolinku[m]> o/
14:03:56 <jcapitao[m]> o/
14:04:34 <spotz[m]> We'll give anyone else a minute to join
14:04:47 <spotz[m]> #link https://etherpad.opendev.org/p/RDO-Meeting
14:04:59 <spotz[m]> Agenda if anyone wants to add anything
14:05:44 <spotz[m]> Topic 1
14:05:49 <spotz[m]> #topic Community poll
14:06:46 <spotz[m]> We had 5 responses for both 9 ad 10 of CentOS Stream and 2 responses of 10 only
14:07:14 <spotz[m]> We had 4 responses for all releases and 3 responses for SLURP only
14:08:25 <spotz[m]> The both question definitely had a community preference towards both looking at the responders for each answer. The SLURP related responses were a mix for both responses
14:10:17 <spotz[m]> Thoughhts?
14:11:31 <jcapitao[m]> and for the puppet-openstack-integration project viability, tkajinam raised concern if we build only SLURP releases
14:12:41 <spotz[m]> Ok so it seems that all is the better option from a technical perspective?
14:13:48 <jcapitao[m]> yes for sure, at least the Trunk repos
14:14:05 <jcapitao[m]> the problem is our capacity to do so
14:15:20 <spotz[m]> Can we put together a what help is needed and how to that we can present as an if you want us to continue this past X release we need help and this is how?
14:16:08 <spotz[m]> I know the 2 Stream versions is a one off every few years(candence could very) but we could also prep for that with a doc as well
14:17:46 <jcapitao[m]> well, we can do this kind of documentation
14:18:50 <jcapitao[m]> the thing is if we commit to do build every release and the 2 Streams for Epoxy, then if nobody shows up to help on that, then we'll have to handle all by ourself
14:18:59 <jcapitao[m]> and there will be issue to fix
14:19:21 <jcapitao[m]> specially on CS10 as it's post GA
14:20:07 <jcapitao[m]> and we are only 2 core maintainer full time
14:20:58 <spotz[m]> SO if we document first, we can put the caveat of we need volunteers to help with these things in order to do all releases going forward?
14:21:46 <jcapitao[m]> yes
14:21:58 <jcapitao[m]> like we commit to build Epoxy on CS10 but not CS9
14:22:59 <jcapitao[m]> if you'd like to have an Epoxy running on CS9, feel free to ping us and we'll help you
14:23:37 <jcapitao[m]> kind of like the "unmaintained" phase in upstream
14:26:12 <spotz[m]> Ok so let me make sure I'm with you we need help to do CS9 epoxy, do we also need help going forward to do Flamingo if we want to do the non-SLURP? Just want to make sure if we put something together to send I'm clear on the ask
14:28:28 <jcapitao[m]> for the non-SLURP releases I'd say we need to keep building it to satisfy p-o-i project
14:28:38 <jcapitao[m]> as we are using it as deployment tool
14:28:51 <spotz[m]> And the resources are there for that?
14:30:20 <jcapitao[m]> yes by reducing the life cycle of our RDO releases
14:30:45 <jcapitao[m]> as soon as upstream put a release in unmaintained status, we'll do the same
14:31:21 <jcapitao[m]> so we'll end up with 4 releases to maintain + master
14:31:26 <jcapitao[m]> wdyt karolinku ?
14:31:36 <spotz[m]> Ok so let's work on documentation on how to build for a Stream release and ask for help. Let's also document how to maintain a release if someone wants to step up to do so but not plan on that actually happening:)
14:32:20 <spotz[m]> If we have the build for stream docs ready we can go ahead and ask for help and work on the other docs when we can as we have a little more time there
14:33:41 <jcapitao[m]> works for me 👍️
14:34:09 <karolinku[m]> release is one problem (effort) and then the maintenance is another
14:36:00 <karolinku[m]> for C9 on Epoxy - I fully agree that we need community help gere
14:36:04 <karolinku[m]> here*
14:36:12 <spotz[m]> Well the dual version is not a regular effort aka every release so lets get help from folks who want both. Then we work on finding folks who want to maintain older releases and if there aren't any we retire them as we do upstream no worries
14:36:30 <karolinku[m]> wrt non-SLURP releasese, im not sure if I understood why it is needed to satisfy p-o-i
14:37:44 <tkajinam> p-o-i uses rdo packages for voting jobs. we have ci with ubuntu but these are non-voting because of its instability (and there are some tricky things sometimes require us to use older versions)
14:38:06 <tkajinam> so if RDO does not ship flamingo for example we have no packages available to test flamingo
14:38:49 <tkajinam> regarding the centos release I understand the situation but may need to sync with you about the timeline of migration. In the past we spent some amount of effort for upgrading centos post release and I'm not very sure that we can complete migration before E
14:39:34 <tkajinam> I mean the expected timeline for Epoxy GA of RDO if you need puppet/packstack test coverage
14:39:42 <tkajinam> given the fact I'm not full time now, as you know
14:40:27 <jcapitao[m]> yeah sure, we'll have to do the same work for packstack as well
14:40:48 <jcapitao[m]> we might validate with packstack only at the beginning if needed, so no rush
14:41:01 <tkajinam> I hope the package changes are not much huge. My current main concern is remaining usage of network-scripts which might need to be replaced by networkmanager hell
14:41:27 <tkajinam> but we'll see details later
14:41:29 <tkajinam> in this cycle
14:41:53 <jcapitao[m]> ah right, we've already hit that network issue :/
14:41:55 <tkajinam> we may also have to wait until base puppet and other modules adopt to c10
14:42:37 <spotz[m]> tkajinam: If we doc how to build c9/c10/etc do you think you and others could contribute?
14:43:14 <karolinku[m]> oh, I just realize how bad may be this networkig stuff:/
14:43:40 <jcapitao[m]> I haven't started digging in the ruby/puppet modules for CS10 TBH (I'm afraid :) )
14:43:56 <jcapitao[m]> I'll do once the base python dependencies built
14:44:47 <tkajinam> spotz[m], I hope I can... but I'm not aware of "others" atm
14:45:13 <spotz[m]> Ok I'll take one hopeful:)
14:48:52 <spotz[m]> Ok so do we have a plan? Doc and then ask for assistance? Worry about ongoing maintenance until later or just retire like upstream if no volunteers?
14:49:18 <jcapitao[m]> I think we have a plan
14:50:41 <jcapitao[m]> for maintenance of CS9 Epoxy it will be "best effort" and retire it if no community help
14:51:20 <jcapitao[m]> but if someone shows up to build it I guess he/she will maintain it
14:51:53 <spotz[m]> Ok I'll try to write something up and share before emailing but I'll leave the how to docs to you and Karolinku
14:52:06 <spotz[m]> I'm going to push us forward so we can get to your other topic
14:52:15 <spotz[m]> #topic CentOS Connect and FOSDEM
14:53:29 <spotz[m]> Connect is Jan 30-31 in Brussels I'll add links to stuff in a sec. Joel is speaking and there is an OKD meetup THursday morning. At FOSDEM there is an OpenStack BoF on Saturday afternoon. OpenStack Birthday party Saturday night
14:53:34 <spotz[m]> #link https://fosdem.org/2025/schedule/event/fosdem-2025-4885-openstack-community-meetup-bof/
14:53:57 <spotz[m]> #link https://connect.centos.org/
14:54:11 <spotz[m]> #link https://www.meetup.com/brussels-openinfra-meetup-group/events/304883862
14:54:20 <spotz[m]> #topic centos10-master Tunk bootstrapping
14:54:54 <jcapitao[m]> just a quick update on https://issues.redhat.com/browse/RDO-392
14:55:13 <jcapitao[m]> we are currently building the dependencies for RDO on CS10
14:55:34 <jcapitao[m]> the effort is tracked on https://etherpad.opendev.org/p/rdo-trunk-centos10-master-bootstrap
14:56:14 <jcapitao[m]> that's it for this stopic
14:56:59 <spotz[m]> #topic Chair for next week
14:57:08 <spotz[m]> I will be in Brussels setting up for COnnect
14:57:39 <jcapitao[m]> me too
14:57:51 <spotz[m]> Ok let's skip then and do Feb 5?
14:58:03 <jcapitao[m]> yes let's dot that
14:58:29 <spotz[m]> That will be the video call
14:59:50 <karolinku[m]> ack
15:00:25 <spotz[m]> Anyone want to volunteer we're at time, also need the watcher
15:00:48 <karolinku[m]> maybe I will be finally able to do whole week of watching ;D
15:01:23 <jcapitao[m]> hopefully :)
15:01:41 <spotz[m]> Ok so watcher is karolinku?
15:01:46 <karolinku[m]> yes
15:02:17 <spotz[m]> Ok and we can decide chair later. Let me close this out
15:02:23 <spotz[m]> #endmeeting