15:00:06 <carloss> #startmeeting manila
15:00:06 <opendevmeet> Meeting started Thu Apr 25 15:00:06 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:06 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:06 <opendevmeet> The meeting name has been set to 'manila'
15:00:25 <carloss> courtesy ping: vhari gouthamr carthaca msaravan pulluri
15:00:35 <carthaca> hi
15:00:35 <vhari> hi
15:01:19 <ccokeke[m]> Hi
15:01:27 <ashrodri> o/
15:01:32 <msaravan> Hi
15:02:00 <gouthamr> o/
15:02:09 <haixin> o/
15:03:02 <carloss> o/ hello everyone
15:04:11 <carloss> it's been a couple of weeks since the last IRC meeting
15:04:16 <carloss> we have plenty to catch up on today
15:04:26 <carloss> today's meeting agenda:
15:04:27 <carloss> #link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting
15:05:25 <carloss> let's start with our announcements:
15:05:31 <carloss> #topic Announcements
15:05:37 <carloss> Schedule and Deadlines:
15:05:56 <carloss> #link https://releases.openstack.org/dalmatian/schedule.html
15:06:23 <carloss> we're ~20 days from our first milestone of this cycle
15:07:01 <carloss> and as you can see, the manila specific deadlines are already available for Manila
15:07:26 <carloss> I didn't hold up the change and the release team merged the change quickly
15:08:00 <carloss> but I'd like to gather your feedback. In case you would like to see some changes to our deadlines, please let me know and I'll be happy to work with you to accommodate
15:08:27 <carloss> that's all I had for announcements. Do you have an announcement to share with us?
15:08:39 <gouthamr> on the schedule, we have one bugsquash
15:09:21 <gouthamr> and it coincides with a holiday in the US - likely folks will try to take some time off around this time
15:09:48 <carloss> ah, good point gouthamr
15:10:06 <carloss> I think moving it 1 week earlier could have some negative impact on spec freeze
15:10:30 <carloss> would the week R-12 (Jul 8 - 12) be better?
15:11:20 <gouthamr> yes
15:13:45 <carloss> #link https://review.opendev.org/c/openstack/releases/+/917055
15:13:46 <carloss> :)
15:14:00 <gouthamr> lightening fast
15:14:50 <carloss> sounded like good timing to do it :p
15:15:01 <carloss> if there's any other feedback on the dates, please take it to the change
15:15:06 <carloss> and I'll be happy to address
15:15:19 <carloss> anything else you'd like to bring up?
15:16:19 <carloss> #topic PTG
15:16:48 <carloss> well, PTG was two weeks ago and I sent the summary email to the openstack-discuss mailing list
15:16:53 <carloss> hope y'all got it
15:16:56 <carloss> #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/3LXZO56M4OVJM6NJPV5QKURA2BGJS3NS/
15:17:25 <carloss> it's not that brief, but I tried my best to summarize the action items and our plans
15:18:08 <carloss> all the recordings from the PTG are available on YouTube as well:
15:18:09 <carloss> #link https://www.youtube.com/watch?v=Bhg4aT1B_vE&list=PLnpzT0InFrqCHg9lfMcPe136BU-27jt-x
15:18:40 <carloss> I created this playlist - but I just need to create a thumbnail for all the videos, to make it easier to identify
15:19:34 <carloss> so in case you missed something, please take a look at the videos. Meetpad always limited the videos under 1h30min, so some videos might end suddenly
15:20:12 <carloss> but you can look at the titles, because I tried to make it easier with specifying "Part 1, Part2" and so on
15:20:28 <carloss> I think that's everything I wanted to bring up regarding PTG
15:20:36 <carloss> do you have something else you'd like to share?
15:23:07 <carloss> #topic SQLAlchemy 2.0 aftermath
15:24:29 <carloss> gouthamr has kindly backported all the fixes for SQLAlchemy 2.0 to the 2024.1 branch
15:24:33 <carloss> and that has merged
15:24:35 <carloss> #link https://review.opendev.org/c/openstack/manila/+/915463
15:25:09 <carloss> and the fixes were shipped in the 18.1.0 release for Manila:
15:25:10 <carloss> #link https://review.opendev.org/c/openstack/releases/+/915996
15:25:59 <carloss> before we merged the change with the fixes, we had a job testing the changes in the 2024.1 branch, just to ensure they would work
15:26:03 <carloss> #link https://review.opendev.org/c/openstack/manila/+/915488
15:26:17 <carloss> so it seems to be all good at this point
15:26:37 <carloss> I believe we can go ahead and merged the job in the 2024.1 Caracal stable branch as well
15:26:58 <carloss> just to ensure it is being tested accordingly
15:27:13 <carloss> now we have some other possible action item to take:
15:27:23 <carloss> bumping our oslo.db version
15:28:27 <carloss> before we backported the changes, zigo reached out and told us the tests for Manila were failing in debian
15:29:01 <carloss> initially we thought that backporting and releasing the fixes would get that sorted out, but apparently some distros also expect us to bump our requirements version
15:29:32 <carloss> the upstream CI is not showing any issues, as you can see in the change I linked above
15:30:02 <gouthamr> we should do the requirements bump now
15:30:27 <carloss> yep, bumping the requirements would be appropriate
15:30:29 <gouthamr> but, technically, the openstack upper constraints on 2024.1 still have older versions of sqlalchemy and alembic
15:30:45 <gouthamr> so, i don't see the value in bumping the minimum version of oslo.db
15:31:20 <gouthamr> in 2024.1
15:32:04 <carloss> i agree
15:32:49 <zigo> carloss: I don't expect you to do it, I told you out of courthesy, as this was the reality, I'm fine with me keeping the version requirements for myself if you don't want to push it upstream (even though I would *advise* you to do so...).
15:34:49 <gouthamr> true... what we can do instead is match reality in the upper constraints for 2024.1 and bump up sqlalchemy and other library versions
15:35:02 <carloss> zigo: yep, and thank you for bringing this up and the suggestion :)
15:35:42 <gouthamr> but it'll be a hard sell because a number of openstack repos may yet have incompatible code
15:36:13 <gouthamr> for one, we are yet to bump the versions on the trunk branch: https://review.opendev.org/c/openstack/requirements/+/879743
15:37:10 <gouthamr> i proposed that we run a sqlalchemy2.0 job on stable/2024.1 for these reasons:
15:37:22 <gouthamr> #link https://review.opendev.org/c/openstack/manila/+/915488
15:38:23 <gouthamr> zigo: are you seeing any failures, even with the backports?
15:42:52 * gouthamr is this a netsplit?
15:43:16 <carloss> might be :)
15:43:23 <carloss> we can continue on #openstack-manila
15:43:34 <gouthamr> sure thing
15:43:35 <carloss> gouthamr: thank you for the suggestions
15:43:50 <carloss> and zigo: thank you for bringing this up
15:44:00 <carloss> on to the next topic...
15:44:03 <carloss> #topic Bug Triage (vhari)
15:44:13 <carloss> #link https://etherpad.openstack.org/p/manila-bug-triage-pad-new (Bug Triage etherpad)
15:44:32 <vhari> ty carloss
15:44:46 <vhari> have a bit of catch up due to missed sessions
15:44:55 <vhari> diving in :)
15:44:57 <vhari> #link https://bugs.launchpad.net/manila/+bug/2060776
15:48:17 * carloss got distracted with the code
15:48:35 <gouthamr> it’s a good suggestion; we do tune2fs right now when we resize
15:49:40 <carloss> I think when we mount as well too, no?
15:49:59 <carloss> mount the device i mean
15:50:16 <carloss> in the create_share
15:50:17 <carloss> #link https://github.com/openstack/manila/blob/master/manila/share/drivers/generic.py#L240
15:50:23 <carloss> this calls _mount_share
15:50:38 <carloss> #link https://github.com/openstack/manila/blob/master/manila/share/drivers/generic.py#L362
15:50:52 <carloss> which should be calling tune2fs
15:51:11 <carloss> I am speed reading the code,  might be wrong
15:51:43 <gouthamr> can be investigated; id suggest low priority/ low hanging fruit
15:52:04 <carloss> yes
15:52:10 <vhari> ++
15:52:30 <vhari> #link https://bugs.launchpad.net/manila/+bug/2060857
15:52:51 <vhari> ^^ carloss if time permitting today
15:53:29 <carloss> gouthamr: thank you for filing this bug
15:53:58 <carloss> maybe msaravan can help us find an assignee
15:54:28 <zigo> gouthamr: It still fails with SQLAlchemy 2.x: https://ci.debian.net/packages/m/manila/unstable/amd64/45799344/
15:55:00 <zigo> Though autopkgtest runs fine with 1.4.x
15:55:24 <carloss> but I think in short, what happens is: when there are special characters in the password, the error shows up in a weird way. We should be escaping the passwords from the conf file when they have special characters
15:58:16 <carloss> I think this bug has a low/medium prio and we can work with msaravan for finding an assignee :)
15:58:46 <vhari> carloss, ack
15:58:52 <carthaca> I've gotten used to this error and just hoped to wait it out until we switched to REST API :)
15:58:55 <msaravan> sure
15:59:25 <carloss> carthaca: oh, we might be able to get this done sooner then :D
15:59:39 <vhari> :) if no other input,  will wrap bugs for today
15:59:44 <carloss> ack, tyvm vhari
15:59:54 <vhari> ty folks for pitching in
15:59:56 <vhari> yw
16:00:07 <carloss> thank you everyone for joining today's meeting. Let's get back to #openstack-manila
16:00:10 <carloss> #endmeeting