Thursday, 2023-02-16

*** dasm|off is now known as dasm14:00
carloss#startmeeting manila15:00
opendevmeetMeeting started Thu Feb 16 15:00:35 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
carthacahi15:00
vhario/15:00
thiagoalvoravelo/15:01
gouthamro/15:01
caiquemello[m]0/15:01
nahimsouza[m]o/15:01
felipe_rodrigueshi15:02
MatheusAndrade[m]o/15:02
haixino/15:03
carlosstoday's meeting agenda:15:03
carloss#link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting15:03
carlosscourtesy ping: dviroel15:04
HelenaDantas[m]o/15:04
dviroelo/15:04
ashrodrio/15:05
carlosso/ hello everyone! great quorum15:05
luizsantos[m]o/15:05
carlosslet's get started with our meeting agenda for today :)15:05
carlossthe agenda is short. I want to focus on reviews for today.15:06
carloss#topic Announcements15:06
carlossSchedule and deadlines:15:06
carloss#link https://releases.openstack.org/antelope/schedule.html15:06
carlossthis is feature freeze week!15:06
carlossand also client release week. we need to ship our client tomorrow tops.15:07
carlossone extra announcement:15:09
carlossthe schedule for the OpenInfra summit in vancouver is live!15:09
carloss#link https://vancouver2023.openinfra.dev/a/schedule?_ga=2.76639381.1243381063.1676560116-1124383034.167102581415:09
carlosswe had one manila talk accepted as a lightning talk!15:09
carlossand a lot of interesting things there :)15:10
carlossplease check it out!15:10
carlossthat's all I had for announcements. Do you have something else you'd like to share with us today?15:10
carlosstaking silence as no :)15:12
carloss#topic Review Focus15:13
carlossso for today I want to do a check on a couple of changes:15:13
gouthamro/ just remembered something :)15:14
carlosssure gouthamr15:15
carlossplease go ahead15:15
gouthamrsorry for the interrupt15:15
carlossno worreis15:15
gouthamrbut congratulations and thank you for becoming our PTL through the Bobcat release15:15
dviroelcarloss++15:16
ashrodricarloss++15:16
caiquemello[m]carloss ++15:16
gouthamrit’s a hard job herding cats and churning oceans - but we love that you are doing this for us :)15:16
carlosshaha, thanks guys! really appreciated. I really think I have learned a lot in the role and that there is still motivation to continue. I love being a part of this community (many of you know I really do :)), so that makes the task more pleasant15:19
gouthamr++15:19
carlossand you have a huge part on this! so I'm happy to continue15:20
carlossand if you feel like being PTL some day, I am pretty sure we are open for a change of leadership, as they are very healthy!15:21
carlossI'd be happy to help you to get there!15:21
vharicarloss++15:21
carlossthanks!15:21
carlossmoving on...15:21
carloss#link https://etherpad.opendev.org/p/manila-antelope-review-focus (review focus etherpad)15:22
carlossso for today I want to do a check on a couple of changes:15:22
carloss#link https://review.opendev.org/c/openstack/manila/+/843832 (Share transfer between projects)15:24
carlossgouthamr and I have been reviewing this change lately and haixin has been solving comments in a blink of an eye15:24
carlossthere are a couple of things we discovered on the reviews though: an issue when we have multiple share replicas and re-applying access rules to them15:24
carlossafter some discussion, the three of us agreed on: blocking share transfers for replicated shares and redesign this on the upcoming PTG15:25
carlossI see some changes haixin made to the code, but I think we could fail earlier in the API and I have detailed it here:15:25
carloss#link https://review.opendev.org/c/openstack/manila/+/843832/comments/78f1849d_e067739a15:25
carlossbut after discussing it with haixin a few minutes ago, we realized that only item 1 would fit, as we don't allow people creating replicas from shares that are not available, and the transfer leaves the share in a different status15:26
haixini am working on it15:26
carlossI really think we can get this merged for this release. We are getting there, and if we need a feature freeze exception, I feel we can do it!15:27
gouthamr+115:28
carlossI am not very confident that the client will make it because we need to have the core merged +  merge the client today15:28
haixinWe also don't need to worry about the replicas quota when accept transfer.15:28
carlossah, true - as we won't allow replicated shares to be transferred for now, it makes sense15:29
carlossso in the worst case scenario we merge the client next release, which happened a couple of times in the past15:29
haixinthat is ok for me if have to merge next release.15:30
carlossawesome! thanks haixin 15:30
carlossmany thanks to the reviewers too!15:30
ashrodrihaixin++ thanks for all your hard work on this!15:31
carlosshaixin++ :)15:31
carlossnext on the list:15:32
carloss#link https://review.opendev.org/c/openstack/manila/+/869707/ (Metadata share network subnet)15:32
carloss#link https://review.opendev.org/c/openstack/manila/+/869708/ (NetApp Driver modification)15:32
carloss#link https://review.opendev.org/c/openstack/python-manilaclient/+/869709 (Client)15:32
carlossthis has received a couple of reviews15:32
carlossCI is not playing nice on the core change. felipe_rodrigues: this is open to a feature freeze exception, even though I think there's a chance we won't need it if reviewers are okay in the next pass15:33
felipe_rodriguesThanks everyone for the reviews15:33
carlossthe client change though: comments are there for some time. I *must* update the client release patch by EOD for me tops, so I can get at least one day for the release to happen. I believe there's a chance this will not make it in this client release too, so we will need to merge the client in the next release15:34
felipe_rodriguesI'm fine to merge the client in next release.. I can talk to customer about applying the patch .. it's much easier than server code15:35
carlossack felipe_rodrigues 15:35
carlossI would also like to ask: what are your plans on adding tests to this change, felipe_rodrigues? Asking because we don't have any functional tests coverage yet15:35
felipe_rodriguesGood point.. we can work on some functional tests as we did with snapshot metadata later15:36
carlossyep - snapshot metadata had the tests proposed with the change but took some time to get in. We have tested most scenarios manually. We can try to have some sort of focus on testing this before RC1 so we ensure we are not shipping any bugs15:37
carlossif issues are encountered, we can file bugs and propose as bugfixes15:38
carlosss/ We have tested most scenarios manually/ We have tested most scenarios manually for subnet metadata though15:38
felipe_rodriguesperfect!15:38
carlossthanks15:39
felipe_rodriguesyw15:39
carloss#link https://review.opendev.org/q/topic:bug%252F2000171 (Add quiesce_wait_time option to share replica promote API)15:39
carlosscore change has landed15:39
carlosskpdev was quick on solving comments too :)15:39
carlossI believe the client is close and is a candidate for this release15:39
carlossto the reviewers: could you please circle back on this change and provide some feedback today?15:40
carlossalso:15:41
carloss#link https://review.opendev.org/q/topic:bug%252F1988146 (Add default datasite to security service)15:41
carlossjust saw the workflow on the core - thanks gouthamr 15:41
carlossso we will have the client and the NetApp change for now15:41
carlossI think we are fine in terms of FFE15:42
carlossand last change from kpdev:15:42
carloss#link https://review.opendev.org/c/openstack/manila/+/859301 (Add 'state' column in 'services' table)15:42
felipe_rodriguesAbout quiesce_wait_time, I think we agreed functional tests to be added later..15:43
carlossfelipe_rodrigues: yes15:43
carlossgood point - I'll ping kpdev on that later too15:44
felipe_rodriguesnice15:45
carlosscontinuing on the state column to the services table: even though the above it does not change the API, it does a db bump. Thanks for the reviews gouthamr - I am taking this as a temptative, but unsure if we would pursue a feature freeze exception15:45
gouthamrthink we can; there's a little bit of an API impact -- i.e., introduction of a new "stopped" state15:45
gouthamrbut, no change to the request/response schema or hence the clients15:46
carlosssure15:49
carlossokay - let's continue to give it a try15:49
carloss#link https://review.opendev.org/q/topic:bp/netapp-ontap-rest-api-client+status:open (NetApp ONTAP - REST API transition)15:49
carlossNow the biggest changes of this cycle. We had a collab review earlier this week and here's a link to the recordings:15:50
carloss#link https://www.youtube.com/watch?v=zCOm_g7HGWU (NetApp ZAPI -> Rest Collab Review)15:50
carlossThe Structure change has merged but there are still 3 *major* changes under review. I am sure this will need a feature freeze exception.15:51
carlossfor the features we are pursuing an FFE: I would like to target them to next Thursday tops15:53
carlossall of the changes we mentioned are features that qualify for feature freeze/client freeze.15:55
carlosswe have a couple of bug fixes that can land after the freeze15:56
carlossis there something else you would like to bring up?15:56
felipe_rodriguesDo I need to send an email requesting the FFE for REST transition feature ? 15:57
carlossusually we would ask everyone to send the emails, but I can just send the emails wrt the changes that are yet to merge and qualify for the exception15:58
carlossso: let's do our best to get the changes that are close to get merged today/tomorrow15:58
felipe_rodriguesthank you carloss15:58
carlossand I can send the email for the request, as I did last cycle15:58
felipe_rodriguesnice15:58
carlossnp felipe_rodrigues 15:59
carlossokay, we are at the top of the hour16:00
carlosssorry for not leaving time for bug triaging vhari :(16:00
carlosswe can compensate next week :)16:00
carlossthank you everyone for joining today and for helping with reviews16:00
carlosslet's continue chatting on the changes and on #openstack-manila!16:00
carloss#endmeeting16:01
opendevmeetMeeting ended Thu Feb 16 16:01:00 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
opendevmeetMinutes:        https://meetings.opendev.org/meetings/manila/2023/manila.2023-02-16-15.00.html16:01
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/manila/2023/manila.2023-02-16-15.00.txt16:01
opendevmeetLog:            https://meetings.opendev.org/meetings/manila/2023/manila.2023-02-16-15.00.log.html16:01
*** dasm is now known as Guest504616:46
*** dasm is now known as Guest505218:10
*** dasm_ is now known as dasm|off23:55

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