15:00:12 <carloss> #startmeeting manila
15:00:12 <opendevmeet> Meeting started Thu Jul  6 15:00:12 2023 UTC and is due to finish in 60 minutes.  The chair is carloss. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:12 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:12 <opendevmeet> The meeting name has been set to 'manila'
15:00:29 <gouthamr> o/
15:00:41 <carloss> courtesy ping: vkmc dviroel felipe_rodrigues vhari carthaca
15:00:43 <felipe_rodrigues> o/
15:00:48 <carthaca> hi
15:00:59 <helenadantas[m]> o/
15:01:02 <MatheusAndrade[m]> o/
15:01:07 <ashrodri> o/
15:01:15 <thiagoalvoravel> o/
15:01:27 <haixin> o/
15:04:02 <caiquemello[m]> o/
15:04:06 <carloss> hello everyone
15:04:13 <vhari> o/
15:04:17 <carloss> and welcome!
15:04:30 <carloss> back to the regular meeting
15:04:33 <carloss> #link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting
15:04:53 <carloss> thank you for everyone that participated in the last week's collab review
15:05:05 <carloss> and thanks kpdev for walking us through your changes
15:05:55 <carloss> I'm working with felipe_rodrigues to upload the recordings to youtube, but I think we'll get this done soon
15:06:05 <carloss> first topic of today's meeting
15:06:08 <carloss> #topic Announcements
15:06:14 <carloss> Schedule and Deadlines:
15:06:20 <carloss> #link https://releases.openstack.org/bobcat/schedule.html
15:07:07 <carloss> this is m-2 week! so if you have a change ready to go and you're targeting it for this week, please let me know
15:08:19 <carloss> we are looking to have this change merged:
15:08:21 <carloss> #link https://review.opendev.org/c/openstack/python-manilaclient/+/869709
15:08:35 <carloss> felipe_rodrigues and I chatted and he is working on an updated patch :)
15:09:03 <carloss> last week was spec freeze and as I mentioned, I think we'd be okay if that deadline was pushed by one week
15:09:14 <carloss> two out of the three candidate specs have already merged:
15:09:39 <carloss> #link https://review.opendev.org/c/openstack/manila-specs/+/881894
15:09:46 <carloss> #link https://review.opendev.org/c/openstack/manila-specs/+/881187
15:09:57 <carloss> gouthamr felipe_rodrigues: thank you for following up on the spec and good job!
15:10:22 <carloss> we have another spec that we are still targeting for this week in progress:
15:10:24 <carloss> #link https://review.opendev.org/c/openstack/manila-specs/+/881934
15:10:31 <gouthamr> chiming in for the last one - i was mostly out since our last meeting here, and couldn't update that one -- but, i wanted to vastly simplify it
15:11:10 <gouthamr> it might end up looking like a lite spec, and should be far less controversial..
15:12:32 <gouthamr> (no database changes for one)
15:13:13 <gouthamr> i'm making the edits now, and can push this up asap - can i have an extension on this merge deadline to have some eyes on it?
15:13:54 <carloss> gouthamr: sure
15:14:04 <carloss> thanks for working on the updates
15:15:07 <gouthamr> thank you; it should be up shortly!
15:15:49 <carloss> gouthamr++ thanks!
15:17:55 <carloss> next milestone to keep in mind (if you're a driver maintainer willing to have your driver merged during this release) is https://releases.openstack.org/bobcat/schedule.html#b-manila-new-driver-deadline
15:18:45 <carloss> we have one driver currently being worked on
15:18:56 <carloss> #link https://review.opendev.org/c/openstack/manila/+/880527 (Adds a new Manila driver for Dell PowerFlex storage backend)
15:19:06 <carloss> feedback on it would be welcome
15:19:34 <carloss> kpdev felipe_rodrigues caiquemello[m] (and netappers in general) - could you please take a look?
15:19:40 <felipe_rodrigues> sure
15:19:50 <carloss> thanks felipe_rodrigues
15:20:12 <caiquemello[m]> yeap
15:20:15 <kpdev> ok
15:20:22 <carloss> that's all I had for announcements. Is there something you would like to share with us today?
15:22:28 * carloss taking silence as no
15:22:35 <carloss> #topic Review focus
15:23:30 <carloss> #link https://etherpad.opendev.org/p/manila-bobcat-review-focus#L18
15:23:55 <carloss> there are a couple of changes under m-2, but I think most of them will be actually m-3
15:24:02 <carloss> but I think this reflects our moment
15:24:08 <carloss> in terms of what to focus
15:26:53 * carloss adds https://review.opendev.org/c/openstack/manila/+/887078 to the list
15:30:11 <carloss> that's all I had for review focus - is there a change you'd like to bring to our attention now?
15:31:40 * carloss takes silence as no
15:31:53 <carloss> #topic Bug Triage (vhari)
15:31:57 <carloss> #link https://etherpad.opendev.org/p/manila-bug-triage-pad-new
15:32:01 <carloss> vhari: floor is yours :)
15:32:09 <vhari> ty carloss :)
15:32:39 <vhari> we have a few bugs to triage today .. starting with #link https://bugs.launchpad.net/manila/+bug/2025075
15:35:30 <gouthamr> i like chaunm's suggestion on how this can be handled in the API - feels like a low-hanging-fruit
15:35:42 <carloss> gouthamr++
15:35:53 <vhari> ack, and an enhancement request
15:36:47 <vhari> can we assign  importance and other triage fields at this time?
15:37:30 <gouthamr> medium? we need an assignee if we need a target milestone
15:37:40 <carloss> medium sounds right
15:37:41 <felipe_rodrigues> if you think about the scripting I'd say medium
15:38:16 <felipe_rodrigues> it breaks the script logic
15:38:19 <carloss> felipe_rodrigues: are you aware of someone in the netapp team that would benefit from learning some API code? :)
15:38:38 <felipe_rodrigues> I think so!
15:39:52 <felipe_rodrigues> you could assign it to helenadantas[m]
15:39:52 <carloss> usually writing API code is fun, and easy to test, it's good to have this experience
15:40:19 <carloss> thanks felipe_rodrigues
15:40:20 <felipe_rodrigues> are you confortable, helenadantas[m] ?
15:41:13 <felipe_rodrigues> it probably requires some sleep on the code.. there is a small window where the bug occurs.. for dev env, probably we might not catch it easily
15:42:02 <helenadantas[m]> felipe_rodrigues: yes
15:42:12 <caiquemello[m]> helenadantas: ++
15:42:18 <carloss> helenadantas[m]++
15:42:23 <vhari> helenadantas[m]++
15:42:27 <carloss> tyvm felipe_rodrigues helenadantas[m] - please feel free to ping in case you have questions
15:42:53 <helenadantas[m]> carloss: ok
15:43:03 <vhari> up next #link https://bugs.launchpad.net/manila/+bug/2025641
15:46:00 <carloss> hmm, sounds like it's not that difficult to reproduce
15:46:41 <carloss> "All happened within 15 minutes (part of a CI/CD) after share create"
15:46:41 <carloss> carthaca: have you seen this in production?
15:48:11 <carthaca> yes, sadly in production - it was not caught by our own ci, but by one of our customers
15:48:33 <carloss> :/
15:49:04 <carloss> felipe_rodrigues: can we have one of the netappers working on this?
15:49:26 <felipe_rodrigues> I'm taking this one: https://bugs.launchpad.net/manila/+bug/1960239
15:50:23 <carthaca> most of the time, our tests don't put data on the shares - lesson learned here
15:50:58 <felipe_rodrigues> they are very similar issue.. I think the idea was the deferred deletion as a solution.. The new bug claims that this option won't work, though.. am I right ?
15:51:11 <carthaca> ack
15:52:08 <felipe_rodrigues> Nice.. I can take both, since they seem very similar.. we can try a similar approach
15:52:27 <carloss> thanks felipe_rodrigues
15:52:37 <carthaca> It does not have to rename, there can be other creative ways of bookkeeping to be deleted entities
15:52:38 <gouthamr> is this the one where we discussed an implementation for deferred deletion driven by the share manager?
15:52:48 <felipe_rodrigues> yeap
15:53:13 <gouthamr> i.e., start deleting, return and periodically check for the deletion to have gone through?
15:54:54 <felipe_rodrigues> yeap.. the problem is that carthaca mentioned that we cannot rename busy volumes/snapshots
15:56:17 <gouthamr> ack; if you can add some other kind of marker directly on the backend - it'd be great; else, you have driver private data
15:58:08 <felipe_rodrigues> driver private data may work.. let's see during the implementation
15:58:25 <felipe_rodrigues> can we implement it without an approved spec ?
15:59:15 <carthaca> yeah, my orphan detection would like some marker :) else it would complain: 'this volume looks like a manila share, but manila does not know about it'
15:59:47 <gouthamr> > can we implement it without an approved spec ? --- no
15:59:58 <gouthamr> > yeah, my orphan detection would like some marker 😊 --- agree
16:00:26 * carloss time check
16:00:46 <gouthamr> > can we implement it without an approved spec ? --- ugh, i mean, this is simple enough and doesn't need a spec imo
16:01:09 <vhari> felipe_rodrigues++ gouthamr++ carthaca++
16:01:49 <carloss> >  this is simple enough and doesn't need a spec imo
16:01:49 <carloss> ++
16:01:53 <felipe_rodrigues> nice.. let's write one spec.. thank you
16:02:09 <carloss> thanks for the bug reports carthaca chuanm
16:02:33 <carloss> so, medium - felipe_rodrigues as an assignee - m-3
16:02:43 * carloss wrapping up
16:02:47 <felipe_rodrigues> I think m-3 is not possible
16:02:53 <felipe_rodrigues> since we need to approve the spec earlier
16:02:55 <felipe_rodrigues> right ?
16:03:14 <carloss> I think we won't need a spec
16:03:17 <carloss> :D
16:03:26 <carloss> I think that's gouthamr's feeling as well
16:03:42 <carloss> "--- ugh, i mean, this is simple enough and doesn't need a spec imo"
16:03:49 <carloss> let's continue on #openstack-manila
16:03:56 <carloss> thank you for joining this meeting!
16:03:57 <vhari> felipe_rodrigues, assigned m-3, pls feel free to revise as needed
16:04:09 <carloss> felipe_rodrigues:++ thanks for working on this
16:04:13 <carloss> #endmeeting