Thursday, 2025-12-11

*** bauzas1 is now known as bauzas00:52
*** mhen_ is now known as mhen02:09
*** vhari_ is now known as vhari14:55
carloss#startmeeting manila15:00
opendevmeetMeeting started Thu Dec 11 15:00:15 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
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
opendevmeetThe meeting name has been set to 'manila'15:00
carlosscourtesy ping: dviroel vhari gouthamr carthaca Sai ashrodri gireesh Kumar_T15:00
Kumar_THi15:00
vharihi15:00
VolodymyrBoiko[m]Hi15:00
dviroelo/15:00
Saio/15:01
kpdevhi15:02
carlosso/ hello everyone15:03
gouthamro/15:03
carlossgood to be back after one week of PTO, one week of holidays and another week that I was unable to join as I had an appointment15:03
carlossall I can tell is that I missed y'all15:03
carlossand special thanks to gouthamr for running the meetings in my absence15:04
carlossI was following last week's meeting and chatted a bit in #openstack-manila after it happened15:04
carlossall good discussions15:04
carlossalright, let's get started15:05
carlossour agenda for today:15:05
carloss#link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting (Weekly meeting agenda)15:05
* carloss just made a late addition to it15:06
carlossbut a good one15:06
gireeshHi15:06
carlosso/15:06
carlosslet's start with our announcements15:07
carloss#topic Announcements15:07
carlossSchedule and Deadlines15:07
carloss#link https://releases.openstack.org/gazpacho/schedule.html (Gazpacho Schedule)15:07
nileshthathagarhi15:07
carlosso/15:07
carlossSpec freeze is next week. We can dive into the proposed specs in the review focus time15:08
carlossI believe we're in a good shape so far15:08
carlossthe gazpacho 2 milestone will happen at the very first week of the next calendar year15:08
carlossso if you're targeting a change for that milestone, please let us know15:08
carlossso that we can get reviewer's attention before people start disappearing for their well-deserved PTOs15:09
carlossthat's all I had regarding our schedule subject15:10
kpdev@carloss : I will address minor comment from carloss today, so that we can merge if possible as already netapp have couple of +1s and yours +2/15:10
carlosskpdev: no worries about it, it's too minor15:11
carlossif people are okay with the content, we can merge it15:11
carlossbut if you need to submit another patch set for some reviewer you got from someone15:11
carlossregarding content and so on15:11
carlossthen please address it15:11
kpdevack15:11
carlosskpdev: thanks for looking into it though :)15:12
carlossthat's all I had in terms of schedule15:12
carlosswe can switch to the next very exciting announcement 15:12
carlossWe are starting a new outreachy internship this week!15:12
carlossgouthamr and I are mentoring RoseKimondo[m] on this round, and we will be focusing on manila UI15:13
carlossyou might have crossed paths with RoseKimondo[m] considering all her activity during the project contribution phase15:13
carloss#link https://review.opendev.org/q/owner:rosewairimu1@gmail.com (Rose's contributions so far)15:14
carlossso please, join me on welcoming RoseKimondo[m] as our Manila outreachy intern :D15:14
carlosswelcome RoseKimondo[m], we're very happy and lucky to have you working with us!15:14
RoseKimondo[m]Hi everyone. I'm Rose and I'll be interning from now till March. Pleased to meet you all and I'm looking forward to learning from you. 15:14
RoseKimondo[m]Thank you. I'm happy to join the team too.15:15
gouthamrwelcome RoseKimondo[m] , super happy to have you here15:16
Anoop_ShuklaWelcome RoseKimondo[m]!15:16
vhariwelcome RoseKimondo[m] 15:16
carlossawesome! very excited and looking forward to all the fun15:18
carlossswitching to the last announcement of today's meeting15:19
carlosswe're approaching the end of this year, which means that some companies have year-end shutdowns and some folks will also take time off15:19
carlossthe last two manila upstream weekly meetings of this year are happening on Dec 25th and Jan 1st, which traditionally people are off, as these dates are holidays in a bunch of countries15:19
carlossshould be no surprise what I'm about to say, but: let's cancel the last two meetings of this year15:20
gouthamr+115:20
carlosswe'll keep the next week's meeting (Dec 17th), as it is spec freeze 15:20
carlosswe'll be back to our regular weekly meeting schedule on Jan 8th15:21
carlossthat's all I had for $topic15:21
carlossdo you have any other announcement you'd like to share with the team today?15:21
carlosstaking silence as no15:23
carloss#topic Review Focus15:23
carlossI'd like to use the allocated review focus time today to talk about the specs15:24
carlosswhich we had another one that is targeted for this cycle merged as we have this meeting15:24
carlosswhat merged so far15:24
carloss#link https://review.opendev.org/c/openstack/manila-specs/+/959548 (Remove v1 API)15:24
carloss#link https://review.opendev.org/c/openstack/manila-specs/+/932637 (Subnet deletion)15:24
carlossand15:24
carloss#link https://review.opendev.org/c/openstack/manila-specs/+/962706 (QoS types)15:24
carlossthank you everyone for the dedication and all of the reviews on the specs that are already merged at this point15:25
carlosswe're like 1 week ahead of the schedule, which is a good sign and helps us not being in a hurry next week15:25
carlossthe only spec that is yet to merge is:15:25
carloss#link https://review.opendev.org/c/openstack/manila-specs/+/968600 (Mount point name on manage)15:25
carlosswhich is already in a good shape15:25
carlossthe author received feedback and acted on it quickly15:26
carlossI added my vote and other reviewers did it too15:26
carlossthe spec is now in merge conflict though. I can fix that so that we don't slow it down15:27
eunkyung[m]thank you for the review15:27
carlosseunkyung[m]: anytime15:28
carlossthanks for all reviewers reviewing all specs. This is of extreme importance to the project and the features we are planning to introduce15:29
carlosseunkyung[m]: just so we don't clash changes: were you already fixing the merge conflict? if not, I have a patch ready15:30
carlossplease let me know if I should push it or not :)15:30
eunkyung[m]I didn’t make change yet. Please push it!15:31
carlossdone :)15:31
eunkyung[m]thanks!15:31
carlossanytime15:31
carlossalright, that's all I had for $topic. Is there another change you'd like to bring up for today's meeting?15:32
carloss#topic Bug Triage (vhari)15:35
carloss#link https://etherpad.openstack.org/p/manila-bug-triage-pad-new (Bug Triage etherpad)15:35
carlossvhari: o/ floor is yours15:35
vharity carloss 15:35
vhariso following the discussions at the PTG, we are adopting a more aggressive approach to bug backlog management15:35
vharithis will begin by targeting stale bugs that are over a year old and have had no recent activity in order of bug priority level15:36
vhariand moving forward, I will share stale bugs during the bug triage review and set to incomplete status for LP auto-expiry as deemed necessary15:36
vhariptal at the following for links for additional details, https://wiki.openstack.org/wiki/BugTriage#Task_4:_Review_incomplete_bugs_.28anyone.2915:37
vhariand https://documentation.ubuntu.com/launchpad/user/reference/bugs/bug-expiry/15:37
carlossvhari++ thanks for following up on this15:37
vharistale bug triage will be as time permits after the weekly new bug triage 15:38
vhariany question? 15:39
carlossvhari: no questions so far, and I'll try to make extra time for triaging more bugs during the weekly meetings15:39
vharity carloss :)   15:40
vharipls reach out if anything comes to mind later .. 15:40
vharifor today we have a short backlog of bugs to triage 15:40
vharistarting with #link https://bugs.launchpad.net/manila-ui/+bug/2132937 15:40
vharias usual looking for minor triage for this issue 15:41
vharibug is in progress .. 15:41
gouthamrI triaged this, the bug was initially filed against Manila-UI, but is in python-manilaclient as jjasek found15:42
* carloss just workflowed it15:42
vhariack, ty gouthamr and carloss 15:42
carlossapparently, a bug introduced in the graduation of share groups15:42
carlossgouthamr: thanks for triaging it and thanks jjasek for the fix :)15:43
vhari++15:43
vharinext up #link https://bugs.launchpad.net/python-manilaclient/+bug/2129614  15:43
carlossthis issue was found in a pair programming with Maria15:44
carlossand she kindly filed the bug report15:44
vhariseems straight forward and an easy repro 15:45
carlossstill a bug, and other metadata resources might have the same issue, so worth testing them as well15:45
carlossyeah, easily reproducible15:45
vhariset to lhf? 15:45
carlossi think so, yes15:46
carlosslow priority too, unless most of our consumers are automating calls to the client and using `-f json`15:47
carlosswhich I think it's not going to be most of the cases15:47
carlosss/low priority/low importance15:47
vhari+115:47
vhari#link https://bugs.launchpad.net/python-manilaclient/+bug/213059115:48
carlosslhf bug15:50
carlossbut nice catch by ruff 15:51
carlossgouthamr: thanks for the report15:51
vhariack, prio low 15:51
carlossanyone looking for a very lhf bug? :)15:51
gouthamrnot low prio i think15:51
gouthamrthere’s at least one user facing issue here; something we haven’t caught elsewhere with unit or functional testing15:52
carlossyep, agreed15:53
vhariack, if anyone in interesting in this lhf bug pls feel free to take this on :)15:54
SaurabhSingh[m]Just for the clarification lhf bugs are beginners friendly bugs?15:55
vhariSaurabhSingh[m], ack15:55
carlossSaurabhSingh[m]: yes15:55
carlossand my bad on this one, this bug is only for tracking15:55
carlossI got confused at the beginning, the fixes are proposed, but we have more lhf bugs15:56
carlosslhf = low hanging fruit15:56
carlossis a tag we use to identify fixes that are good for new contributors15:56
vharicarloss++ for breakdown 15:57
SaurabhSingh[m]Got it,  cool carloss: 15:57
vhariSaurabhSingh[m], if you are interested pls reach out to us15:57
vhariback to you carloss ... ty all for pitching in today 15:58
SaurabhSingh[m]Surely I'm going to take and work on it vhari:  will commentas well on the issue 15:59
SaurabhSingh[m]* Surely I'm going to take and work on it 15:59
SaurabhSingh[m]@_oftc_vhari:matrix.org:  will comment as well on the issue15:59
carlossvhari: thank you for the triage session!15:59
carlossSaurabhSingh[m]: awesome! thank you for contributing15:59
carlossreally appreciated15:59
carlossplease reach out to us in #openstack-manila in case you have any questions15:59
carlossalright, we're at the top of the hour16:00
carlosslet's wrap up this meeting and get back to #openstack-manila16:00
carlossthank you all for participating and for the efforts on the spec reviews and patches16:00
carlosshave a great day!16:00
SaurabhSingh[m]Absolutely carloss:  thank you 16:00
carloss#endmeeting16:00
opendevmeetMeeting ended Thu Dec 11 16:00:46 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
opendevmeetMinutes:        https://meetings.opendev.org/meetings/manila/2025/manila.2025-12-11-15.00.html16:00
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/manila/2025/manila.2025-12-11-15.00.txt16:00
opendevmeetLog:            https://meetings.opendev.org/meetings/manila/2025/manila.2025-12-11-15.00.log.html16:00

Generated by irclog2html.py 4.0.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!