15:02:39 #startmeeting manila 15:02:39 Meeting started Thu Feb 24 15:02:39 2022 UTC and is due to finish in 60 minutes. The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:39 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:02:39 The meeting name has been set to 'manila' 15:02:50 hello 15:02:54 o/ 15:03:06 hi everyone 15:03:15 o/ 15:03:33 o/ 15:03:33 hi 15:04:07 hi 15:04:15 o/ hi everyone 15:04:29 courtesy ping: ganso dviroel carloss tbarron felipe_rodrigues ecsantos 15:04:35 o/ 15:04:36 o/ 15:04:47 * gouthamr is it just me, or irccloud flaky today? 15:05:18 o/ 15:05:24 fo/ 15:05:33 #chair carloss 15:05:33 Current chairs: carloss gouthamr 15:05:53 carloss++ 15:05:53 ^ just in case net-splits, and i'm speaking to myself 15:06:02 :) 15:06:08 although it appears like i'm okay: https://meetings.opendev.org/meetings/manila/2022/manila.2022-02-24-15.02.log.txt 15:06:16 #topic Announcements 15:06:43 alright, we 15:06:50 are at feature freeze 15:06:54 o/ 15:06:56 #link https://releases.openstack.org/yoga/schedule.html 15:07:16 we hope to ship out a client by tomorrow 15:07:36 ^ python-manilaclient* only.. 15:07:43 o/ 15:08:10 hi 15:08:11 after tomorrow, no feature changes will be accepted into manila, or manila-ui until RC1 has been shipped 15:08:44 the target date for RC1 is Mar 11 15:09:37 that's the announcements i had, any one else got any? 15:10:37 #topic Zorilla cycle PTG Planning 15:10:52 ^ a reminder here to add your topic proposals to the planning etherpad 15:11:07 #link https://etherpad.opendev.org/p/zorilla-ptg-manila-planning (PTG Planning Etherpad) 15:12:06 #topic M-3 Bugsquash 15:12:20 more like RC1 bug squash :) 15:12:50 we're planning to have a bugsquash that begins next thursday 15:13:33 fabiooliveira, carloss and i have been chatting about it a bit, we'll share some more details over the openstack-discuss mailing list 15:15:08 as has been the case with the last several bugsquashes 15:15:28 we'll have this one run for a week and close out on March 10th 15:16:27 i hope you can all participate and review patches :) 15:17:13 i'll brainstorm with vhari to put up a list of bugs that need attention -- but, feel free to bring your own bug as always 15:18:15 any concerns with the timing, or the plan? 15:19:13 we'll switch to a bugsquash kick-off/bug triage meeting on meetpad next week at this time instead of having this IRC meeting 15:21:08 if there's no concerns, i hope you all are excited to close out on a bug or two next week :D 15:21:14 #topic M-3 feature reviews tracking 15:21:29 #link https://etherpad.opendev.org/p/manila-yoga-review-focus 15:21:56 lots of movement on this etherpad 15:22:40 and some comments for deferring some things to the Zorilla cycle 15:24:05 lets chat about 15:24:07 Admin only metadata keys/Metadata API 15:24:20 #link https://review.opendev.org/c/openstack/manila-tempest-plugin/+/826747 15:24:35 #link https://review.opendev.org/c/openstack/manila/+/824648 15:25:15 #link https://review.opendev.org/q/topic:bp%252Fmetadata-for-share-resources 15:25:34 ashrodri: what's the status of these? 15:27:01 o/ right so I had zuul passing for the shares refactoring til I started rebasing on the recent changes, but ive almost got that cleaned up 15:28:16 tempest trim is passing zuul and could use another coupler eviews 15:28:42 I think its a good idea to defer the featureful changes to Zorilla cycle, and keep the tempest trim and shares refactoring for this cycle, thoughts? 15:29:57 okay.. 15:30:16 aside from the behavior change that's warranting the removal of a metadata test: https://review.opendev.org/c/openstack/manila-tempest-plugin/+/826747, there are no feature changes in the shares patch 15:30:54 yep 15:31:22 in other words, https://review.opendev.org/c/openstack/manila/+/824648 is a refactor with no end-user impact (besides the invalid corner case that we've beaten to death) 15:31:29 i can live with that 15:32:37 haixin,felipe_rodrigues, carloss wdyt? 15:32:46 sounds good 15:32:55 * carloss added his vote to the tempest removal change :) 15:33:02 tempest test* 15:33:39 thanks carloss++ 15:34:22 yw :) 15:34:46 good too 15:35:43 great, thank you! lets move on.. 15:35:52 Add support to multiple subnets per AZ 15:36:06 #link https://review.opendev.org/q/topic:bp%252Fmultiple-share-network-subnets 15:36:33 merge conflicts and some review comments, how are these looking, felipe_rodrigues ecsantos[m] andrebeltrami[m] 15:37:11 From the core patch, there are some reviews thank you gouthamr, carloss and dviroel 15:38:05 I already addressed them and rebased.. Now, there some unit tests to be fixed, I'm working on it! A new patch will be sent soon 15:38:49 we also have reviews for both ontap and containers 15:39:32 we are working to have all comments addressed including unit tests by the end of the day 15:39:55 thanks a lot carloss and dviroel for taking some time to review our patches 15:39:57 :) 15:40:13 Thanks for the review on the Container side carloss! I'm already addressing your comments and should publish a new patchset today :) 15:40:25 from manila client, I already added the new check operation, and received some review from carloss thanks. I'm fixing the comments 15:40:25 from tempest, I implemented more tests and I already fixed the comments from dviroel. Thank you dviroel. Waiting the new ps from core to submit the tempest changes. 15:40:41 awesome thanks for the updates and the reviews 15:40:57 yw :) 15:41:06 ++ 15:41:42 taking a pause here and looking at the clock, the client patch here is the one that needs to go out on time, or get deferred 15:42:56 since these changes are all backwards compatible, there's no regression if the client doesn't include these new features... but, we've tried hard to get new features in alongside the server each release 15:44:01 a new functional test from manila client depends on the core patch, it's a problem? 15:44:48 I am addressing the comments from carloss and I'll update the ps today 15:44:50 at the same time, i don't want us to get burnt out and rush things in.. lets take our time with the reviews and take a call about how to handle this on #openstack-manila after this meeting 15:45:02 ++ 15:45:39 > a new functional test from manila client depends on the core patch, it's a problem? 15:45:39 an alternative to that would be to add the functional test after 15:45:52 i'd say it's not the ideal scenario 15:46:03 s/the functional test/this specific functional test 15:46:04 andrebeltrami[m]: in the worst case, we'll end up merging the core patches, and leave the client changes for zorilla -- they can merge next week, and we can request a new release 15:46:29 gouthamr++ 15:46:49 but, lets see how that pans out.. won't count it out if everything's looking good.. 15:47:07 as is the mantra at this time of the release: all hands on deck :) 15:47:25 I think the client can be merged until tomorrow.. We have tested with the core patch locally.. 15:47:27 that sounds reasonable. Would be nice to have it merged too and I believe all comments aren't really critical 15:47:50 great.. 15:47:57 lets discuss the last feature changes on the etherpad 15:48:16 #link https://review.opendev.org/q/topic:bp%252Fprivsep-migration (privsep migration) 15:49:46 both of these looking quite close 15:49:51 more eyes would be appreciated :D 15:50:00 yes, these look good to me; they're a good start to the migration which will hopefully be complete in the zorilla cycle 15:51:03 vkmc: would you be able to take a look? 15:51:15 gouthamr, sure thing 15:51:21 thanks 15:51:27 :) 15:51:39 alright, are we missing any other feature change? 15:53:12 #topic Bug Triage (vhari) 15:53:33 o/ vhari, do we want to triage any bugs in the time left? 15:53:40 gouthamr, lets take a look at #link https://bugs.launchpad.net/manila/+bug/1960239 15:53:51 #link https://bugs.launchpad.net/manila/+bug/1960239 15:55:35 looking to set importance and prio 15:56:11 that could be assigned to me 15:56:24 seems like there is a workaround 15:56:28 and it's more like a user experience thing 15:56:42 yeah, an ux improvement, it looks like this could go the way of deferred deletion too 15:56:45 so, importance medium? 15:58:09 looks like "low" to me, but annoying for sure; maybe something to address at the bugsquash! 15:58:30 Low +1 15:58:57 gouthamr, I will set it to a Med for now and park it for bugsquash 15:59:20 :) okay, np 15:59:20 with that .. that's all the time we have for bugs today :) 15:59:29 thanks 15:59:33 #topic Open Discussion 15:59:47 under 1 min for any snarky comments :) 16:00:13 and you've had your time 16:00:26 thanks for coding all the changes and for reviewing, everyone 16:00:34 see you on #openstack-manila 16:00:53 and at the bugsquash call next week 16:00:56 #endmeeting