15:00:19 #startmeeting manila 15:00:19 Meeting started Thu Jan 5 15:00:19 2023 UTC and is due to finish in 60 minutes. The chair is carloss. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:19 The meeting name has been set to 'manila' 15:00:27 o/ 15:00:36 o/ 15:00:52 o/ 15:01:01 o/ 15:01:05 hi 15:01:12 o/ 15:01:34 hi 15:01:36 hi 15:01:42 \o 15:01:45 courtesy ping: vkmc dviroel 15:01:59 hi o/ 15:02:28 o/ 15:03:56 o/ hello everyone 15:04:02 and happy new year! 15:05:01 it's good to be back 15:05:10 Is the Christmas break over? 15:05:28 haixin: for many of us, yes :) 15:05:33 some could have extended 15:05:40 today's meeting agenda: 15:05:42 #link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting 15:05:49 hi 15:06:12 o. thiagoalvoravel 15:06:16 o/ * 15:06:36 o/ 15:06:47 #topic Announcements 15:07:05 Schedule and Deadlines: 15:07:22 #link https://releases.openstack.org/antelope/schedule.html 15:07:36 so we are past spec freeze and this week is M-2 for Antelope 15:08:15 next week would be our new driver deadline but apparently we don't have candidates for this cycle 15:09:15 so I think we are good with that 15:10:35 next deadlines to track, I'd say: feature proposal freeze (in 2 weeks) 15:11:02 where featureful patches should be submitted with unit and functional tests to gerrit (also client changes if needed) 15:11:45 and m-3 is in 6 weeks, which is also our client merge deadline 15:12:33 next announcement is the PTG, which is in a few months from now 15:12:55 #link https://openinfra-ptg.eventbrite.com 15:13:13 please register if you intend to participate. I will create the topics etherpad soon and share it with you 15:14:19 on a side note: talk and forums submission for the next OpenInfra Summit in June is still open 15:14:29 so you can propose talks you might want to bring up in the CFP 15:14:44 #link https://openinfra.dev/summit/vancouver-2023 15:14:47 ^ more info here 15:15:35 and last announcement on my side: 15:15:39 we have a name for the next release 15:15:52 2023.2, aka Bobcat :D 15:15:58 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031666.html 15:16:06 the foundation shared the name yesterday 15:16:45 that's all I had for announcements 15:16:56 is there an announcement you would like to share with us today? 15:19:15 I have an announcement, we have a new member in Netapp Team 15:19:22 thiagoalvoravel: welcome ^^ 15:19:53 welcome thiagoalvoravel ^^ 15:19:55 thiagoalvoravel: welcome o/ 15:20:09 welcome thiagoalvoravel! glad to hear the Zorilla team is growing up 15:20:14 ++ welcome thiagoalvoravel 15:20:15 welcome :) 15:21:02 thank you everybody =) 15:22:18 moving on... 15:22:23 #topic Feedback on deleting service table entries (gouthamr/kpdev) 15:22:31 gouthamr kpdev_: floor is yours 15:22:59 thanks carloss 15:24:00 wanted to get some more eyes on a change to clean up the service table entries while bringing down a service 15:24:10 #link https://review.opendev.org/c/openstack/manila/+/859301 15:24:48 i think we can make changes as you suggested 15:24:58 this should be fine in deployments as is where services are deployed on unique hosts 15:25:15 instead of deleting service entry during service stop, we mark it as STOPPED 15:25:43 and add per service periodic cleanup task, which checks for STOPPED entries and delete those entries. 15:26:14 if entry is marked as DOWN, it wont be deleted as its actual service down and not the stopped in previous iterations. 15:27:27 wdyt, gouthamr 15:28:28 in our use case, multiple manila-share backends deployed as PODS and so they does on different host during each deployment, so we want to delete stale entries of invalid/previous deployments. 15:28:37 kpdev_: that sounds okay.. do i understand correctly that you'd introduce a new column in the service table? 15:29:47 kpdev_: indeed, the use case is perfectly valid - trying to look out for another set of deployments where we configure multiple copies of the service across different hosts by overriding the "host" attribute to the same name 15:30:13 thereby making these services look the same, but still have H/A 15:30:53 yes, i will add new column and periodic cleanup task 15:32:30 thanks, i like that solution 15:32:40 ++ I like it too 15:32:47 what is the different between your new column mark STPPPED and the original logic uses service_down_time (60s by default) to determine if the service is down 15:34:01 STOPPED is service stopped and if its stopped more than periodic interval, its stale entry.. so should be deleted 15:34:17 while DOWN, service down under current deployment 15:35:35 This means we need to develop a new api to flag the service as stopped? 15:37:00 haixin: won't be necessary; if services need to be taken down explicitly, the "disable" API would work fine.. 15:37:24 the "stopped" state is only an internal representation of the service 15:37:46 nothing should rely on it except this periodic cleanup task 15:37:48 got it, i will check this "disable" api. 15:38:14 if a service reports again within the report interval, we pop off the "stopped" state 15:39:20 sounds good 15:40:17 this will mostly happen during service start i.e. move from STOPPED to UP 15:41:06 sounds great kpdev_ 15:41:11 kpdev_: we wouldn't wait for start time, if a service reports, we can simultaneously remove the stopped state.. 15:41:32 yes 15:42:42 thanks kpdev_ gouthamr haixin :) 15:43:18 do you have something else to add? 15:43:23 ++.. thanks kpdev_ for this enhancement! 15:44:50 okay, moving to the next topic: 15:44:53 #topic Review Focus 15:45:00 #link https://etherpad.opendev.org/p/manila-antelope-review-focus 15:45:13 the etherpad was updated earlier today 15:45:27 the usual changes are there, some changes in the pad were merged and I removed them from the list 15:45:29 and added some more 15:46:11 stephenfin's changes for making the code compatible with sqlalchemy 2.0 15:46:25 #link https://review.opendev.org/q/topic:sqlalchemy-20+project:openstack/manila 15:46:33 would be good to have some eyes on these changes 15:46:40 thanks gouthamr for the reviews already 15:46:59 I intend to review the changes, but would like to voluntell some people :) 15:47:22 felipe_rodrigues ashrodri MatheusAndrade[m]: could you please take a look when you have some time? :) 15:47:35 sure 15:47:51 sure 15:48:29 awesome, thanks! :) 15:49:16 is there any other change you would like to bring up during this meeting? 15:50:00 support share transfer between project need review 15:50:19 https://review.opendev.org/c/openstack/manila/+/843832 15:50:43 I will review 15:50:52 thanks :) 15:51:05 +1 me too, haixin can you rebase? should be a trivial one 15:51:38 ++, I intend to take a look as well 15:51:41 ok, i will rebase it tomorrow 15:51:54 thanks haixin 15:51:58 thanks! 15:52:26 and our last topic for today: 15:52:30 #topic Bug Triage 15:53:04 we have one bug we carried from last week: 15:53:06 #link https://bugs.launchpad.net/manila/+bug/2000171 15:53:42 thanks for filing the bug carthaca 15:53:58 and thanks for working on the fix kpdev_ 15:54:00 #link https://review.opendev.org/c/openstack/manila/+/868486 15:55:39 +1 ; medium, M-3? 15:55:44 yes, I'd say so 15:55:49 an RFE, good to have 15:56:03 some netappers eyes on this would be appreciated too :) 15:58:48 * carloss checks time 15:58:52 sure, I will 15:58:57 that's all for bus on the list 15:58:59 thanks felipe_rodrigues 15:59:16 thank you for joining today's meeting! 15:59:25 let's get back to #openstack-manila 15:59:32 #endmeeting