16:01:05 #startmeeting Octavia 16:01:06 Meeting started Wed Mar 11 16:01:05 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:01:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:01:10 The meeting name has been set to 'octavia' 16:01:12 #chair johnsom 16:01:13 Current chairs: johnsom rm_work 16:01:17 #chair cgoncalves 16:01:18 Current chairs: cgoncalves johnsom rm_work 16:01:26 hi 16:01:29 Hi 16:01:41 hey, carlos can you run this? both johnsom and I are in meetings internally that are running over 16:02:02 Hi 16:02:16 I am on a call too :/ 16:02:39 Daylight time is fun! 16:02:52 #topic Announcements 16:03:12 hi 16:03:19 I have not prepared anything, sorry. is there anything relevant to share? 16:04:12 The last release of octavia-lib date is coming up quickly 16:04:36 Week of March 30 16:05:23 thanks 16:05:25 Any other announcements this week? 16:06:02 #topic Brief progress reports / bugs needing review 16:06:19 #link https://releases.openstack.org/ussuri/schedule.html 16:07:31 Hightlight for #link https://review.opendev.org/#/c/709696/ 16:07:31 Oye, Ummmm, I'm down to just the network driver testing work. I have had some internal distractions that have slowed this down. 16:07:56 I also needed to address a few other small bugs, you probably saw the patches for. 16:08:21 Plan is to wrap failover as soon as possible and start the v2 driver work on it. 16:08:56 And wanted to raise attention for this bug #link https://storyboard.openstack.org/#!/story/2007340 - please share you thoughts. 16:09:48 I saw it, but have not had time to read/understand it. 16:10:00 I have been busy internally and with tripleo. I did some work in the octavia tempest plugin side to add coverage for the allowed CIDRs. sadly the jobs fail occasionally, it is a shortcoming in Neutron where the SG rule doesn't get configured in the agent faster than Octavia completes its flow, returns and tempest sends checks if the allowed CIDR is applied in the listener. 16:12:26 ataraday_ Are you keeping the priority review list up to date for the jobboard chain? I think in the next we or so we really need to prioritize getting the last base patches reviewed and merged. IMO, this is a *must* feature for U. 16:13:47 johnsom, yes, things are on track there. Just two changes left - one small I pointed earlier 16:13:53 and the main change 16:14:07 Ok, thank you 16:15:29 Any other updates this week? 16:16:30 #topic Open Discussion 16:16:50 One item I wanted to mention today, the upstream periodic image building jobs are not working 16:16:57 They stopped early last month. 16:17:21 It appears the python "yaml" package issue is going on there. 16:17:41 If anyone has some time, it would be great if you could track that down. 16:17:54 Maybe work with those DIB cores.... grin 16:17:59 http://zuul.openstack.org/builds?project=openstack%2Foctavia&pipeline=periodic-stable&pipeline=periodic 16:18:29 * cgoncalves wears the Octavia hat at all times 16:18:49 I think I had some patches up for new image building jobs, but it's been such chaos recently I'm not 100% sure if those are related or not 16:18:54 I will check what is going on there 16:19:22 weird ok, we have not had issues with this internally and we build centos images from master :/ 16:19:29 have not seen any build failures 16:19:29 Ah, mine is just a "test" not a publish, so different issues 16:20:00 I *think* this may just be that DIB has not released a fixed package for this issue yet, but not sure 16:20:34 #link https://review.opendev.org/#/c/706393/ 16:20:41 That is the "test" job patch 16:20:45 ianw released DIB 2.43.0 today (?) 16:21:21 Ah, yes, maybe that will fix it???? 16:21:43 I can check 16:22:25 Thank you 16:22:30 Any other topics today? 16:22:54 thanks for monitoring the periodic jobs! 16:24:04 Ok, if there are not any more topics we can close it out. 16:24:43 Maybe our PTL rm_work can scrub the priority list and bring a proposed list of features that are at risk of not making Ussuri next week. 16:25:02 We are pretty much up to the feature in/out time. 16:25:02 that would be awesome if i could do that 16:25:24 yes, so I have time in my sprint this week/next for actually working on the multi-vip stuff 16:25:37 but I am worried that may not make it into U even though the lib change did 16:25:41 which is fine 16:25:59 I think our real bottleneck is legitimately review cycles 16:26:10 and even if the work can get done, there's no cycles to get people to review it 16:26:27 for instance, STILL waiting on reviews for outstanding AZ code bugs that are making AZ support unusable 16:26:41 (thanks carlos for the +2 on the first one) 16:27:48 so I will try to take some time to scrub that and make some decisions about what we will most likely have to delay till next cycle, and what we need to focus on for this cycle 16:27:55 Ok, any thing else today or onward? 16:29:00 Ok, thanks everyone! 16:29:04 o/ 16:29:06 #endmeeting