15:00:58 #startmeeting manila 15:00:59 Meeting started Thu Jul 23 15:00:58 2020 UTC and is due to finish in 60 minutes. The chair is gouthamr. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:01:02 The meeting name has been set to 'manila' 15:01:08 o/ hey 15:01:10 yo 15:01:11 o/ 15:01:12 hi 15:01:14 o/ 15:01:15 o/ 15:01:21 amito++ 15:01:31 o/ 15:01:42 that's a variable for his year-count 15:01:50 o/ 15:02:06 courtesy ping: ganso lseki 15:02:10 :) 15:02:15 o/ hello everyone! 15:02:31 hope you celebrated well, amito 15:02:40 o/ 15:02:50 here's the agenda for our meeting today: 15:02:51 https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting 15:02:53 gouthamr: yes, indeed we have :) 15:02:56 amito, happy belated birthday :D 15:03:02 vkmc: thanks! :D 15:03:22 🎉 15:03:38 great, lets begin with 15:03:41 #topic Announcements 15:04:02 We had some new releases in the past week that i'd like to call your attention to 15:04:13 #link http://lists.openstack.org/pipermail/release-announce/2020-July/009554.html (manila 8.1.3 | stable/stein) 15:04:23 #link http://lists.openstack.org/pipermail/release-announce/2020-July/009577.html (manila-tempest-plugin 1.1.0 | victoria) 15:05:01 if you're testing manila with tagged versions of the manila-tempest-plugin, this one is our best one yet 15:05:20 \o/ 15:05:22 it fixes numerous historic issues we've lugged around 15:05:40 many thanks to everyone that worked hard for several weeks to get this out the door 15:06:31 we're in week 12 weeks away from the Victoria release 15:06:55 * gouthamr changes thoughts midway often 15:07:21 milestone-2 is next week 15:07:33 that is also our new driver deadline 15:07:40 #link https://releases.openstack.org/victoria/schedule.html (victoria release schedule) 15:08:15 i haven't seen any submissions so far, but there have been a couple of queries 15:09:02 there are also a number of bugs that are targeted for next week: 15:09:10 #link https://launchpad.net/manila/+milestone/victoria-2 (m-2 bugs) 15:09:58 please take a look, and either polish up your patches, or retarget the bugs you're working on in case you need longer 15:10:51 that's all i had in terms of announcements 15:10:59 * gouthamr looks around the room 15:11:12 .. 15:11:25 Short announcement from my side - 15:11:56 * gouthamr grips coffee 15:12:15 I recently moved on from Infinidat, and it's been a while even when I was there since I did any work on the Infinidat Cinder / Manila drivers. I hope I'll get some time in the future to get back to OpenStack, but for now - I'll have to drop my core status. 15:12:58 It's been great working with and meeting all of you, and I'll try to attend the meetings as much as possible and keep in touch :) 15:13:09 amito: I'm very sorry you won't be working on OpenStack but hope your new work will be great. 15:13:16 amito: congratulations on your move! 15:13:28 Thanks @tbarron, @gouthamr :) 15:13:50 amito: I'll especially remember being snowed in at PTG in Dublin. 15:14:12 @tbarron Yes, it's indeed a PTG to remember ^^ 15:14:39 +1, we're sad, but thank you so much for your work on Manila. we'll miss you around here 15:14:45 :( 15:15:02 congrats amito! 15:15:18 you will be missed for sure 15:15:29 Thank you @vkmc! :) @gouthamr I'll miss you guys as well, and I hope we'll get a chance to work together again in the future. I'll do my best to keep in touch :) 15:15:30 amito: congrats and thanks for everything! hope to see your around in irc channels 15:15:34 amito, best of luck on your new work .. do stay in touch 15:15:45 Thanks @vhari. 15:15:55 Thanks @dviroel! 15:16:04 * gouthamr this guy surely uses Slack now at his new workplace 15:16:22 lol indeed we do 15:16:23 lol 15:16:35 I was remembering the snow people building we did in Dublin with ganso... thinking on which was the best OpenStack event we was (question the OpenStack Foundation folks did on social media) 15:16:38 :D 15:16:39 Yep I got confused with the @'s 15:16:51 lol 15:16:54 Snowpenstack 15:16:54 thanks for your work in manila amito! wish you luck in your new job :) 15:17:27 carloss: thanks :) best of luck! 15:18:27 good stuff, ty for sharing the news too, amito 15:18:31 anyone else have anything? 15:19:13 better not, we can't handle any more happy news today 15:19:33 #topic Stable branch status 15:19:35 :) 15:20:15 alright we've had a much degraded gate on our stable branches for a while now 15:20:42 so a couple of weeks ago, we discussed closing stable/ocata and stable/pike 15:20:43 #link http://lists.openstack.org/pipermail/openstack-discuss/2020-July/015869.html 15:21:22 since i've had the stable maintenance core take a look at stable/pike and tell me what's wrong 15:21:37 but, honestly, with all the things that are going on - i haven't had the chance to take a look 15:22:31 and as you're aware, the biggest lesson in open source PTL'ing is learning to say no 15:22:57 ^ could apply to all of you, as maintainers too 15:23:08 +1 15:23:18 here's a sheet that dviroel put together to track CI status for third party CIs 15:23:27 #link https://docs.google.com/spreadsheets/d/1mgjqpHB97HAzwvTmiMeLksSbOrtvdd_fsbs3vHK2l5c/edit#gid=332683504 (Manila CI tracker) 15:23:59 There's a sheet there to show you the CI status for Extended Maintenance 15:24:54 i'll follow up to the ML post and propose EOL patches to ocata and pike 15:25:00 +1 15:25:10 but, we're not doing that great on queens and rocky either 15:25:51 we have a centos-7 voting job in each of these branches, and there are very few devstack jobs that run on centos-7 on older branches 15:26:23 our centos-7 stable/queens job can benefit from this fix in devstack: https://review.opendev.org/#/c/736189/ 15:27:36 hmm, have we tested stable/queens depending on that patch? 15:27:59 tbarron: yes 15:28:23 gouthamr: awesome, is it sufficient or just necessary? 15:28:27 tbarron: https://review.opendev.org/#/c/728472/ 15:29:04 sufficient for lvm job! 15:29:05 tbarron: it's necessary, the uwsgi fix that got backported to stable/queens works well on ubuntu, not on centos 15:30:24 isn't the same issue that we have for centos-7 in stable/rocky? 15:30:53 dviroel: we do have that issue, so i cherry-picked that fix to just check: https://review.opendev.org/#/q/I57e6219d675c951880808ced4e26c2344ef15cee 15:30:59 sry, https://review.opendev.org/#/c/689635/ 15:31:32 this is the cherry-pick: https://review.opendev.org/#/c/741030/ 15:32:27 https://zuul.opendev.org/t/openstack/build/e31a3d8c16ec45a995a7f73d844c6f19/log/logs/devstacklog.txt#7810 <--- the error 15:33:19 i didn't spend time checking for the fix, and its possible we're not constraining our reqs somehow 15:34:46 but, i could use some help getting these jobs back into shape 15:35:16 The only reason we were using CentOS for lvm was an ubuntu IPv6 handling bug. I wonder if it has been fixed in Xenial. 15:35:17 so, if you have some cycles, let me know, and we can brainstorm 15:36:41 tbarron: true, last i checked was a year ago, and the fix in question wasn't backported 15:37:24 gouthamr: i'll do some checking just in case 15:38:20 ty tbarron 15:38:44 tbarron: i'll find the missing patch, and we might have to resort to a workaround 15:39:12 1) We could port the job to Xenial if there's support for ipv6 (iirc the bug was in exportfs) 15:39:40 2) We could stop running ipv6 and port the job to xenial - this would be trivial, but we'd lose coverage 15:40:46 3) Make the job non-voting for now, and figure out if we can fix it - there are other integration test jobs that do work to test regressions, except we run the risk of regression in the LVM driver, and in the ipv6 access-rules/exports code path 15:42:00 I think #3 isn't bad because if we backport changes in that code path we could figure out a way to test them 15:42:59 The chance that we have address-family specific changes in that code path to backport is not that big either. 15:43:05 * tbarron tempts fate 15:43:21 a combination of 2 and 3 could work too - in case we have bugfixes to the LVM driver (there are some backports pending right now) 15:43:36 3) looks good, we can backport other important fixes to those branches and hold lvm related fixes 15:44:18 agree with #2 + #3 so we can test changes to lvm that don't impact that path 15:44:34 rather, that path and that address family 15:44:40 okay, anyone has any objections? 15:45:15 no objections from my side :) 15:46:06 okay, we'll work on 3) and 2) discuss on #openstack-manila 15:46:22 * gouthamr oh boy, we're just on our second topic 15:46:38 any other concerns about stable branches 15:46:45 * gouthamr besides the 99 that we currently have? 15:47:14 moving on.. 15:47:15 #topic Zuulv3 status 15:47:52 as you all know this is one of the two goals that the wider openstack community has chosen to work on for the victoria cycle 15:47:56 #link https://tree.taiga.io/project/gouthampacha-manila-ci-zuul-v3-migration/kanban (Zuulv3 status tracker) 15:48:15 gouthamr: thanks for your great work on this and thanks to tosky for his great advice 15:48:39 ++ 15:48:55 we've ported all the tempest jobs so far 15:48:59 a lot of work, thanks for that, and an overdue refactor/cleanup 15:49:09 gouthamr++ 15:49:25 gouthamr ++ 15:49:34 lets begin with the easy ones: python-manilaclient, manila-ui and manila-image-elements should have no more legacy jobs 15:49:44 thanks for ack'ing the backports 15:50:10 there are legacy jobs in the EM branches - but, we'll get to those in our copious free time at the end of the release /jk 15:50:41 #link https://review.opendev.org/#/q/project:openstack/manila-tempest-plugin+topic:native-zuulv3-migration (porting tempest jobs) 15:51:12 i could use some code reviews to merge the last integration (tempest) job that's pending 15:51:27 #link https://review.opendev.org/#/c/740534/ (Add Zuulv3 native jobs for the dummy driver) 15:52:14 that's all for manila-tempest-plugin 15:52:21 moving on to the manila repo 15:52:29 we begin with the grenade job: 15:52:39 #link https://review.opendev.org/#/c/741727/ (Zuulv3 native grenade job) 15:53:10 there's a late W-1 from me, because gmann reminded me that we need to test the accessibility of the resources in the middle of the upgrade process 15:53:25 #link https://review.opendev.org/#/c/740509/ ([manila] assert:supports-accessible-upgrade) 15:53:35 * gouthamr slides in our tc request there 15:54:13 i began working on that yesteday, and i should have an update very soon 15:54:57 but, just fyi - we'll use a real backend for our grenade job, and seeing as we have so many at our disposal, we might actually make two grenade jobs eventually - one for DHSS=True (future) and one for DHSS=False (now) 15:55:45 so once that's done, we'll need be able to get rid of grenade and tempest legacy jobs 15:55:52 in a patch that somewhat looks like this: 15:55:54 (... but just one is needed now for the porting goal and the TC tag) 15:56:01 #link https://review.opendev.org/#/c/671868/ ([victoria][goal] Native Zuulv3 CI jobs) 15:56:05 tosky: +1 15:56:48 we'll still have a couple of legacy style jobs after all of this - and those pertain to our experiments in the past to get manila-image-elements builds tested 15:57:25 but those have remained experiments, since we haven't gotten them working in my memory 15:57:33 agree 15:58:22 okay, that's the status update on this 15:59:20 any questions/concerns? 15:59:47 with that, time check 16:00:14 i apologize for mismanaging time and taking up the whole hour, but, i appreciate the productive conversation! 16:00:27 we'll take the remaining issues to next week 16:00:39 thank you all for attending, and participating... 16:00:43 stay safe! 16:01:00 #endmeeting