15:00:11 <carloss> #startmeeting manila
15:00:11 <opendevmeet> Meeting started Thu Apr  6 15:00:11 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:11 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:11 <opendevmeet> The meeting name has been set to 'manila'
15:00:25 <felipe_rodrigues> hi
15:00:30 <lucasmoliveira059> o/
15:00:34 <nahimsouza[m]> o/
15:00:44 <caiquemello[m]> hello!
15:00:47 <haixin> O/
15:01:01 <vhari> o/
15:01:03 <thiagoalvoravel> o/
15:01:04 <carloss> courtesy ping: vkmc dviroel gouthamr carthaca
15:01:40 <gouthamr> o/
15:02:30 <HelenaDantas[m]> o/
15:03:03 <carloss> hello everyone!
15:03:07 <carloss> g'day!
15:03:51 <carloss> great to see you here today
15:04:01 <carloss> let's get started with our shorter than usual agenda for today:
15:04:04 * dviroel o/
15:04:04 <carloss> #link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting
15:04:10 * carloss waves at dviroel
15:04:57 <carloss> first topic of the day:
15:04:59 <carloss> #topic Announcements
15:05:19 <carloss> Schedule and Deadlines:
15:05:25 <carloss> #link https://releases.openstack.org/bobcat/schedule.html
15:06:18 <carloss> we are in the third week of this release cycle
15:06:24 <carloss> so things are a bit more calm now
15:06:45 <carloss> we're 5 weeks away from m-1
15:07:32 <carloss> on the next thing for announcements
15:07:43 <carloss> I would like to thank you for the participation and feedback on the PTG
15:08:08 <carloss> I am happy with the collaboration we had and the deep and meaningful discussions around the proposed topics
15:08:25 <carloss> it resulted in a good list of AIs and things to keep in mind during this cycle
15:09:08 <carloss> the recordings for PTG are up since last week, so in case you want to watch the discussions or get back to a certain discussion, here's the Bobcat PTG youtube playlist:
15:09:13 <carloss> #link https://www.youtube.com/watch?v=gefbYrzRD04&list=PLnpzT0InFrqDW_djitgCiFzwhBFdvoRBC
15:09:25 <carloss> and, for the PTG summary:
15:09:29 <carloss> #link https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033202.html
15:09:41 <carloss> I tried to capture the essence of the discussions and the AIs and add them to this summary
15:11:44 <carloss> is there something you would like to add to this PTG topic? :)
15:15:20 <carloss> moving on...
15:16:08 <carloss> I'll be on PTO for the next two weeks
15:16:34 <carloss> gouthamr: has kindly offered to run the next week's weekly meeting
15:16:40 <carloss> (thanks gouthamr)
15:16:55 <gouthamr> ++
15:17:47 <carloss> but for the week after (Apr 20th) is a different scenario, as gouthamr would possibly be OOO too... so I would like to ask you: is there anyone interested in running the Apr 20th manila upstream meeting?
15:19:15 <carloss> Apr 21st is a holiday in Brazil, and if folks are planning to extend the holiday, then it would be a massive drop in the audience
15:19:28 <carloss> the second option would be cancelling the Apr 20th weekly meeting
15:20:33 <gouthamr> i'd be okay skipping
15:20:55 <gouthamr> we can keep an eye on the ML in case there's something that needs attention
15:21:37 <vhari> carloss, I  am available to run the meeting on 20th  if we decide to keep it
15:23:57 <haixin> i am ok for skip too. :)
15:24:05 <carloss> netappers + haixin: what's your take?
15:24:13 <carloss> haixin beat me to it :D
15:24:36 <haixin> what holiday in Brazil?
15:24:40 <nahimsouza[m]> i'll be working, but i'm ok for skipping too
15:25:26 <felipe_rodrigues> skip+1
15:26:07 <thiagoalvoravel> I think it's ok skip
15:26:08 <caiquemello[m]> skip+1
15:26:16 <carloss> haixin: https://www.officeholidays.com/holidays/brazil/tiradentes-day
15:26:16 <carloss> :D
15:27:07 <carloss> thanks for offering to run the call vhari
15:27:45 <carloss> I think we can skip it in that day and keep an eye on the ML as suggested by gouthamr
15:28:04 <carloss> I'll send an email to the ML to announce that then
15:28:06 <haixin> happy holidy :D
15:28:15 <carloss> haixin: thank you! :D
15:28:19 <carloss> thanks for your input folks
15:28:37 <carloss> next topic...
15:28:41 <carloss> #topic Bug Triage
15:28:52 <carloss> #link https://etherpad.opendev.org/p/manila-bug-triage-pad-new
15:28:57 <carloss> vhari: floor is yours
15:29:35 <vhari> carloss, ty
15:29:49 <vhari> lets dive it
15:29:51 <vhari> #link https://bugs.launchpad.net/manila/+bug/2015328
15:30:18 <vhari> looking for minor triage
15:32:44 <carloss> sounds like a low hanging fruit to implement in case we decide to proceed with it
15:32:56 <carloss> a bit of a bug/rfe
15:33:19 <carloss> I'd say low/medium prio and would ask if someone is willing to work on this LHF :D
15:35:02 <vhari> ack lhf for this one as well?
15:35:45 <felipe_rodrigues> I am not totally sure.. is It about block users from set active replica state ?
15:37:33 <carloss> I understood as not allow users to modify an active replica state
15:38:16 <felipe_rodrigues> uhh.. I see.. seems LHF
15:38:49 <carloss> but, would that be expected? I mean, if I know something has happened to an active replica and I want to set its state to error, I should be able to
15:39:25 <felipe_rodrigues> I was wondering it
15:39:50 <felipe_rodrigues> is there any use case ?
15:39:59 <gouthamr> feels like we want a safety for the trigger to shoot ourselves in the foot
15:40:23 <gouthamr> the course of actions that happened seems dangerous
15:41:18 <gouthamr> we can prevent this, and provide a "force" flag?
15:41:25 <carloss> yep - that would be nice
15:41:30 <felipe_rodrigues> yep
15:41:43 <carloss> --force would be required only when it's the active replica
15:42:13 <carloss> ^ maybe design it like this
15:42:16 <carloss> still a lhf :D
15:42:26 <felipe_rodrigues> medium ?
15:43:08 <carloss> medium++
15:43:39 <vhari> ack .. moving on to the next lhf :D
15:43:41 <vhari> #link https://bugs.launchpad.net/manila/+bug/2015325
15:44:09 <carloss> lhf, low?
15:44:33 <felipe_rodrigues> low LHF +1
15:44:36 <vhari> agreed +1
15:44:52 <vhari> anyone interested to look at this?
15:45:16 <felipe_rodrigues> I think NetApp can take this one
15:45:56 <vhari> +1 anyone on in particular
15:46:08 <felipe_rodrigues> Add me and I will find someone later
15:46:20 <vhari> awesome felipe_rodrigues++
15:46:29 <carloss> felipe_rodrigues++
15:46:36 <vhari> next #link https://bugs.launchpad.net/manila/+bug/2013026
15:49:09 <felipe_rodrigues> I could not find which the backend storage is used
15:49:57 <carloss> ++
15:50:54 <carloss> more logs would be needed I think
15:50:59 <vhari> felipe_rodrigues, will ask to clarify
15:51:09 <vhari> ack the logs are slim
15:51:32 <vhari> seems we need more data to proceed
15:52:00 <vhari> if on other thoughts .. on to last bug for today
15:52:08 <vhari> #link https://bugs.launchpad.net/manila/+bug/2012742
15:52:19 <vhari> have a few minutes for a brief triage
15:53:04 <carloss> felipe_rodrigues: netapp one :p
15:53:09 <carloss> and we have an assignee
15:53:32 <carloss> i believe this would be blocking someone
15:56:00 <felipe_rodrigues> yep.. the reporter assigned to himself
15:56:12 <felipe_rodrigues> good catch btw
15:57:33 <carloss> i'd say medium
15:57:47 <felipe_rodrigues> If the env reaches this scenario maybe all data motion cannot work
15:57:58 <felipe_rodrigues> Id say as medium too
15:59:08 <carloss> ack
15:59:13 <vhari> done, thanks all.. that's a wrap for bugs today .. :)
15:59:40 <carloss> awesome
15:59:42 <carloss> thanks vhari!
15:59:46 <carloss> thank you everyone!
15:59:54 <carloss> see you on #openstack-manila
15:59:57 <carloss> #endmeeting