15:00:19 #startmeeting manila 15:00:19 Meeting started Thu Sep 26 15:00:19 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:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:19 The meeting name has been set to 'manila' 15:00:35 courtesy ping: vhari gouthamr carthaca msaravan pulluri ashrodri 15:00:43 o/ 15:00:47 hi 15:00:48 hi 15:00:59 o/ 15:04:29 our meeting agenda for today: 15:04:35 #link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting (Meeting agenda) 15:04:38 hi 15:04:46 #topic Announcements 15:04:57 Schedule and Deadlines 15:05:46 #link https://releases.openstack.org/dalmatian/schedule.html 15:06:02 so the 2024.2 Dalmatian release should happen next week :D 15:06:19 a lot of work coming together 15:07:31 Hi 15:07:39 o/ 15:07:47 and next week, as usual, we will have the OpenInfra live 15:07:57 and I volunteered to share the Manila updates again 15:08:29 it should start at 14:00 UTC and end at 15:00 UTC 15:09:15 there is a chance that it will run a bit late 15:10:24 ++ thanks for signing up to do these updates 15:10:54 if you get delayed; i can start the meeting and you can take over when you’re back 15:11:08 ack, thanks gouthamr :D 15:11:28 we can also consider having someone running the meeting, if they are interested 15:12:30 still on announcements: 15:12:48 PTG will happen in a month 15:13:01 #link #link https://openinfra.dev/ptg/ (OpenInfra PTG) 15:13:09 so please subscribe ^ 15:13:32 manila is one of the projects that adhered and as always, we will have some intense days of project discussions 15:13:54 so please add your topics to the PTG planning etherpad: 15:14:07 #link #link https://etherpad.opendev.org/p/epoxy-ptg-manila-planning (Epoxy PTG planning etherpad) 15:14:34 * carloss just noticed the double link command :D 15:15:58 that's all I had in terms of announcements 15:16:05 is there an announcement you'd like to share with us today? 15:18:09 #topic Review focus 15:18:15 #link https://etherpad.opendev.org/p/manila-dalmatian-review-focus (Dalmatian review focus etherpad) 15:18:52 penultimate meeting before we replace this etherpad :D 15:19:12 but I've already added some updates to it and re-targeted the fixes there 15:20:09 most of the changes in this list received reviews and are waiting on the authors to fix a couple of issues 15:20:30 so I'd say that's where we stand at the moment 15:21:10 we have a couple of docs fixes that could use some eyes 15:21:19 #link https://review.opendev.org/c/openstack/manila/+/930441 ([doc] Driver updatabled metadata) 15:21:50 #link https://review.opendev.org/c/openstack/manila/+/929844 (Add CephFS Manage/unmanage documentation) 15:22:03 #link https://review.opendev.org/c/openstack/manila/+/929972 (Add ensure shares admin docs) 15:22:19 gouthamr gireesh carthaca: can I have your eyes on these? :) 15:22:37 ack 15:22:41 ack 15:22:48 yep 15:23:25 tyvm 15:23:44 that's all I had for $topic 15:23:56 is there another change you would like some eyes on? 15:26:21 taking silence as no 15:26:26 #topic Bug Triage (vhari) 15:26:31 #link https://etherpad.openstack.org/p/manila-bug-triage-pad-new (Bug Triage etherpad) 15:26:36 plenty of time for some bug triaging today :D 15:26:59 ty carloss 15:27:17 lets dive in :) 15:27:21 #link https://bugs.launchpad.net/manila/+bug/2081676 15:30:56 so if I understand correctly, the bug reporter is using the generic driver and is trying to use ceph and netapp as a backend 15:31:15 (through cinder?) 15:31:30 I wonder why not use the netapp driver directly to have the dhss=true behavior? 15:31:42 generic driver is not supposed to be used in production 15:32:28 carloss, we can ask for more information regarding backend 15:32:58 also ask for additional logs 15:33:10 yeah, for cephfs I understand we don't have dhss=true, but for netapp we do 15:33:19 ack 15:33:21 so that could be configured directly in the deployment 15:33:35 yes, they should use netapp driver for the greater advantage 15:34:06 vhari: yes, thanks... we can ask for the use case and suggest them to use the respective drivers directly, instead of trying to use the backends with the generic driver 15:34:16 I'll commend that in the bug 15:34:21 thanks :) 15:34:35 carloss++ 15:34:53 next up #link https://bugs.launchpad.net/manila/+bug/2081827 15:36:40 nice one, an RFE 15:37:13 I'd likely think this would be part of kpdev's plans, but he removed himself of the assignees 15:37:34 so I'd say low priority, as there isn't something broken an is an enhancement, and m-3 sounds like a good target for this 15:37:38 thoughts? 15:39:08 carloss++ done 15:39:52 if anyone would like to add additional info or take this on, pls feel free to update the bug 15:39:57 #link https://bugs.launchpad.net/manila/+bug/2081990 15:41:36 thanks for the bug report carthaca 15:41:38 and nice catch 15:42:25 Interesting; yes, if specifying the layout is possible, the driver should make choices based on the existing distribution 15:42:33 ++ 15:42:46 but, does that affect the “host” field set on the shares? 15:44:44 iirc server migration is across backends; and potentially all pool names in the share’s host field will change 15:45:18 i think it would affect and we should be accounting for that 15:46:39 #link https://opendev.org/openstack/manila/src/branch/master/manila/share/manager.py#L6318-L6324 15:46:50 we'd be covered if the driver is currently reporting the new host correctly 15:48:27 great; thanks 15:48:35 yep, this is done correctly already https://opendev.org/openstack/manila/src/commit/dca04e2270a745e73226adbdf80f740f002bd133/manila/share/drivers/netapp/dataontap/cluster_mode/lib_multi_svm.py#L1911 15:49:16 ++ 15:49:28 cool 15:49:43 msaravan: can we have one of the netappers assigned? 15:50:36 carthaca: or are you planning to work on the fix for it? :) 15:51:34 I already asked the netapp engineers for help :) 15:51:42 carthaca: ah, thank you :D 15:51:47 and again, thanks for the report 15:51:50 we discussed with maurice yesterday, and there are 2 bugs he is reporting and we'll look at them in epoxy release. 15:52:26 msaravan: great, I'll assign it to you for now and please change the assignee when you guys have figured out who will work on this issue 15:52:44 sure, thank you carloss and carthaca 15:52:47 carthaca++ msaravan++ ty for heads up 15:52:47 thanks! 15:53:04 so I'd say low, m-1 for this could be feasible :) 15:53:42 carloss, time check .. looking tight .. lets triage the last bug later? 15:53:45 #link https://bugs.launchpad.net/manila/+bug/2081992 15:54:13 yes, this is the other one reported by carthaca 15:54:15 heads up, pls have a look after the meeting ^^ 15:54:39 this wraps up today's bugs 15:54:49 ty all for pitching in as usual :) 15:54:58 I think the time we have should still be enough 15:55:01 sounds like an RFE 15:55:05 carthaca: thanks for the report 15:55:22 carloss, ack 15:55:26 > But maybe this can get more clever with a dedicated scheduler filter? 15:55:26 could be one way out 15:55:34 and very likely a good topic for a discussion at the PTG 15:55:44 considering the time for discussion, let's target it for m-3? :) 15:56:11 ack 15:56:15 thanks msaravan 15:56:19 thanks vhari :D 15:56:32 productive bug triaging today 15:56:32 yw :) 15:56:53 yep, covered all target bugs today 15:57:00 (we had more time for it, so that explains getting more bugs triaged) 15:57:03 and thanks for the list as always :D 15:57:06 awesome 15:57:11 so let's wrap up this meeting then 15:57:21 hope y'all have a great day 15:57:29 let's get back to #openstack-manila 15:57:38 #endmeeting