15:00:30 #startmeeting manila 15:00:30 Meeting started Thu Jul 27 15:00:30 2023 UTC and is due to finish in 60 minutes. The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:30 The meeting name has been set to 'manila' 15:00:34 #chair carloss 15:00:34 Current chairs: carloss gouthamr 15:00:56 o/ 15:01:03 o/ 15:01:10 o/ 15:01:11 courtesy ping: vkmc dviroel felipe_rodrigues carthaca 15:01:21 o/ 15:01:49 o/ 15:01:58 hello everyone o/ 15:02:02 i started this here, but carloss will take over in a bit 15:02:12 here's our agenda for today: 15:02:15 #link https://wiki.openstack.org/wiki/Manila/Meetings#Next_Meeting 15:02:17 o/ 15:03:05 let's get started 15:03:10 #topic Announcements 15:03:31 we're at a milestone on our release schedule 15:03:32 #link https://releases.openstack.org/bobcat/schedule.html 15:03:49 Manila's New Driver Deadline is tomorrow 15:04:06 we have a couple of new drivers proposed: 15:04:13 #link https://review.opendev.org/c/openstack/manila/+/880527 (Adds a new Manila driver for Dell PowerFlex storage backend) 15:04:13 #link https://review.opendev.org/c/openstack/manila/+/885974 (Adds a new Manila driver for Dell PowerStore storage backend) 15:04:50 both are in a good shape according to our expectations - i.e., they seem complete and they have passing CI systems on the respective changes 15:05:23 they're getting some review attention, thank you! i'd like to encourage some more at these patches... 15:05:49 thanks gouthamr :D 15:06:30 on to the next one: 15:06:54 we're beginning to plan the next Project Teams Gathering event 15:07:14 it's going to a virtual one, and slated for Oct 23-27 15:07:20 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-July/034363.html 15:07:38 the event is now open for registrations ^; so please sign up :) 15:07:58 #link http://ptg2023.openinfra.dev/ (PTG registration) 15:09:18 milestones and the calendar for the next release (Caracal/2024.1) is also being drafted atm: 15:09:21 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-July/034555.html 15:10:07 thanks for starting the meeting and going over announcements gouthamr :D 15:11:16 as soon as it merges, I'll be proposing the manila-specific deadlines and sharing it with you 15:11:31 so we can gather everyone's feedback on it 15:12:24 I think that's all we had for announcements 15:12:31 is there an announcement you would like to share with us today? 15:14:16 * carloss taking silence as no 15:14:45 #topic Review focus 15:14:58 #link https://etherpad.opendev.org/p/manila-bobcat-review-focus 15:15:41 o/ 15:16:21 * carloss o/ gireesh 15:16:51 we are approaching feature proposal freeze, which means that all featureful changes should be proposed to gerrit by the end of the next week 15:17:05 it should have unit and functional tests in place 15:17:33 so please add your changes to the review focus etherpad I just linked 15:18:40 I think for the features we already have patches proposed so far are in a good shape (have unit and functional tests and they mostly work) 15:18:52 felipe_rodrigues: are the Scheduler changes coming in this cycle? 15:21:19 yes.. Iwill submit soon 15:21:24 okay, thanks! 15:22:30 so we will have a huge amount of code to review this cycle 15:22:45 the more reviews the merrier... we can work with assignments 15:23:48 please don't hesitate to schedule collaborative review sessions... they have proven to be very useful and it makes it easier for the reviewers to understand the changes you are proposing 15:25:04 ++ 15:25:15 we are currently putting some effort in reviewing share backups changes, which are looking in a good shape, and we are figuring out how to get them tested with tempest 15:26:10 but we could use some eyes in the new Dell drivers too... kpdev can I have your eyes on the new driver additions? 15:26:28 sure 15:26:29 NetAppers: you're more than welcome to share your feedback too :) 15:26:36 thanks kpdev 15:27:28 that's all I have wrt $topic 15:27:50 do you have something you would like to bring up? 15:27:53 Sure, will do !! 15:29:54 thanks msaravan :) 15:30:56 on to the next topic... 15:30:59 #topic Bug Triage (vhari) 15:31:09 #link https://etherpad.openstack.org/p/manila-bug-triage-pad-new (Bug Triage etherpad) 15:31:12 hi everyone :) 15:31:19 o/ vhari 15:31:42 let's dive into the new bug due for minor triage 15:31:44 #link https://bugs.launchpad.net/manila/+bug/2028642 15:33:17 this feels more like an RFE, but if I'm not mistaken, not all share servers were automatically deleted after the migration complete 15:33:19 this is an RFE that goes against my old argument of trusting manila to do the cleanups 15:33:28 this is more of an improvement 15:34:42 chuanm says he'd like to rollback, but wouldn't that be an entirely manual process after a cutover? 15:35:04 #link https://github.com/openstack/manila/blob/master/manila/share/manager.py#L5823-L5839 15:35:52 yeah, it is being delete immediately only when the share server is reused, aka nondisruptive migration 15:36:09 in other scenarios, we set it to inactive and leave it to the manila routine 15:36:41 ah 15:36:42 > chuanm says he'd like to rollback, but wouldn't that be an entirely manual process after a cutover? 15:36:42 yeah, it would... even if Manila found the old share server, we couldn't be sure it would be the one picked up for the rollback 15:37:49 if a share server was migrated nondisruptively, wouldn't it mean that the move has happened in the storage system; and a rollback would really be a different migration? 15:38:01 ^ this 15:38:11 ^ yes* 15:38:53 keeping the share server in the source would feel more like a replication 15:39:38 replication with an "expiration" date, based on the request 15:40:20 so i wonder if chaunm is looking for the reference in manila to be retained .. perhaps we should ask how he'd do a rollback 15:40:45 and how this manila ref would be useful in the process 15:40:57 yeah 15:41:26 maybe he'd just reset the status of the share server? then it wouldn't be picked up by the cleanup share servers 15:41:34 let's ask him that question :) 15:42:52 carloss, will do 15:43:13 any other considerations for this bug? 15:43:18 oh, thanks vhari :) - had the comment almost ready 15:43:40 k carloss 15:43:50 so that the bottom of bugs for today 15:44:20 tyvm vhari :) 15:44:22 as always.. thanks for pitching in 15:44:29 yw carloss :) 15:45:27 #topic Open Discussion 15:46:15 it's been a while :D 15:46:29 haha, i've one topic that's not about bears 15:46:39 :O 15:46:41 i'd like to schedule a collab review for the resource locks patches 15:46:59 * carloss was about to ask gouthamr how's the Katmai bear season going 15:47:04 would anyone have a time/date preference? 15:47:36 oh they're feeding and fattening up well carloss: https://explore.org/livecams/brown-bears/brown-bear-salmon-cam-brooks-falls?gclid=EAIaIQobChMIu5OlhZ6vgAMVfAytBh1BfAZgEAAYASAAEgI4yvD_BwE 15:47:47 Tuesdays and Wednesdays are the busiest days for me, but I can fit a session for sure 15:48:39 ack; we can do thursday, with an overlap to this meeting, if it works? 15:48:46 yeah, that works :) 15:49:03 gouthamr++ 15:49:13 great idea gouthamr - perhaps I should do one for the access restrict changes too after yours, as it uses the locks changes you're implementing 15:49:18 gouthamr++ 15:49:44 ^ thought we'd do it together carloss 15:49:51 ah, sure 15:50:05 unless it is more digestible in separate sessions 15:50:12 we can take an ad hoc call 15:51:26 I think we can cover it together 15:53:00 ack 15:53:17 lets plan and send info over to the ML 15:53:45 ack, thanks! 15:54:02 gouthamr++ 15:55:51 anything else to bring up in this call? 15:55:57 s/call/meeting :) 15:56:21 going once... 15:56:56 thank you for joining! let's get back to #openstack-manila 15:57:01 #endmeeting