14:00:42 #startmeeting RDO meeting - 2023-04-19 14:00:42 Meeting started Wed Apr 19 14:00:42 2023 UTC and is due to finish in 60 minutes. The chair is jcapitao[m]. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:42 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:42 The meeting name has been set to 'rdo_meeting___2023_04_19' 14:00:47 it's meeting time ! 14:01:07 Merged openstack/ansible-collections-openstack-distgit wallaby-rdo: Explicitely require openstack-ansible-core in EL9 https://review.rdoproject.org/r/c/openstack/ansible-collections-openstack-distgit/+/48347 14:01:32 #topic Roll Call 14:02:17 o/ 14:02:44 Merged openstack/tripleo-validations-distgit wallaby-rdo: Revert "Removing check stage for the package build" https://review.rdoproject.org/r/c/openstack/tripleo-validations-distgit/+/48059 14:02:47 o/ 14:03:00 #chair karolinku amoralej 14:03:00 Warning: Nick not in channel: karolinku 14:03:00 Current chairs: amoralej jcapitao[m] karolinku 14:04:16 o/ 14:04:38 #chair spotz 14:04:38 Current chairs: amoralej jcapitao[m] karolinku spotz 14:07:17 let's start with first and unique topic of the agenda today 14:07:24 #topic Antelope release 14:07:43 #info Antelope was released on April 18 14:07:59 #link https://lists.rdoproject.org/archives/list/dev@lists.rdoproject.org/thread/JUWA4D6E3522AQQCPV46ZGXI5DFV3TDE/ 14:08:10 #link https://lists.rdoproject.org/archives/list/dev@lists.rdoproject.org/thread/JUWA4D6E3522AQQCPV46ZGXI5DFV3TDE/ 14:08:29 We were one day off with the notice from the first RDO release 10 years ago! 14:09:17 happy birthday RDO !! 14:09:40 oh, nice! 14:10:03 how many releases ? 14:10:04 I think we should be really proud of that! I'm tempted to talk to tiger about maybe doing a different image for the contributor SWAG 14:10:13 First was grizzly 14:10:42 give me a sec to count should be 20 I suspect 14:11:03 21 releases if we count from g to a 14:11:09 our baby is growing... :) 14:11:12 Yep 21 with Grizzly 14:12:16 So let me talk to Tiger, besides not getting a food type storage item I haven't looked for the contributor SWAG yet 14:12:38 I have started looking at Ducks for summit though:) 14:13:11 +1 for the custom image ! 14:14:43 I know Tiger is busy getting artwork done for RH Summit but I'll get this on his list to discuss when he's done with those 14:15:10 nice 14:15:14 ok 14:15:34 it'd be cool to get a 10th aniversary special edition 14:17:01 I wish I would have known about the 20 releases too. Thanks to apevec we know about the first release date though:) 14:17:29 :) 14:17:46 i guess he was already around 14:20:13 hehe 14:20:14 I think that's all for this topic 14:20:32 Ok I did drop Tiger an email to think on it but that we'd wait for him to be free 14:20:35 Yep 14:20:37 Merged openstack/tripleoclient-distgit wallaby-rdo: Revert "Ignore unit tests when building tripleoclient" https://review.rdoproject.org/r/c/openstack/tripleoclient-distgit/+/48061 14:20:39 I'll take care of the tempest unpinning after the mtg 14:21:03 thanks 14:21:15 #topic Next Chair 14:21:25 who's willing to chair next week ? 14:22:16 I can take it 14:23:01 Thanks karolinku[m] 14:23:57 #action karolinku will chair next week 14:24:00 thank you 14:24:10 #topic open floor 14:26:32 fyi, i sent a patch to support cloudsig repo in osa 14:26:57 https://review.opendev.org/c/openstack/openstack-ansible-openstack_hosts/+/880473 14:27:05 i still need to fix it 14:27:13 but i hope to get it working 14:27:17 Nice, I saw noonedeadpunk had -1, I'll peek as well once any concerns are resolved 14:28:55 yep, i just was side tracked 14:28:59 but i'll retake it 14:32:06 amoralej: so osa is supporting RDO with the Trunk repos currently ? 14:32:29 yes 14:32:45 osa supports both source and distro installation 14:33:02 when working in distro, they use trunk in ci at least 14:33:13 okk 14:33:21 actually, current default when you use centos9 + distro is trunk zed 14:34:53 oog so we could add OSA to our release criteria! 14:35:05 s/oog/ooh/ 14:35:37 I thought they dropped installing from distro pkgs completely 14:35:55 i'd like to be able to run osa ci jobs 14:36:01 apevec, nop, kolla dropped it 14:36:09 but not osa 14:36:25 heh I mix the two 14:36:35 although source installation support is more widely supported and tested 14:37:21 I think this is good for us if we can get it working 14:37:38 yeah 14:37:47 we will :) 14:38:02 :D 14:38:12 "i guess he was already around" <- FTR I indeed was, even pre-RDO when we were building in EPEL 14:39:13 wow :) 14:39:17 it was Portland Summit where we formally announced RDO as a project 14:40:00 We missed doing something special for the 20th release but I'll try to get something for 10th birthday! 14:40:43 apevec: well, we were thinking about it, but I standed ground that it's good to have distro option:) 14:41:22 though we defenitely don't have much deployments with distro at the moment, and not much interested parties to get this path evolved. 14:41:36 Only limited amount of services are currently supported. 14:44:21 but at very least base services are covered and it's quite straightforward to enroll more services if needed 14:47:03 my position is that, if osa decides to support distro packages with RDO, i'd like to make sure it works as smooth as possible and in the opposite way, testing osa is a good way to validate distro packages works as expected 14:47:34 i see the value of using distro packages vs source, but or course, i'm a distro maintainer :) 14:48:33 hehe 14:48:47 I'd like ppl to be able to choose between opionated methods :D 14:48:50 and i understand supporting two deployment models has bigger effort that maintaining one 14:49:30 And it could be as simple as non-default is less popular as always 14:49:40 yeah, sure 14:50:08 It actually doesn't cost as lot lately, was slightly more turbulent with py2/py3 stuff, but it's not the case anymore 14:50:10 i agree, giving multiple options is always good 14:52:56 One thing I'd love to raise though more with TC hat on, and that is release naming. As since Antelope OpenStack tries to use date-released versions as main identifier (ie 2023.1 for Antelope, 2023.2 for Bobcat). Thus, all branches are named stable/2023.1 etc. 14:53:53 I know we did call it 2023.1 Antelope in the release at least once:) 14:54:26 yep, for the official name i think we should stick to both 14:54:29 well, repos/packages are called antelope from what I got from your email? 14:54:34 as in https://releases.openstack.org/ 14:54:46 wrt repo 14:55:23 sec, I will find document :) 14:55:26 actually, we used name probably because of habit, 14:55:40 but also, note the deliverables directory is using antelope upstream 14:55:46 https://github.com/openstack/releases/tree/master/deliverables 14:55:52 so i understand both are used 14:56:42 https://governance.openstack.org/tc/reference/release-naming.html 14:57:30 so, your proposal is to use only date based release for repo names? 14:57:40 and centos-release-openstack- ? 14:57:45 so release names are more marketing/transition thing that will go away in the future 14:58:05 I doubt they're going away but go on:) 14:58:50 actually yes. I've raised topic for TC discussion for the next week regarding this topic. 14:59:02 I'll close the mtg notes but we can follow the discussion 14:59:06 #endmeeting