16:03:48 #startmeeting Octavia 16:03:49 Meeting started Wed Aug 7 16:03:48 2019 UTC and is due to finish in 60 minutes. The chair is johnsom. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:03:50 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:03:52 The meeting name has been set to 'octavia' 16:04:05 hi 16:04:17 I am not exactly sure what is going on, but I will start the meeting 16:04:26 Hi everyone 16:04:41 Hi 16:04:44 \o 16:04:53 Hi 16:05:04 hi 16:05:09 Our PTL was just commenting, but then disappeared 16:05:16 ah 16:05:22 gottem! 16:05:27 yeah whoops missed the time :D 16:05:41 was reviewing the patch you just updated about the log socket lol 16:06:01 go ahead, you're doing good :) 16:06:20 eiddccidnvgenbjjunkgnkburcikcijfetrlvreflbc 16:06:22 Ha, well, I don't have an agenda, do you? 16:06:33 ^^ my yubikey wants you to know the meeting is going well 16:06:34 lol, yubikey? 16:07:03 #topic Announcements 16:07:11 Anybody have anything this week? 16:08:00 The Shanghai summit schedule is posted 16:08:51 Ok, moving on then 16:08:52 #topic Brief progress reports / bugs needing review 16:09:57 I have been busy working on octavia-lib provider related things recently. That main work is done, but I have some patch cleanup to do still. 16:10:02 lots of merging going on! woo! 16:10:19 great turnaround from a week ago when i was saying i was super concerned about review velocity 16:10:24 I am going to start work on a better failover flow. 16:11:02 Yes, it looks like we have burned through 60+ patches since I setup the review list. That is awesome 16:11:06 wow 16:11:52 I posted some comments on https://review.opendev.org/#/c/662791/ about issues with retry tasks - usage of redis jobboard, will try to find something else, for now concluding refactor of db object - dicts... 16:11:55 Anqi Li proposed openstack/octavia master: Implements notifications for octavia https://review.opendev.org/674432 16:12:56 johnsom, I will need to get your change https://review.opendev.org/#/c/660236/ updated, do you mind if I rebase it? 16:13:25 ataraday_ Please do, I keep forgetting to look at that. It's going to be a hard one to do. 16:13:48 johnsom, OK, thanks! 16:14:32 Ah, the data too long for column. I might have some ideas on how to fix that. 16:16:42 Any other updates? 16:17:54 #topic Open Discussion 16:18:00 Other topics this week? 16:18:23 johnsom, if you have time, may be you left some comments on change? My only idea to try notify taskflow listener that task is in progress, though not sure it is possible... 16:20:07 Ok 16:20:35 i realize the original authors of the active-active L3 spec are not present to answer this but wanted to ask anyway because i was curious; when looking at the changes https://review.opendev.org/#/c/453005/15 i don't see any mention of VRRP being used and was curious if anybody knew why not? it appears in haproxy's active-active guidelines is why i was wondering 16:21:51 VRRP for the top of rack switches or for the amphora? 16:22:22 for the amphora 16:22:24 cd 16:22:35 Opps, wrong window. lol 16:22:39 trying to go home so soon :)? 16:23:21 Well, in active-active the amphora are all equal, they don't need to pass a VIP between amphora, the L3 layer is holding the VIP 16:23:46 i think this might be a mistake on my part, i think the VRRP refers just to their Aloha virtual appliance that i'm actually unfamiliar with 16:23:53 In the non-L3 ToR active/active, the distributor component will use VRRP to pass the VIP around 16:23:53 so maybe disregard heh, quesiton might be half-baked 16:24:11 ok 16:26:11 Ok, anything else? 16:26:44 ataraday_ That DataError, was that when you were using Redis for persistence? 16:29:31 Must have lost her. 16:29:35 Any other topics today? 16:30:38 Ok, thanks everyone 16:30:39 #endmeeting