14:01:02 <rafaelweingartner> #startmeeting cloudkitty 14:01:02 <opendevmeet> Meeting started Mon Aug 21 14:01:02 2023 UTC and is due to finish in 60 minutes. The chair is rafaelweingartner. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:02 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:02 <opendevmeet> The meeting name has been set to 'cloudkitty' 14:01:05 <rafaelweingartner> Hello guys! 14:01:09 <rafaelweingartner> Roll count 14:01:11 <rafaelweingartner> \O 14:01:17 <mkarpiarz> Hi! 14:01:18 <priteau> o/ 14:01:34 <rafaelweingartner> Awesome to see you all here! 14:04:11 <rafaelweingartner> #topic vPTG meeting 14:04:30 <rafaelweingartner> We need to register at https://ptg2023.openinfra.dev/ 14:04:44 <rafaelweingartner> I already did, do not forget to register yourselvers as well 14:04:54 <rafaelweingartner> We still need to register the timeslot and the etherpad 14:05:02 <rafaelweingartner> Do you guys have a preference for a timeslot? 14:05:15 <rafaelweingartner> Should I create a pool, or can we define a slot ourselves? 14:05:45 <priteau> I have a preference for the Monday as I will be on travel the rest of the week 14:05:56 <rafaelweingartner> I see 14:05:59 <rafaelweingartner> that works for me 14:06:32 <rafaelweingartner> What about you mkarpiarz? 14:07:33 <mkarpiarz> No preferences. 14:07:47 <rafaelweingartner> priteau: do you know where I can register the timeslot? 14:08:04 <rafaelweingartner> I look into my email, but could not find a link to register the timeslot and the etherpad 14:08:19 <priteau> It is not yet possible. 14:08:33 <priteau> As usual it will be done via the ptgbot on IRC 14:08:43 <priteau> But I think it is still configured with the previous PTG 14:08:48 <priteau> After all, it is in two months 14:09:33 <rafaelweingartner> I see 14:09:41 <rafaelweingartner> so I wil just register the preference for Monday then 14:10:16 <mkarpiarz> Sure 14:10:43 <rafaelweingartner> Moving on 14:10:52 <rafaelweingartner> #topic the OpenSearch support 14:10:59 <rafaelweingartner> the patch is being introduced via #link https://review.opendev.org/c/openstack/cloudkitty/+/880739 14:11:19 <rafaelweingartner> should we start reviewing that patch? Or, maybe, it needs more time 14:13:31 <priteau> As I mentioned last time, we saw an issue while upgrading from elasticsearch to opensearch (which is not tested by CI) 14:13:38 <priteau> This needs more time I am afraid 14:13:43 <rafaelweingartner> I see 14:13:45 <rafaelweingartner> no worries 14:13:49 <rafaelweingartner> just checking 14:13:59 <rafaelweingartner> Our open patches also need more time :) 14:14:55 <rafaelweingartner> #topic Monasca deprecation 14:15:15 <rafaelweingartner> We announced the Monasca deprecation past release, and now it is time to remove it. Can I move on with the patches? 14:16:05 <mkarpiarz> Sure 14:16:14 <mkarpiarz> No objections from my side. :) 14:17:32 <priteau> Please go ahead 14:17:54 <rafaelweingartner> thanks for you support guys! 14:18:13 <rafaelweingartner> Moving on, #topic Target reviews 14:18:43 <rafaelweingartner> From our side, we were not able to advance much into the open patches. However, I reserved this week and next for this. Therefore, we will move on with our patches =) 14:18:58 <rafaelweingartner> do you guys have something to add to the target patches for reviewing in this meeting? 14:21:22 <priteau> First one is ok for me 14:21:28 <priteau> Second one, I left a -1 with a comment 14:21:32 <priteau> Third one is not passing CI 14:23:21 <rafaelweingartner> yes, we need to ammend those patches 14:23:24 <rafaelweingartner> we will do so this week 14:24:50 <rafaelweingartner> Do you guys have some other patches that would require our attention? 14:26:01 <priteau> The failing patch on stable/stein 14:26:17 <priteau> https://review.opendev.org/c/openstack/cloudkitty/+/892082 14:26:30 <priteau> CI is broken on this branch 14:27:04 <priteau> Since we don't actively support old releases, I suggest we EOL stein 14:27:49 <rafaelweingartner> I aggree 14:28:00 <rafaelweingartner> What is the process to EOL stein? 14:28:09 <rafaelweingartner> I do not recall having done that before 14:31:37 <priteau> It is done automatically by release managers when we reach the usual EOL time, I will try to find one of their patches 14:32:15 <priteau> https://review.opendev.org/c/openstack/releases/+/881603 14:32:16 <rafaelweingartner> I see 14:32:35 <rafaelweingartner> and, then I just have to approve 14:32:39 <rafaelweingartner> now I get it 14:32:40 <priteau> Maybe you can also ask them to issue a patch for stein on #openstack-release 14:32:52 <rafaelweingartner> sure 14:32:53 <rafaelweingartner> will do so 14:33:27 <priteau> For example, this is a patch from the Kolla project to EOL more recent releases: https://review.opendev.org/c/openstack/releases/+/869569 14:34:10 <rafaelweingartner> I see 14:34:19 <rafaelweingartner> so we are the ones that should create the patch? 14:34:27 <rafaelweingartner> I mean, can we create a patch for those repos? 14:36:32 <priteau> Yes you can 14:36:40 <rafaelweingartner> AH, I see 14:36:43 <rafaelweingartner> I will do so then 14:41:46 <priteau> You problably need to target all the cloudkitty repos, not just the main one 14:42:41 <rafaelweingartner> I see 14:42:50 <priteau> i.e. cloudkitty-dashboard.yaml cloudkitty-tempest-plugin.yaml cloudkitty.yaml python-cloudkittyclient.yaml 14:43:02 <rafaelweingartner> I see 14:47:00 <rafaelweingartner> Do you guys have something else to add? Otherwise, I guess we can close the meeting. 14:47:26 <priteau> OK 14:47:34 <mkarpiarz> Nothing from my side. 14:48:14 <rafaelweingartner> Thank you guys for participating. Have a nice week. 14:48:17 <rafaelweingartner> #endmeeting