16:00:08 <johnsom> #startmeeting Octavia
16:00:09 <openstack> Meeting started Wed Aug 28 16:00:08 2019 UTC and is due to finish in 60 minutes.  The chair is johnsom. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:10 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:12 <openstack> The meeting name has been set to 'octavia'
16:00:16 <johnsom> Hi folks
16:00:52 <colin-> howdy
16:01:10 <johnsom> It might be a quiet week as I know a few people are out today.
16:01:30 <rm_work> ah hey, so my appointment was not the time i thought lol
16:01:49 <rm_work> so i'm here :D
16:01:53 <gthiemonge> Hi
16:01:56 <johnsom> Ah, cool. Well, I put an agenda together. Do you want to run the meeting or should I continue
16:01:57 <johnsom> ?
16:02:14 <rm_work> nah, go ahead ;)
16:02:17 * johnsom knows the answer but will ask anyway
16:02:21 <rm_work> ^_^
16:02:35 <johnsom> #topic Announcements
16:02:45 <ataraday_> hi
16:03:05 <johnsom> Starting off, it saddens me to say, but Nir has stepped down as an Octavia core.
16:03:11 <johnsom> #link http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008785.html
16:03:42 <johnsom> He has been working on neutron-lbaas and octavia for some time, so it's sad that he is leaving the project.
16:03:54 <rm_work> indeed :(
16:04:18 <johnsom> He is changing jobs, so needed to make the change.
16:04:37 <johnsom> Also, TC and PTL nominations for the "U" cycle are now open.
16:04:45 <johnsom> #link http://lists.openstack.org/pipermail/openstack-discuss/2019-August/008679.html
16:05:23 <rm_work> woo! one of ya'll can do this annoying job ;) lol
16:05:33 <johnsom> Let me or Adam know if you have any questions about the process/role
16:05:35 <rm_work> oooh, johnsom again? :D
16:05:52 <mugsie> johnsom again, definitely
16:06:12 <rm_work> yisss
16:06:20 <johnsom> mugsie I hear you are now available. Finally moving on to the fancy project?
16:06:42 <mugsie> I am happy in my no PTL job world :P
16:06:45 <johnsom> mugsie for Octavia PTL!
16:06:51 <johnsom> lol
16:07:16 <colin-> lots of time now that he's not doing designate!
16:07:24 <rm_work> well so far nothing has caught fire under my watch, so maybe I can do it again, lol
16:07:27 <johnsom> I am just waiting for mugsie to propose C# as an OpenStack supported language
16:07:44 <johnsom> grin
16:08:03 * mugsie writes that down for April 1
16:08:11 <johnsom> nice
16:08:53 <johnsom> Finally, my weekly reminder that feature freeze is upon us.
16:09:02 <johnsom> We must have features merged by Sept 2nd for library changes and Sept. 9th for everything else.
16:09:13 <johnsom> #link https://releases.openstack.org/train/schedule.html
16:09:31 <johnsom> Any other announcements this week?
16:10:45 <johnsom> #topic Brief progress reports / bugs needing review
16:11:12 <johnsom> I have been working on the failover flow task. It is coming along, but slow due to distractions.
16:12:05 <johnsom> Speaking of, I also proposed a patch that changes the devstack plugin to use a dual certificate authority with an intermediate CA. This is intended to help us test more like a production deployment.
16:12:13 <johnsom> #link https://review.opendev.org/#/c/678923/
16:13:12 <johnsom> Note, it does use weak security (1024 bit keys, aes128, etc.) to save gate entropy and CPU cycles. So no copy/paste please.  Refer to the certificates guide for how to do it better.
16:13:23 <ataraday_> I rebased listener, pool, lb, amphora, member flows to dict and test against joboard - all work properly, so I need to create heathmonitor change, and check l7 policy changes - that this refactor work will be complite.
16:14:25 <johnsom> Nice! After I get through this failover fix I plan to focus back on the jobboard work for a bit.
16:14:57 <johnsom> ataraday_ How do you feel about merge timing for those? Are these things you really want to get into Train or can they wait for the start of "U"?
16:15:19 <ataraday_> johnsom, I will probably ask you advise this week - we need to have housekeepling and healthmanager using worker v2 as well, how better to organize this...
16:15:50 <ataraday_> johnsom, I guess this should wait to get proper reviews
16:16:01 <johnsom> ataraday_ Ok, happy to help as I can. The failover is a priority for me.
16:16:27 <ataraday_> as none of my changes are merged for now
16:16:30 <johnsom> ataraday_ We can still do reviews and polish the patches. We would just potentially delay the merge to the start of U
16:17:00 <johnsom> In fact, I would highly support doing reviews on these
16:17:15 <ataraday_> yes, reviews are really appreciated :)
16:17:39 <johnsom> ataraday_ Ok, thank you. Sorry I didn't get to spend as much time helping as I had hoped.
16:18:25 <johnsom> Any other updates today?
16:18:28 <ataraday_> johnsom, no problem - issues with redis took a lot of time unfortunatly
16:18:57 <johnsom> Yeah, I still want to look at adding etcd support. Maybe I can do that in "U"
16:19:49 <johnsom> If there are no more updates, I will move on to Open Discussion
16:20:04 <johnsom> #topic Open Discussion
16:20:27 <johnsom> Also please remember, we have a priority patch review list we are working against:
16:20:28 <johnsom> #link https://etherpad.openstack.org/p/octavia-priority-reviews
16:20:30 <ataraday_> I'm afraid etc will have the same issue as redis as it is key-value storage after all, and zookeper has its own claim check - which makes it work easier
16:20:38 <johnsom> We have mad incredible progress, thank you!
16:21:32 <johnsom> ataraday_ So from your experience, zookeeper is currently the best backend for our jobboard work?
16:23:11 <johnsom> Are there any other topics this week?
16:23:21 <colin-> briefly want to echo lxkong's sentiment yesterday
16:23:47 <colin-> he and others (myself included) have run into situations where resources become stuckin an immutable state and the database updates necessary to clean them are (for me, at least) sometimes scary
16:23:59 <ataraday_> johnsom, I was testing only on devstack, but it seems better - as with redis we need to intoduce listerners, claims and retries on our side
16:24:02 <colin-> fully appreciate that there is graceful shutdown logic designed to prevent these cases but also recognize that i'm encountering them
16:24:21 <colin-> will try to do better about quantifying when and how in a story so that it's less anecdotal in the future
16:24:35 <ataraday_> and with zookeper just set proper type of backend
16:24:54 <johnsom> colin- If you see that occurring outside of a non-graceful shutdown I would be interested to see a bug report and the logs
16:25:30 <johnsom> colin- Are you on queens or newer?
16:26:24 <johnsom> ataraday_ ok, maybe we should re-evaluate our Redis decision now that we have more information. At least for the development phase. I don't want us spending a bunch of extra time due to a backend selection.
16:26:33 <ataraday_> Anyway I hope to make this configrable via conf which backend to use, so that it can be tested properly on scale, larger env, etc...
16:26:41 <johnsom> +1 to that
16:29:38 <johnsom> Any other topics today?
16:30:31 <johnsom> Ok, thanks folks! Have a great week.
16:30:36 <johnsom> #endmeeting