15:00:24 <carloss> #startmeeting manila
15:00:24 <opendevmeet> Meeting started Thu Jun 12 15:00:24 2025 UTC and is due to finish in 60 minutes.  The chair is carloss. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:24 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:24 <opendevmeet> The meeting name has been set to 'manila'
15:00:45 <carloss> courtesy ping: dviroel vhari msaravan Sai ashrodri gireesh
15:00:58 <vhari> hi
15:01:00 <kpdev> hi
15:01:07 <haixin> hi
15:03:57 <carloss> smaller crowd today, plenty to get through in the schedule
15:04:05 <carloss> let's get started
15:04:12 <carloss> and hi everyone :D
15:04:21 <gireesh> hi
15:04:21 <carloss> hope you're having a good day
15:04:38 <carloss> let's start with our first topic of the today
15:04:41 <carloss> #topic Announcements
15:04:47 <carloss> Schedule and Deadlines
15:04:53 <carloss> #link https://releases.openstack.org/flamingo/schedule.html (Flamingo Schedule)
15:05:25 <carloss> next week is spec freeze
15:05:34 <carloss> and in 3 weeks from now we will have our hack-a-ton
15:05:55 <carloss> for spec freeze, I think we are in a good shape but there is still time for the authors to update the specs that are open
15:07:12 <carloss> as for the hack-a-ton, vhari kindly offered to do a howcast for the bugsquash
15:07:29 <carloss> so that will happen as part of the kick-off meeting
15:08:15 <carloss> I was thinking we can use the week for the hack-a-ton and focus on getting some contributions done
15:08:23 <carloss> and have the kick-off call on Monday
15:08:40 <carloss> and use this meeting of that week to assign reviews and go through the proposed changes
15:08:44 <carloss> how does that sound?
15:09:51 <vhari> +1
15:11:13 <kpdev> +1
15:11:26 <carloss> great thank you for the feedback
15:11:39 <carloss> I'll send an email to the mailing list announcing and sharing the room details + ics
15:11:52 <carloss> last but not least on announcements:
15:11:54 <carloss> OpenInfra Summit CFP ending
15:12:14 <carloss> the CFP closes tomorrow
15:12:31 <carloss> so that's the last chance to propose talks if you are planning to attend
15:13:22 <carloss> that's all I had for $topic. Is there another announcement you'd like to share?
15:16:04 <carloss> #topic Review Focus
15:16:14 <carloss> #link https://etherpad.opendev.org/p/manila-flamingo-review-focus (Review focus etherpad)
15:18:29 * carloss got a bit distracted with one review, sorry
15:18:31 <kpdev> FYI - The encryption PRs are ready to review. We have verified with NetApp driver. Reviews are welcome. https://review.opendev.org/q/topic:%22bp/share-encryption%22
15:18:49 <carloss> kpdev: yes, will take a look at the encryption changes asap
15:18:54 <carloss> thanks for keeping them updated
15:20:33 <carloss> so as for the changes, I've just shared one review
15:20:36 <carloss> #link https://review.opendev.org/c/openstack/manila/+/951782 (NetApp: Fix vserver create REST API)
15:20:48 <carloss> this is a fix for a bug that Sai reported some weeks ago
15:20:52 <carloss> kpdev: thanks for working on it
15:21:10 <carloss> this bug also gets us back to the CI testing question
15:22:34 <carloss> which is heavily important. This is a bug that the NetApp ONTAP CI would easily catch if running, also if testing was done with the change and the driver configured to use REST API
15:24:04 <carloss> I've heard some updates on the NetApp CI from gireesh and Sai recently, and it is being worked on at the moment
15:24:16 <carloss> but I think we should really get back to testing these changes and avoid breakages
15:24:21 <carloss> not only these, other changes as well
15:24:33 <gireesh> will test this in in my local setup, yes we are working on CI part also
15:24:36 <carloss> this is also one of the changes that we've asked for testing feedback
15:25:37 <carloss> gireesh: I just had one idea: tempest testing should be easy to set up locally in a devstack environment
15:26:13 <carloss> gireesh: is it possible for you guys to keep one VM around just for testing stuff and posting the result while CI isn't back up?
15:27:08 <kpdev> yes, that can be temporary solution that NetApp can do to speed up reviews. wdyt gireesh ?
15:27:15 <carloss> for example: set up a VM, install manila-tempest-plugin and apply the patch you guys are willing to test. You can do the manual testing by hand, and later run at least a suite to test
15:27:24 <carloss> like some functional tests
15:27:27 <carloss> and share the output
15:28:20 <carloss> I am saying that it is easy because once the set up is done, you can simply kick off the testing and get back later to check the tempest output, might take 10, 20 minutes
15:28:24 <carloss> and then share the result
15:28:42 <carloss> it supposedly should be a 1 command thing that can help us avoiding breakages like this
15:29:03 <carloss> I can help with that setup if you need some help, no worries
15:29:17 <gireesh> ireesh: I just had one idea: tempest testing should be easy to set up locally in a devstack environment - sure @caloss, will take this approach
15:30:35 <carloss> gireesh: thank you very much. Please reach out to me in case you have any question on set up or how to do that
15:30:42 <carloss> I think this will help a lot on the patches moving faster
15:30:44 <gireesh> sure
15:30:57 <gireesh> this is good idea
15:31:41 <carloss> thanks
15:32:25 <carloss> and yeah, a couple of changes have been waiting for feedback
15:35:15 <carloss> gireesh: we've been adding you to a lot of reviews on the NetApp changes, and we know there's a lot on your plate. Do you think there's something we can do to distribute the workload?
15:35:49 <carloss> like balancing the ping on the changes from you and another NetApper?
15:36:01 <carloss> we can get more people up to speed with the reviews and share the workload
15:36:26 <carloss> I think that it might be easier on you as well, kind of helping with review activity and discipline
15:37:31 <carloss> ^ something that we can keep chatting if you guys agree
15:37:41 <carloss> maybe even ramping up more people to join the core team will help
15:37:53 <carloss> I think it gets easier when shared
15:38:14 <gireesh> I will ask other NetApp team member to review the patches,  yes, I wanted other also to review the patches
15:38:52 <carloss> gireesh++
15:38:53 <gireesh> sure, will ramp-up other engineer in team
15:39:25 <carloss> thank you
15:41:40 <carloss> other than this change I brought up and the share encryption series, is there another change you'd like to bring up on this meeting?
15:42:49 <carloss> taking silence as no
15:42:59 <carloss> #topic Bug Triage (vhari)
15:43:08 <carloss> #link https://etherpad.openstack.org/p/manila-bug-triage-pad-new (Bug Triage etherpad)
15:43:16 <vhari> o/ everyone
15:43:23 <vhari> lets dive in
15:43:24 <vhari> #link https://bugs.launchpad.net/manila/+bug/2112603
15:43:33 <vhari> with basic triage
15:44:25 <carloss> hmm, maybe we need some confirmation but seems like a real issue
15:44:44 <vhari> ack
15:45:03 <carloss> apparently a failover issue
15:45:05 <vhari> has anyone else experienced this bug?
15:45:16 <carloss> gireesh: could you please take a look at this? or someone at the netapp team?
15:45:22 <carloss> we need to confirm the behavior
15:45:39 <gireesh> sure, we know the issue, one of our customer is hitting this
15:45:44 <carloss> ah, sure
15:45:57 <vhari> ty for confirming gireesh
15:46:00 <carloss> i'd say medium prio
15:46:11 <carloss> gireesh: do you guys have a fix in mind?
15:46:20 <gireesh> yes, they are hitting this in case of HA failover
15:47:06 <vhari> gireesh, is anyone looking at a possible fix
15:47:22 <gireesh> yes, we have some fix in our mind. We creating the LIF on each nodes, due to that in case of failover, LIF creation is failing for one node
15:48:26 <gireesh> we will add the fix, if node is down or in failover state, we will not create the LIF on that node. apart form this, there are few customer they don't wanted to create the LIF on each node, we'll fix that issue also
15:48:44 <carloss> gireesh: ack, thanks for the update
15:49:34 <vhari> gireesh, was this due to a transient network issue?  or reproduced?
15:50:21 <gireesh> reproduced
15:50:47 <vhari> ty gireesh , pls update the bug when you get a chance
15:50:52 <vhari> gireesh++
15:51:10 <vhari> carloss, that's a wrap for bugs today .. back to you :)
15:51:12 <gireesh> sure, will assign  this to me
15:51:19 <carloss> gireesh++
15:51:23 <carloss> thanks vhari
15:51:30 <carloss> #topic Open Discussion
15:52:08 <carloss> so today we've some first timers in the meeting
15:52:30 <carloss> (I think they dropped :D)
15:52:31 <carloss> haha
15:53:40 <vhari> :)
15:54:04 <vhari> getting late in some TZs
15:54:08 <carloss> haha
15:54:12 <carloss> indeed
15:54:22 <carloss> I'd like to share that RianeTorres[m] (RealRTorres), ChristianEspinal[m] and jessekendall[m] are the new interns for this internship round from Valencia College
15:54:33 <carloss> we've been working with Valencia College for some time now
15:54:57 <carloss> and students have been helping us to pursue changes for openapi, manila-ui, python-manilaclient
15:55:06 <carloss> there's a lot that is being done with their help
15:55:25 <carloss> they got disconnected but I'll share the meeting logs with them later
15:55:31 <carloss> so I'd like to welcome them
15:55:35 <vhari> welcome to the community y'all
15:55:56 <carloss> you are likely seeing some pings for them on the channels :)
15:57:32 <carloss> and that's all I had for today's meeting
15:57:35 <carloss> let's wrap up
15:57:38 <carloss> thank you for participating
15:57:46 <carloss> let's get back to #openstack-manila
15:57:52 <carloss> have a great day!
15:57:56 <carloss> #endmeeting