15:00:37 <gouthamr> #startmeeting manila
15:00:37 <opendevmeet> Meeting started Thu Apr 13 15:00:37 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:37 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:37 <opendevmeet> The meeting name has been set to 'manila'
15:00:45 <felipe_rodrigues> hi
15:00:59 <lucasmoliveira059> o/
15:01:00 <thiagoalvoravel> hi
15:01:01 <haixin> o/
15:01:04 <ashrodri> o/
15:01:04 <helenadantas[m]> hi
15:01:08 <nahimsouza> Hi
15:01:17 <gouthamr> hello everyone! o/
15:01:35 <gouthamr> courtesy ping: vkmc dviroel ecsantos vhari carthaca
15:02:27 <luizsantos[m]> o/
15:02:59 <gouthamr> welcome; we're lacking a few folks here to PTO and travel
15:03:15 <gouthamr> maybe this will be a short meeting :) let's get started
15:03:20 <gouthamr> #topic Announcements
15:04:09 <gouthamr> the agenda doesn't have any new items, but i'll not mention that i set it just minutes out :D
15:04:12 <gouthamr> #link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting
15:04:31 * gouthamr has a knack
15:05:03 <gouthamr> we've begun the process of transitioning the "xena" release to extended-maintenance
15:05:09 * dviroel o/
15:05:16 <vhari> o/
15:05:23 <gouthamr> #link https://review.opendev.org/c/openstack/releases/+/878897 ([manila] Transition Xena to EM)
15:06:08 <gouthamr> to facilitate that, we cut the final releases from that branch for manila and python-manilaclient
15:06:47 <gouthamr> there's also a bunch of other release activity on later branches
15:06:58 <gouthamr> #link https://lists.openstack.org/pipermail/release-announce/2023-April/thread.html (manila releases)
15:07:37 <gouthamr> a reminder about what "extended maintenance" means for us:
15:08:02 <gouthamr> the branch remains open on gerrit - "All bugfixes (that meet the criteria) are appropriate. No Releases produced, reduced CI commitment."
15:08:18 <gouthamr> the criteria itself is described here:
15:08:31 <gouthamr> #link https://docs.openstack.org/project-team-guide/stable-branches.html#extended-maintenance (Extended Maintenance doc)
15:09:45 <gouthamr> in this group, we've maintained CI with best effort for these really old branches... but once that starts falling off, you'll know which fixes are appropriate and which ones we may not choose to
15:11:16 <gouthamr> i'm also looking to get new releases with python-manilaclient (including SDK/CLI changes for manila APIs we've shipped in Antelope) and manila-tempest-plugin (RBAC and new tests)
15:11:58 <gouthamr> so calling out to both, patch authors and reviewers to revive pending efforts and lets get this done in the next week or so if possible
15:12:54 <gouthamr> my next announcement is regarding the bobcat schedule
15:13:24 <gouthamr> carloss has created a patch with manila-specific additions to the release tracker
15:13:41 <gouthamr> #link https://review.opendev.org/c/openstack/releases/+/879998 ([manila][bobcat] Add project tracking schedule)
15:14:13 <gouthamr> #link https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_3ac/879998/2/check/openstack-tox-docs/3ac62f1/docs/bobcat/schedule.html (CI rendered version of the schedule page)
15:15:05 <gouthamr> we're 24 weeks away from the Bobcat release; but under 20 weeks from the feature freeze
15:15:54 <gouthamr> it seems like a long time, but it honestly isn't by our past experience - the calendar is a global conspiracy
15:17:15 <gouthamr> our first event on the schedule though is the bobcat-1 milestone, which is in 4 weeks; it's a bug milestone for us
15:17:39 <gouthamr> so if you're actively working on bugs targeted to this date, please note the date: May 22 - May 26
15:17:45 <gouthamr> grr
15:17:51 <gouthamr> May 08 - May 12
15:18:23 <gouthamr> i was skipping ahead to the exciting week: May 22 - May 26 - which is when the Hackathon's planned
15:18:49 <gouthamr> i think we're still looking for ideas on what we can all hack on together..
15:19:51 <gouthamr> alright, last thing on the announcements
15:19:55 <gouthamr> we're not meeting next week
15:21:17 <gouthamr> we canceled that meeting because a number of the regular attendees are missing; we can communicate via #openstack-manila here, or on the openstack-discuss ML
15:21:36 <gouthamr> that's all i had for $subject today
15:21:46 <gouthamr> anyone else has anything to announce?
15:24:37 <gouthamr> okay, lets move on
15:24:42 <gouthamr> #topic Review Focus
15:24:46 <gouthamr> #link https://etherpad.opendev.org/p/manila-bobcat-review-focus
15:25:04 <gouthamr> ^ please go ahead and start throwing things in there
15:26:00 <gouthamr> i was hoping to get some eyes on the sqlalchemy changes:
15:26:02 <gouthamr> #link https://review.opendev.org/q/topic:sqlalchemy-20+project:openstack/manila
15:27:16 <gouthamr> if anyone's able to help, this is a massive effort from stephenfin and will need multiple pairs of eyes
15:29:08 * gouthamr plays some roulette and picks on people randomly
15:29:28 <gouthamr> ashrodri, renanv - do you have some bandwidth to look at these changes?
15:31:33 <gouthamr> ^ you can let me know later; lets move on..
15:31:57 <gouthamr> does any other review need attention atm?
15:33:49 <gouthamr> good stuff, lets get to the next thing on the agenda
15:33:52 <gouthamr> #topic: Bug Triage (vhari)
15:33:58 <gouthamr> o/ vhari, floor is yours
15:34:09 <vhari> \o ty gouthamr
15:34:23 <vhari> so there were NO new bugs this week :)
15:34:34 <vhari> will take this change to revisit some oldies
15:34:37 <vhari> #link https://bugs.launchpad.net/manila/+bug/2009083
15:35:00 <vhari> one fix merged and 2nd one has merge conflict
15:35:33 <vhari> so we need anything else to resolve this bug?
15:35:50 <gouthamr> ah! this one
15:36:00 <gouthamr> so i think we'll stick with the "workaround" that we currently have
15:36:27 <gouthamr> which is skipping one set of the duplicate shrink/extend tests we were doing with ipv4 and ipv6
15:37:02 <gouthamr> i shared at the PTG that putting ceph storage on non-local storage isn't a viable option; so i'll abandon https://review.opendev.org/c/openstack/manila-tempest-plugin/+/856540
15:37:23 <gouthamr> wrong link; this is the right one: https://review.opendev.org/c/openstack/manila-tempest-plugin/+/876239
15:37:54 <gouthamr> it's abandoned now
15:38:03 <gouthamr> so we can close this bug vhari
15:38:37 <gouthamr> ashrodri is working on the long term solution of replacing this job with a better suited cephadm job
15:38:43 <vhari> gouthamr, ack, good to know
15:39:44 <vhari> #link https://bugs.launchpad.net/manila/+bug/1886904
15:40:08 <vhari> we planned to work on it in A cycle ..
15:40:46 <vhari> looping back, to get some traction
15:41:04 <gouthamr> yep; i'm hoping a combination of https://review.opendev.org/c/openstack/manila/+/879012 and https://review.opendev.org/c/openstack/manila/+/879013
15:41:08 <gouthamr> should address this issue
15:41:32 <gouthamr> i can check and reference the bug in those fixes
15:42:19 <vhari> gouthamr, sounds like a plan, ty
15:42:45 <gouthamr> i've set the milestone and updated the bug
15:43:09 <vhari> gouthamr++
15:43:11 <vhari> last but not least ... would like to share a lhf   bug in case someone is interested to pick it up :)
15:43:19 <vhari> #link https://bugs.launchpad.net/manila/+bug/1867030
15:44:18 <vhari> if anyone is interested, pls feel free to assign it to self
15:44:37 <vhari> if no other thoughts.. that's a wrap for bugs
15:45:12 <gouthamr> ++ thank you very much vhari
15:45:36 <gouthamr> https://bugs.launchpad.net/manila/+bug/1867030 was offered to potential outreachy candidates
15:45:41 <vhari> yw gouthamr
15:45:56 <gouthamr> anyone here is welcome to grab it too
15:46:14 <gouthamr> i feel like we need a re-triage of our LHFs
15:46:48 <vhari> good to know,  yeah I plan to share one with the community here
15:46:57 <vhari> just as we share stale bugs
15:47:13 <gouthamr> yep! it certainly helps
15:47:27 <vhari> to help with the lhf backlog as well .. good opportunity for folks who want to  learn and pitch in
15:47:42 <gouthamr> yes
15:48:24 <gouthamr> #topic Open Discussion
15:48:49 <gouthamr> i see we've left a lot of bugs in new or in-progress states in https://launchpad.net/manila/+milestone/antelope-rc1
15:49:12 <gouthamr> if you are assigned, please take a look and retarget these to a milestone in bobcat
15:49:47 <vhari> gouthamr,  ack, I wanted to suggest adding a new status to indicted the bug was reviewed with the community
15:50:09 <vhari> since we review all new bugs,  it would help to flag them as such
15:50:12 <gouthamr> ah; it can help.. "Triaged" ?
15:50:14 <vhari> thoughts?
15:50:44 <vhari> triaged is slightly different
15:51:28 <vhari> in this case, we have not reproduced or taken any real action to resolve the issue .. only discussed it and added comments in the bug
15:52:00 <gouthamr> ah i see
15:53:06 <gouthamr> #link https://help.launchpad.net/Bugs/Statuses
15:53:16 <gouthamr> i wish there was a way to throw in a custom status
15:53:18 <vhari> 'new'  can  be misconstrued  as  no action done
15:54:04 <gouthamr> yes; "Confirmed" is something we can use - but anyone other than the reporter can set it
15:54:27 <gouthamr> i wonder if a tag can help instead?
15:55:46 <vhari> tag could be a next best option if status is not customized
15:56:06 <vhari> no need to decide today,  just wanted to  get a pulse on it
15:56:38 <vhari> if we like the idea, we can discuss options offline or in manila channel
15:56:51 <gouthamr> +1 thanks for bringing it up
15:56:59 <gouthamr> i like the idea of a tag
15:57:05 <vhari> ++
15:57:51 <gouthamr> its extensible, in case we want more classifications in the future
15:58:26 <gouthamr> tags are freeform, but, we can configure "official" ones that get bubbled to the top of the list on the bug page
15:59:23 <gouthamr> some doc on how launchpad team uses them: https://dev.launchpad.net/LaunchpadBugTags
15:59:48 <gouthamr> alright, its time to wrap this up here
15:59:54 <gouthamr> see you folks here in two weeks :)
16:00:11 <gouthamr> thank you for attending and participating!
16:00:17 <gouthamr> #endmeeting