13:02:29 #startmeeting barbican 13:02:29 Meeting started Tue Mar 8 13:02:29 2022 UTC and is due to finish in 60 minutes. The chair is dmendiza[m]. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:02:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 13:02:30 The meeting name has been set to 'barbican' 13:03:06 #topic Roll Call 13:03:32 Courtesy ping for ade_lee dave-mccowan d34dh0r53 hrybacki jamespage Luzi lxkong mhen rm_work tosky xek nearyo oleksandry 13:03:53 hi 13:05:26 o/ 13:09:30 Let's get started! 13:09:38 #topic Review Past Meeting Action Items 13:09:46 #link https://meetings.opendev.org/meetings/barbican/2022/ 13:09:55 err, I mean 13:09:58 #link https://meetings.opendev.org/meetings/barbican/2022/barbican.2022-03-01-13.00.html 13:10:06 We didn't have any 13:10:10 * dmendiza[m] needs coffee 13:10:22 #topic Liaison Updates 13:10:26 tosky: around? 13:12:09 Doesn't look like it 13:12:24 #topic Secret Consumers 13:14:00 xek's patch is still under review 13:14:02 #link https://review.opendev.org/c/openstack/barbican/+/828829 13:14:08 Looking like this will be a Zed feature 13:15:44 OK, moving on 13:16:23 #topic RC1 13:16:27 #link https://releases.openstack.org/yoga/schedule.html 13:16:32 This week is Yoga RC1 week 13:17:36 that means reviews need to get approved? 13:18:01 Yeah, if there's anything we need in Yoga it needs to be approved in the next few days 13:18:17 ack 13:20:19 once we tag RC1 then the master branch will be tracking Zed 13:20:55 do we have something pending that needs to go into Yoga? 13:22:19 Nothing off the top of my head 13:26:35 #topic Zed Cycle 13:26:56 Looks like the Zed schedule is out 13:26:58 #link https://releases.openstack.org/zed/schedule.html 13:27:56 And the weekly reminder that we have an etherpad for the upcoming Zed PTG 13:27:58 #link https://etherpad.opendev.org/p/z-ptg-barbican 13:28:05 which will be in about 4 weeks 13:31:25 Ok, moving on 13:31:31 #topic Bug Review 13:31:42 #link https://storyboard.openstack.org/#!/project_group/barbican 13:31:51 Looks like no new bugs 13:32:08 #link https://bugs.launchpad.net/castellan/+bugs?orderby=-id&start=0 13:32:14 And no new bugs for Castellan 13:32:30 #link https://bugs.launchpad.net/cursive/+bugs?orderby=-id&start=0 13:32:34 and no new Cursive bugs 13:32:38 #topic Open Discussion 13:32:46 Anything else y'all want to talk about? 13:33:09 I was checking some (what seems to be) low hanging fruits, Barbican pagination logic doesn't preserve URL filters, https://storyboard.openstack.org/#!/story/2009322 , it seems to be related to wsgi? 13:33:48 I tried to see how it's done but, honestly, wsgi is still unfamiliar to me, do we need to deal here with configurations or some part of the code? 13:34:20 I think this is a bug in the API controllers 13:35:09 When the request comes in, the framework takes that query string and breaks it down 13:35:33 I don't think we're using that in the controllers to rebuild the query string to be added to the "links" section of the response 13:37:09 in this case, I was just looking at the code where barbican created the "next" part of the response 13:37:31 I didn't find it, so I thought this is related to the wsgi? so, in some configuration or somewhere else 13:38:38 anyway, I just wanna know if someone already dealt with wsgi and could share where this needed to be fixed 13:40:29 yeah, ping me after the meeting and I can look into where the next/previous attributes get generated in the response 13:40:45 I want to say it happens in the controller, but it may be hidden in some helper function 13:41:33 right, I'll try to find it then, I'll ping you later 13:43:55 Sounds good 13:43:58 Any other topics? 13:44:56 not from me 13:45:59 Thanks for joining, everyone! 13:46:03 #endmeeting