Thursday, 2023-04-06

*** chuanm0 is now known as chuanm00:16
*** chuanm1 is now known as chuanm00:24
*** chuanm1 is now known as chuanm01:59
*** chuanm9 is now known as chuanm02:35
*** chuanm1 is now known as chuanm04:48
*** chuanm8 is now known as chuanm05:10
*** chuanm4 is now known as chuanm05:27
*** geguileo is now known as Guest1015709:31
*** chuanm1 is now known as chuanm09:39
*** chuanm2 is now known as chuanm10:39
*** chuanm5 is now known as chuanm13:08
*** geguileo is now known as Guest1016813:10
carloss#startmeeting manila15:00
opendevmeetMeeting 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
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
opendevmeetThe meeting name has been set to 'manila'15:00
felipe_rodrigueshi15:00
lucasmoliveira059o/15:00
nahimsouza[m]o/15:00
caiquemello[m]hello!15:00
haixinO/15:00
vhario/15:01
thiagoalvoravelo/15:01
carlosscourtesy ping: vkmc dviroel gouthamr carthaca15:01
gouthamro/15:01
HelenaDantas[m]o/15:02
carlosshello everyone!15:03
carlossg'day!15:03
carlossgreat to see you here today15:03
carlosslet's get started with our shorter than usual agenda for today:15:04
* dviroel o/15:04
carloss#link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting15:04
* carloss waves at dviroel 15:04
carlossfirst topic of the day:15:04
carloss#topic Announcements15:04
carlossSchedule and Deadlines:15:05
carloss#link https://releases.openstack.org/bobcat/schedule.html15:05
carlosswe are in the third week of this release cycle15:06
carlossso things are a bit more calm now15:06
carlosswe're 5 weeks away from m-115:06
carlosson the next thing for announcements15:07
carlossI would like to thank you for the participation and feedback on the PTG15:07
carlossI am happy with the collaboration we had and the deep and meaningful discussions around the proposed topics15:08
carlossit resulted in a good list of AIs and things to keep in mind during this cycle15:08
carlossthe 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
carloss#link https://www.youtube.com/watch?v=gefbYrzRD04&list=PLnpzT0InFrqDW_djitgCiFzwhBFdvoRBC15:09
carlossand, for the PTG summary:15:09
carloss#link https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033202.html15:09
carlossI tried to capture the essence of the discussions and the AIs and add them to this summary15:09
carlossis there something you would like to add to this PTG topic? :)15:11
carlossmoving on...15:15
carlossI'll be on PTO for the next two weeks15:16
carlossgouthamr: has kindly offered to run the next week's weekly meeting15:16
carloss(thanks gouthamr)15:16
gouthamr++15:16
carlossbut 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:17
carlossApr 21st is a holiday in Brazil, and if folks are planning to extend the holiday, then it would be a massive drop in the audience15:19
carlossthe second option would be cancelling the Apr 20th weekly meeting15:19
gouthamri'd be okay skipping 15:20
gouthamrwe can keep an eye on the ML in case there's something that needs attention15:20
vharicarloss, I  am available to run the meeting on 20th  if we decide to keep it 15:21
haixini am ok for skip too. :)15:23
carlossnetappers + haixin: what's your take?15:24
carlosshaixin beat me to it :D15:24
haixinwhat holiday in Brazil?15:24
nahimsouza[m]i'll be working, but i'm ok for skipping too15:24
felipe_rodriguesskip+115:25
thiagoalvoravelI think it's ok skip15:26
caiquemello[m]skip+115:26
carlosshaixin: https://www.officeholidays.com/holidays/brazil/tiradentes-day15:26
carloss:D15:26
carlossthanks for offering to run the call vhari 15:27
carlossI think we can skip it in that day and keep an eye on the ML as suggested by gouthamr 15:27
carlossI'll send an email to the ML to announce that then15:28
haixinhappy holidy :D15:28
carlosshaixin: thank you! :D15:28
carlossthanks for your input folks15:28
carlossnext topic...15:28
carloss#topic Bug Triage15:28
carloss#link https://etherpad.opendev.org/p/manila-bug-triage-pad-new15:28
carlossvhari: floor is yours15:28
vharicarloss, ty15:29
vharilets dive it 15:29
vhari#link https://bugs.launchpad.net/manila/+bug/201532815:29
vharilooking for minor triage 15:30
carlosssounds like a low hanging fruit to implement in case we decide to proceed with it15:32
carlossa bit of a bug/rfe15:32
carlossI'd say low/medium prio and would ask if someone is willing to work on this LHF :D15:33
vhariack lhf for this one as well? 15:35
felipe_rodriguesI am not totally sure.. is It about block users from set active replica state ? 15:35
carlossI understood as not allow users to modify an active replica state15:37
felipe_rodriguesuhh.. I see.. seems LHF 15:38
carlossbut, 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 to15:38
felipe_rodriguesI was wondering it15:39
felipe_rodriguesis there any use case ?15:39
gouthamrfeels like we want a safety for the trigger to shoot ourselves in the foot15:39
gouthamrthe course of actions that happened seems dangerous15:40
gouthamrwe can prevent this, and provide a "force" flag? 15:41
carlossyep - that would be nice15:41
felipe_rodriguesyep15:41
carloss--force would be required only when it's the active replica15:41
carloss^ maybe design it like this15:42
carlossstill a lhf :D15:42
felipe_rodriguesmedium ? 15:42
carlossmedium++15:43
vhariack .. moving on to the next lhf :D15:43
vhari#link https://bugs.launchpad.net/manila/+bug/2015325  15:43
carlosslhf, low?15:44
felipe_rodrigueslow LHF +115:44
vhariagreed +115:44
vharianyone interested to look at this? 15:44
felipe_rodriguesI think NetApp can take this one15:45
vhari+1 anyone on in particular 15:45
felipe_rodriguesAdd me and I will find someone later15:46
vhariawesome felipe_rodrigues++15:46
carlossfelipe_rodrigues++15:46
vharinext #link https://bugs.launchpad.net/manila/+bug/201302615:46
felipe_rodriguesI could not find which the backend storage is used15:49
carloss++15:49
carlossmore logs would be needed I think15:50
vharifelipe_rodrigues, will ask to clarify 15:50
vhariack the logs are slim 15:51
vhariseems we need more data to proceed 15:51
vhariif on other thoughts .. on to last bug for today 15:52
vhari#link https://bugs.launchpad.net/manila/+bug/2012742  15:52
vharihave a few minutes for a brief triage 15:52
carlossfelipe_rodrigues: netapp one :p15:53
carlossand we have an assignee15:53
carlossi believe this would be blocking someone15:53
felipe_rodriguesyep.. the reporter assigned to himself 15:56
felipe_rodriguesgood catch btw15:56
carlossi'd say medium15:57
felipe_rodriguesIf the env reaches this scenario maybe all data motion cannot work15:57
felipe_rodriguesId say as medium too15:57
carlossack15:59
vharidone, thanks all.. that's a wrap for bugs today .. :)15:59
carlossawesome15:59
carlossthanks vhari!15:59
carlossthank you everyone!15:59
carlosssee you on #openstack-manila15:59
carloss#endmeeting15:59
opendevmeetMeeting ended Thu Apr  6 15:59:57 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
opendevmeetMinutes:        https://meetings.opendev.org/meetings/manila/2023/manila.2023-04-06-15.00.html15:59
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/manila/2023/manila.2023-04-06-15.00.txt15:59
opendevmeetLog:            https://meetings.opendev.org/meetings/manila/2023/manila.2023-04-06-15.00.log.html15:59
*** chuanm1 is now known as chuanm17:58

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