15:00:37 #startmeeting manila 15:00:37 Meeting started Thu Nov 14 15:00:37 2024 UTC and is due to finish in 60 minutes. The chair is carloss. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:37 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:37 The meeting name has been set to 'manila' 15:00:54 courtesy ping: dviroel vhari gouthamr carthaca msaravan pulluri ashrodri 15:02:12 hi 15:02:13 o/ 15:02:21 hi 15:02:42 o/ 15:04:25 o/ hello 15:04:28 let's get started :) 15:04:35 our meeting agenda for today: 15:04:38 #link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting 15:05:25 #topic Announcements 15:05:39 Schedule and Deadlines 15:05:39 #link https://releases.openstack.org/epoxy/schedule.html 15:06:07 the epoxy-1 milestone is this week 15:07:14 we have a couple of things currently targeted to this milestone on launchpad 15:08:20 I should definitely add the manila milestones to the official schedule 15:08:36 that's on top of my todo list 15:08:52 I believe I'll be able to get to it next week and share it with you 15:10:32 o/ 15:10:37 o/ 15:11:00 another announcement: 15:11:10 #https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/PAI43MRAEZFRJYRGCYL3E7CR5VKQBTK2/ (Scale CFP extension) 15:11:35 there will be another openinfra days co-located with the scale linux event next year 15:11:41 and I should've brought it up sooner 15:11:50 but the cfp extension ends tomorrow 15:12:03 so if you have any last minute ideas you'd like to propose, please go ahead 15:12:24 that's all I had for announcements. Is there an announcement you'd like to share with us? 15:15:15 taking silence as no 15:15:31 #topic Review focus 15:15:41 #link https://etherpad.opendev.org/p/manila-epoxy-review-focus (Epoxy review focus etherpad) 15:16:14 we currently have two specs being proposed 15:16:34 #link https://review.opendev.org/c/openstack/manila-specs/+/932637 (Add spec for subnet force deletion) 15:16:44 and 15:16:57 #link https://review.opendev.org/c/openstack/manila-specs/+/933558 (Add spec for share group affinity policy) 15:17:15 sharing feedback on the specs is very important 15:17:52 i'd encourage all of the reviewers to take a look at them 15:18:18 +1 I’ve looked but not finished commenting 15:18:26 will do today 15:18:46 gouthamr: thank you very much! 15:20:02 for today I'd like to ask for some attention to these specs and the bugs targeted to epoxy-1 15:20:19 Is there another change you'd like to bring up for $topic? 15:21:33 #topic Bug Triage (vhari) 15:21:40 #link https://etherpad.openstack.org/p/manila-bug-triage-pad-new (Bug Triage etherpad) 15:21:47 ty carloss 15:22:07 lets start with new bugs needing triage this week 15:22:17 then dive into a small backlog 15:22:19 #link https://bugs.launchpad.net/manila/+bug/2087192 15:23:05 ty for reporting this gouthamr 15:24:31 yeah; was hoping we can pin this job on jammy as we investigate 15:25:45 hi, sorry for joining late. 15:26:11 gouthamr: sounds like a good idea 15:26:21 hey msaravan o. 15:26:25 o/* 15:26:44 ack, gouthamr what would stop us from this? are there any drawbacks? 15:26:54 o/ msaravan 15:27:02 Hi carloss. if there are any asks on NetApp, please share.. 15:28:50 msaravan: sure, so far only me asking for some reviews in the specs :) 15:29:02 ack 15:30:16 vhari: the image pinning should be okay as far as I remember 15:30:37 gouthamr: are you planning to work on this? or would you like someone to take a look at pinning the image? 15:32:39 wasn’t planning to; but we got to move along to land the noble based jobs early 15:32:46 so can do 15:33:09 thanks 15:33:11 ty gouthamr++ 15:33:28 if you have too much going on, let us know and we can try to find another owner 15:33:50 s/let us know/please let us know 15:33:56 moving on .. #link https://bugs.launchpad.net/manila/+bug/2088063 15:35:25 so this is a bug I reported after hearing some feedback from bauzas, while he was doing some testing with VirtioFS 15:35:26 good catch carloss 15:35:46 saw the thread around this issue .. ty for reporting it 15:35:55 missing user message? 15:35:59 vhari: np 15:36:32 yes, a user message would be helpful there 15:36:56 his suggetion was: we shouldn't let the user do this when we know that backup isn't supported 15:37:32 ack 15:37:40 and if we would be able to fail earlier, I would be in favor of it, but it is a bit tricky 15:37:54 to fail earlier, this means failing at the API layer 15:38:39 where we don't have a lot of information whether the backup will use the generic implementation or the driver own means to create the backup 15:39:24 his idea was: as the generic implementation only works with NFS, we can check on the share's protocol and fail 15:39:27 when it's cephfs 15:39:59 which makes sense until we implement share backup using the cephfs driver and can take backups from cephfs shares too 15:40:46 this would make us impose something only based on a single protocol, but if we are to fail, I'd rather ask the backend if it supports the action or not 15:41:16 because we also have CIFS, glusterfs... 15:41:44 ++ that would be a broader solution 15:41:54 and CIFS might work with NetApp, so the best way out to fail earlier would be to check with the backend first 15:42:22 the downside is that it adds some extra complexity and a direct call to the backend 15:42:38 which can leave the API request hanging 15:44:12 so maybe we can check if the protocol is not NFS. if it is not, we can make a call to the share manager and check if there's a backup driver or an implementation for backups 15:44:40 or 15:45:16 we can use only the user message, which will fail at the moment it attempts to mount the share in order to copy the data 15:45:54 ^ currently 15:46:00 we can also return earlier in the generic backup implementation in case this isn't an nfs share 15:46:02 thoughts? 15:48:42 I think I live the latter; the backup driver is reporting to the scheduler, correct? 15:49:41 gouthamr: iirc yes 15:51:16 carloss, any interest in taking a stab at this bug? :) 15:51:31 yes, I can take a look 15:52:02 great ty .. you've done a lot of research on possible fixes ++ 15:52:26 I think that's all the time we have for bugs today 15:52:32 so back at you carloss 15:52:43 ty all for pitching in as always 15:52:47 vhari: tyvm :) 15:52:55 #topic Open Discussion 15:52:58 yw :) 15:54:34 https://etherpad.opendev.org/p/manila-epoxy-review-focus, most of PRs are there for more than 3 weeks, I have not received significant reviews. so please review and speed up. 15:59:52 hey kpdev o/ sorry for the wait but from what I hear a lot of people are fighting fires at the moment 16:00:11 and the reviews are a bit delayed 16:00:20 ack 16:02:49 kpdev, would you mind share your top prio changes in manila channel for folks to focus on? 16:03:06 since we are at top of hr for this meeting? 16:03:16 that would greatly help ty 16:03:22 ok 16:03:29 vhari++ thank you 16:03:29 kpdev++ 16:03:43 yw carloss :) 16:03:50 kpdev++ i'm hoping we can get some reviews in asap 16:04:00 we're past the hour 16:04:05 let's get back to #openstack-manila 16:11:16 #endmeeting