16:00:45 #startmeeting Octavia 16:00:46 p/ 16:00:46 Meeting started Wed Mar 25 16:00:45 2020 UTC and is due to finish in 60 minutes. The chair is rm_work. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:47 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:47 o/ 16:00:50 The meeting name has been set to 'octavia' 16:00:51 o/ 16:01:03 o/ 16:01:03 hi 16:01:05 hi 16:01:37 hi 16:05:35 rm_work, you there? 16:05:43 sorry, distracted 16:05:46 #chair johnsom 16:05:47 Current chairs: johnsom rm_work 16:05:51 #chair cgoncalves 16:05:52 Current chairs: cgoncalves johnsom rm_work 16:05:57 welcome everyone! 16:06:02 #topic Announcements 16:06:29 Feature freeze is right around the corner 16:06:45 #link https://releases.openstack.org/ussuri/schedule.html 16:07:05 We need to release octavia-lib next week 16:07:18 Feature freeze is the week after 16:08:31 I will take a first pass at our highlights today, but we probably have a bit before those need to be finalized. 16:09:02 "he deadline for cycle highlights is the end of the R-5 week [4] on April 10th." 16:09:33 #link http://lists.openstack.org/pipermail/openstack-discuss/2020-February/012873.html 16:10:05 I will also try to take a pass at the docs goal. Now that it is decided what the goal is... lol 16:10:37 The OpenStack Foundation User Committee has a new 2020 OpenStack User Survey: https://www.openstack.org/user-survey/survey-2020/landing 16:11:19 I have not taken it yet so I don't know if there are project-specific questions. I am not aware of the our team being asked to contribute with questions to the survey either 16:11:32 I didn't hear anything 16:12:42 I will also mention there is discussion starting on the goals for "V" 16:12:46 #link http://lists.openstack.org/pipermail/openstack-discuss/2020-March/013528.html 16:12:51 If you have input 16:17:21 #topic Brief progress reports / bugs needing review 16:17:43 rm_work Must have been called away, so I will move us on in the agenda 16:19:03 Mostly I have been working on cleaning up the tempest plugin and restructuring how we handle features that provider drivers don't support. 16:19:28 Other minor side items with image builds for ppc64, etc. 16:19:43 jobboard change required review, not so much time left.. 16:19:46 #link https://review.opendev.org/#/c/647406/ 16:20:01 I had a patch review day this last week as well, where I reviewed a bunch of patches. 16:20:42 yeah sorry, semi-around, this meeting time continues to be *the worst ever* :) 16:20:49 My plan is to hit those two housekeeping items (goal and highlights), continue work on the tempest plugin, polish failover, and review for jobboard ^^^. 16:21:00 ataraday_: i am pretty much good on that 16:21:09 rm_work, you had some questions if you around we can discuss this later 16:21:14 ataraday_: yes 16:21:20 sorry for disappearing the other day 16:21:39 these days whoever pings the most wins, constant distractions from all sides :( 16:22:06 i feel like a ping-pong ball 16:22:39 Yeah, I have been struggling with context switching recently myself. Lots going on 16:22:52 I proposed a tiny patch that should fix our amphora image build jobs 16:22:57 #link https://review.opendev.org/#/c/714680/ 16:24:14 I could not reproduce locally with different configurations (bionic, py2, py3, ansible 2.7/2.8, ...). it pains me I can't reproduce it but at least the job passed 16:24:57 cgoncalves Did it pass with the nightly job? I only see one case where it failed 16:25:01 the tempest scenario test for allowed CIDRs is ready for review. there was an issue with Neutron I addressed in latest patch set 16:25:05 #link https://review.opendev.org/#/c/702629/ 16:26:05 johnsom, patch set 5 was an attempted to just remove explicit install of python3-yaml. it failed, so I reverted 16:26:18 Ah, ok, PS3 is the pass 16:26:23 right 16:27:23 FWIW, pip installs PyYAML when installing DIB so... :/ 16:28:07 Yeah, that was very strange. It really should be a DIB requirement/bindep 16:28:13 IMO 16:28:46 it is in requirements.txt 16:29:15 Maybe it needs the py2/py3 conditional in requirements.txt for DIB? 16:30:42 could be. I did not check that 16:31:16 IIRC in my local env the latest version of PyYAML was being installed 16:32:38 Any other updates today? 16:33:00 ataraday_ Is that the last patch needed for the jobboard feature? 16:34:04 I still owe a port of the failover to the jobboard v2 path. I was just letting the v1 patch settle a bit and get some reviews. 16:36:03 johnsom, yes, I was going to test and review failover v1, hopefully do this on this week 16:37:37 Cool, thank you. 16:37:40 #topic Open Discussion 16:37:54 Moving forward on the agenda. Any other items to discuss this week? 16:44:31 I will take that as a no 16:44:41 Thanks folks, have a great week! 16:44:46 thank you 16:44:50 #endmeeting