| *** dviroel|out is now known as dviroel | 11:02 | |
| gouthamr | #startmeeting manila | 15:01 |
|---|---|---|
| opendevmeet | Meeting started Thu Jul 15 15:01:12 2021 UTC and is due to finish in 60 minutes. The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:01 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:01 |
| opendevmeet | The meeting name has been set to 'manila' | 15:01 |
| carloss | o/ | 15:01 |
| ashrodri | o/ | 15:01 |
| vhari | hi | 15:01 |
| tbarron | hi | 15:01 |
| dviroel | o/ | 15:02 |
| gouthamr | courtesy ping: ganso vkmc felipe_rodrigues ecsantos vhari | 15:02 |
| felipe_rodrigues | o/ | 15:02 |
| gouthamr | o/ hello folks | 15:02 |
| vkmc | o/ | 15:02 |
| vkmc | hi everyone | 15:02 |
| archanaserver | o/ | 15:02 |
| caiquemello | o/ | 15:02 |
| gouthamr | here's the agenda for today's meeting: https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting | 15:03 |
| gouthamr | let's begin with | 15:03 |
| gouthamr | #topic Announcements | 15:03 |
| gouthamr | it's milestone-2 today | 15:03 |
| gouthamr | #link https://releases.openstack.org/xena/schedule.html | 15:03 |
| gouthamr | #link https://launchpad.net/manila/+milestone/xena-2 | 15:04 |
| gouthamr | ^ if your name's against any of these bugs, and you're not working on them, please comment on the bug and move the target forward | 15:04 |
| gouthamr | our new driver submission deadline is in two weeks | 15:05 |
| gouthamr | and Feature Proposal Freeze is on Aug 6 | 15:05 |
| gouthamr | so we're slowly inching towards the tail end of the xena development cycle | 15:05 |
| gouthamr | i've signed us up for space and time at the upcoming virtual project team gathering event | 15:07 |
| gouthamr | #link https://ethercalc.openstack.org/8tum5yl1bx43 (Tentative Schedule for the Yoga PTG) | 15:07 |
| gouthamr | it's a tentative schedule, and we have the flexibility to move things around | 15:07 |
| gouthamr | lots of empty spaces on the ethercalc :) but this is FCFS | 15:08 |
| gouthamr | as has been the case in the past, we may move some action around to other team rooms | 15:09 |
| gouthamr | i'll send an email on the ML with some more details, and a planning etherpad to collect ideas/topics | 15:11 |
| gouthamr | a number of us are participating in the grace hopper celebration summer open source day today | 15:11 |
| gouthamr | its a day long event, you could see some code review action around eod | 15:12 |
| gouthamr | that's all the announcements i had, anyone else got any? | 15:12 |
| gouthamr | #topic Manila UI stable/queens to EOL? | 15:14 |
| gouthamr | so the horizon team's planning to EOL their stable/queens branches | 15:15 |
| gouthamr | #link https://review.opendev.org/c/openstack/releases/+/799543 (Horizon moving stable/queens to eol) | 15:15 |
| gouthamr | and they want to let us determine if manila-ui's stable/queens branch has to be EOL'ed at the same time | 15:15 |
| gouthamr | noticed this via code review, and thought i could stop some wasted effort.. | 15:16 |
| gouthamr | #link https://review.opendev.org/c/openstack/manila-ui/+/800544 (Patch to move horizon jobs to manila-ui, but is this necessary?) | 15:16 |
| gouthamr | there's really little benefit if horizon's moving to eol, and manila-ui continues to accept patches | 15:16 |
| gouthamr | queens is a 3.5 year old release | 15:17 |
| gouthamr | and i am motivated to pursue discussions to eol the stable/queens branches on manila repos itself | 15:18 |
| gouthamr | but, the immediate question is how we want to proceed with manila-ui | 15:18 |
| gouthamr | does anyone have any concerns with us asking the horizon team to eol the stable/queens branch of manila-ui as well? | 15:19 |
| gouthamr | ^ manila-ui is jointly maintained by the horizon team and us | 15:20 |
| gouthamr | and the last time we had a patch on the queens branch here was exactly one year ago: | 15:20 |
| gouthamr | #link https://review.opendev.org/q/project:openstack/manila-ui+branch:stable/queens (backports to stable/queens on manila-ui) | 15:21 |
| vkmc | ++ | 15:21 |
| vkmc | I think this should be a joint effort | 15:21 |
| vkmc | if they are eol, it doesn't make sense we keep maintaining that branch | 15:22 |
| vkmc | in manila-ui | 15:22 |
| carloss | I don't have any concerns :) | 15:22 |
| vkmc | perhaps one of us could follow this up with them | 15:22 |
| vkmc | gouthamr, do you want me to chase that? | 15:22 |
| gouthamr | vkmc: yep! vishalmanchanda was pursuing this, so we can let him know | 15:23 |
| vkmc | gouthamr, cool! | 15:24 |
| gouthamr | vkmc: if we don't want to do this in https://review.opendev.org/c/openstack/releases/+/799543 ; you can upload a similar patch to tag just manila-ui | 15:24 |
| gouthamr | and add me to review :) | 15:24 |
| vkmc | gouthamr, perfect | 15:24 |
| gouthamr | thanks vkmc++ | 15:25 |
| gouthamr | alright anything else regarding $topic? | 15:25 |
| haixin | what does eol mean? | 15:25 |
| vkmc | end of life | 15:25 |
| vkmc | :D | 15:25 |
| gouthamr | +1, the branch will be retired | 15:25 |
| haixin | i know,, | 15:26 |
| gouthamr | the phases are described here: | 15:26 |
| gouthamr | #link https://docs.openstack.org/project-team-guide/stable-branches.html (Stable Branches and Policies) | 15:26 |
| gouthamr | so at eol, we 1) create a git tag, 2) abandon all pending changes to the respective branch, 3) pursue the deletion of the branch | 15:27 |
| gouthamr | step 1) is done via the openstack/releases repository, like https://review.opendev.org/c/openstack/releases/+/799543 | 15:27 |
| gouthamr | step 2) for stable branches will need someone from the manila-stable-core, or stable-maint teams, or patch owners to manually abandon the pending gerrit changes | 15:28 |
| gouthamr | step 3) will require asking the friendly folks at #opendev-infra to clean up the branch | 15:29 |
| gouthamr | so the real impact here is if anyone was pulling code from that branch | 15:30 |
| gouthamr | since the branch will disappear from the sources (opendev.org, github.com), they'll need to stop relying on it | 15:30 |
| gouthamr | generally, distributions like RDO watch changes to older branches, and possibly have work to cleanup stuff on their end when we retire older stable branches | 15:31 |
| gouthamr | its a lot of sausage making being described here :P | 15:31 |
| gouthamr | on related thoughts, i'd like to propose similar retirement of the stable/queens branch on manila and python-manilaclient and signal the intent to retire stable/rocky and stable/stein as well | 15:33 |
| tbarron | +1 | 15:33 |
| gouthamr | we discussed this at the PTG and we seem to be in agreement, i'll collect some thoughts on the mailing list | 15:34 |
| gouthamr | any other comments/concerns about this? | 15:35 |
| ashrodri | ++ | 15:35 |
| gouthamr | good stuff, lets move to regular programming | 15:36 |
| gouthamr | #topic Reviews needing attention | 15:36 |
| gouthamr | #link https://etherpad.opendev.org/p/manila-xena-review-focus | 15:36 |
| gouthamr | we've some good reviews on the last spec to merge: https://review.opendev.org/c/openstack/manila-specs/+/775198 | 15:37 |
| gouthamr | carloss vkmc dviroel haixin, et al ^ can you please look as well | 15:37 |
| vkmc | gouthamr, sure thing | 15:37 |
| dviroel | yep | 15:38 |
| gouthamr | i reiterate, i treat spec reviews a bit differently than code - i usually wait for maximum reviews there, so we have a chance to work through the design collectively | 15:38 |
| haixin | ok | 15:39 |
| gouthamr | if you're new to this community, this is your cue :D you'll love specs - they lay out problems and solutions in a way that'll probably peak your interest as opposed to reading code | 15:39 |
| carloss | sure | 15:39 |
| gouthamr | thanks folks | 15:39 |
| gouthamr | simondodsley: we're chatting here, this is the weekly irc sync | 15:39 |
| gouthamr | so regarding the pure driver review, we're stuck with not being able to get the CI to pass of late | 15:40 |
| gouthamr | #link https://review.opendev.org/c/openstack/manila/+/789384 | 15:40 |
| gouthamr | #link http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023631.html | 15:40 |
| gouthamr | thanks for running tests and posting on the mailing list, carloss | 15:41 |
| carloss | my pleasure gouthamr | 15:41 |
| simondodsley | note that before the devstack changes to OVN we were getting the CI to pass | 15:41 |
| gouthamr | so if you're not aware, something is broken on devstack that we're unable to nail down that prevents vms within the devstack from accessing the world outside the devstack node | 15:42 |
| simondodsley | so the scenarios do work with this driver | 15:42 |
| gouthamr | so if you have bright ideas, do share them on the review | 15:42 |
| simondodsley | what I'd like, whilst this issue is resolved, to get an exception for the vendor CI pass and get the driver merged | 15:43 |
| dviroel | is mandatory to have scenarios tests passing as criteria to merge? | 15:44 |
| gouthamr | it's mandatory to run the scenario tests, yes - although this failure of infrastructure is bothersome | 15:44 |
| * dviroel doesn't mean that we shouldn't persue the issue, of course | 15:44 | |
| gouthamr | simondodsley: you've ofcourse tested the data paths, you've a vested interest in making sure this works | 15:45 |
| gouthamr | ^ any concerns with allowing this exception, while we pursue what broke with devstack? | 15:46 |
| simondodsley | yes - all the data paths have been tested and I will continue to work of a resolution as it will stop the CI passing any other reviews | 15:46 |
| gouthamr | tbarron dviroel carloss: you've signed up to review, what do you think? | 15:46 |
| carloss | I'm okay with the exception - simondodsley has been working for some time in the driver, was always responsive in the reviews I saw | 15:48 |
| dviroel | me too | 15:49 |
| gouthamr | awesome thank you, simondodsley - we'll do the exception | 15:50 |
| gouthamr | thanks for all your hard work resolving this issue | 15:50 |
| tbarron | ok by me | 15:50 |
| gouthamr | its now a common concern for most third party CIs, so we'll chase this down with the neutron/OVN folks | 15:51 |
| simondodsley | thanks team. appreciate it. | 15:51 |
| dviroel | simondodsley++ | 15:51 |
| carloss | simondodsley++ | 15:51 |
| gouthamr | great, any other reviews on https://etherpad.opendev.org/p/manila-xena-review-focus that need to be discussed here? | 15:51 |
| gouthamr | haixin tbarron: it is possible that https://review.opendev.org/c/openstack/manila/+/789702 exposes an underlying issue | 15:52 |
| tbarron | yes | 15:52 |
| tbarron | I think exposes rather than causes | 15:52 |
| gouthamr | i haven't looked at the loopingcall code (although at first glance the code paths look very similar) closely yet | 15:53 |
| tbarron | but am open to counter-argument | 15:53 |
| tbarron | I wonder if those tasks only take so long in a resource constrained devstack environment | 15:54 |
| tbarron | dunno | 15:54 |
| gouthamr | it's possible | 15:54 |
| gouthamr | there was a thread on the ML where this occurred in prod | 15:54 |
| gouthamr | #link http://lists.openstack.org/pipermail/openstack-discuss/2019-September/009534.html ([oslo] run outlasted interval) | 15:54 |
| gouthamr | i didn't see a resolution however | 15:54 |
| tbarron | good find | 15:55 |
| gouthamr | i don't see this in the tempest jobs in cinder where a similar approach is followed | 15:55 |
| gouthamr | another thing to check is if this occurs on all the CI jobs | 15:56 |
| tbarron | gouthamr: do you know if we see this consistently? | 15:56 |
| tbarron | jinx | 15:56 |
| gouthamr | i didn't look beyond one of the dummy driver jobs that i linked you folks to | 15:57 |
| * gouthamr looks at the clock | 15:57 | |
| tbarron | dummy driver job probably is running lots of concurrent stuff with no backend slowing stuff down | 15:57 |
| tbarron | maybe more contention but let's check other jobs | 15:58 |
| gouthamr | +1 | 15:58 |
| gouthamr | haixin: would like your thoughts as well; but lets chat directly on the change | 15:58 |
| gouthamr | vhari: sorry we're going to skip bug triage today | 15:59 |
| vhari | gouthamr, np .. no new bug this week :) | 15:59 |
| gouthamr | oh that's good news :) | 15:59 |
| gouthamr | alright, everyone - no time for Open Discussion as well. | 16:00 |
| gouthamr | if you'd like to chat about something, please hop on over to #openstack-manila | 16:00 |
| gouthamr | have fun at GHC/OSD if you're attending, and see you here next week! | 16:00 |
| gouthamr | thanks! | 16:00 |
| gouthamr | #endmeeting | 16:00 |
| opendevmeet | Meeting ended Thu Jul 15 16:00:51 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:00 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/manila/2021/manila.2021-07-15-15.01.html | 16:00 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/manila/2021/manila.2021-07-15-15.01.txt | 16:00 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/manila/2021/manila.2021-07-15-15.01.log.html | 16:00 |
| haixin | about run outlasted interval, i have no idea now, i will see it by my free time. | 16:00 |
| gouthamr | haixin: +1 | 16:01 |
| haixin | :) | 16:01 |
| *** dviroel is now known as dviroel|brb | 19:53 | |
| *** dviroel|brb is now known as dviroel | 20:27 | |
| *** dviroel is now known as dviroel|out | 21:24 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!