16:00:41 <gthiemonge> #startmeeting Octavia
16:00:41 <opendevmeet> Meeting started Wed Aug 31 16:00:41 2022 UTC and is due to finish in 60 minutes.  The chair is gthiemonge. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:41 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
16:00:41 <opendevmeet> The meeting name has been set to 'octavia'
16:00:46 <gthiemonge> Hi Folks
16:00:57 <oschwart> o/
16:01:01 <QG> Hi
16:01:04 <johnsom> o/
16:01:08 <tweining> o/
16:01:11 <pyjou> o/
16:01:50 <gthiemonge> wow, what a crowded channel ;-)
16:02:15 <johnsom> Folks are back from vacation. lol
16:03:26 <gthiemonge> #topic Announcements
16:03:36 <gthiemonge> ** OpenStack Zed schedule
16:03:59 <gthiemonge> this week is Feature Freeze/Final release for client libraries!
16:04:09 <gthiemonge> #link https://releases.openstack.org/zed/schedule.html
16:04:46 <gthiemonge> I see that some patches are already approved! that's great
16:05:02 <tweining> I also read that it's deadline for submitting release highlights
16:05:21 <johnsom> Yes, that is correct
16:05:28 <gthiemonge> oh thanks for the heads up
16:05:57 <gthiemonge> our features are cool, I will propose a patch, but first we need to merge them
16:06:39 <gthiemonge> I'm going to work on it
16:07:10 <tweining> yes, the failover circuit breaker change didn't get a lot of reviews yet. I hope nobody finds any last minute issues.
16:07:33 <gthiemonge> one CR+2
16:07:49 <tweining> that is a good start :D
16:08:02 <johnsom> I plan to look at it today
16:08:59 <oschwart> I was looking at it until this meeting
16:09:09 <gthiemonge> great
16:10:30 <gthiemonge> ** PTL election
16:10:30 <tweining> thanks
16:10:44 <gthiemonge> FYI I have proposed my candidacy for Octavia PTL on the openstack-discuss ML
16:10:56 <johnsom> Twelve more years!
16:11:07 <tweining> +1 :D
16:11:29 <gthiemonge> please note: "We have extended the nomination period 7 days"
16:11:29 <tweining> you do a great job!
16:11:48 <gthiemonge> thanks
16:13:10 <gthiemonge> ** Antelope PTG
16:13:23 <gthiemonge> I created an etherpad for the Antelope PTG:
16:13:31 <gthiemonge> #link https://etherpad.opendev.org/p/antelope-ptg-octavia
16:13:58 <gthiemonge> we can propose topics at the bottom of the doc
16:14:22 <gthiemonge> anything you want: Feature, Bugs, CI, dashboard, blahblah
16:17:13 <gthiemonge> I think the CI is fine, I'll skip the "CI status" topic
16:17:22 <gthiemonge> #topic Brief progress reports / bugs needing review
16:18:03 <gthiemonge> so, any urgent reviews (that are not feature patches)?
16:18:43 <tweining> I worked on fixing an issue with backwards compatibilty
16:18:51 <tweining> https://review.opendev.org/c/openstack/octavia/+/854609
16:19:07 <tweining> but I wouldn't consider it urgent
16:19:44 <johnsom> I have mostly been focused on reviewing some of these large feature patches....
16:19:57 <gthiemonge> tweining: oh thanks, I need to take a look at this one ;-)
16:20:26 <tweining> it will also need to be backported to Yoga I think
16:20:37 <gthiemonge> yeah same for me, lot of reviews, and lot of updates of these large patches ;-)
16:21:10 <QG> it is not urgent either but I worked on a small fix : https://review.opendev.org/c/openstack/octavia/+/852459
16:21:20 <gthiemonge> tweining: this patch is also needed in train ;-)
16:22:18 <johnsom> QG Yeah, I never did like that those were "sharing" a list. Thanks for the patch
16:22:25 <tweining> gthiemonge: really? I thought server-state-file was only added during Yoga
16:22:43 <gthiemonge> QG: thanks for this patch, it's not in the review list (in the etherpad), I'm adding it (on top of it)
16:23:39 <gthiemonge> tweining: yeah it affects our downstream CI with train
16:23:46 <tweining> ok
16:29:35 <gthiemonge> #topic Open Discussion
16:30:18 <gthiemonge> QG: pyjou: Hey Folks, do you plan to join the Octavia PTG?
16:30:44 <tweining> it is virtual again.
16:31:02 <QG> why not we don't really know how this kind of event works
16:31:33 <QG> but with pleasure, I'm sure it can be very interesting
16:32:03 <gthiemonge> it's like a long meeting with a lot of topics :D -- we will talk about what will be in Antelope, what we need to improve/fix
16:32:16 <gthiemonge> but that would be great to hear your feedback about octavia
16:32:47 <johnsom> It is basically an event for discussing development topics and plan for the Antelope release. It is a video meeting this time.
16:33:26 <QG> ok well clearly we will try to attend
16:33:52 <gthiemonge> cool
16:34:21 <QG> I wanted to know what you think about adding the functionality in horizon to be able to configure a listener with prometheus ?
16:35:44 <johnsom> I think it is a good idea and should be fairly straight forward.
16:35:55 <gthiemonge> good question.. johnsom what is missing? only the "PROMETHEUS" protocol in the box? or are there other params?
16:36:13 <johnsom> Yeah, that is it. They are the same as any other Listener
16:37:02 <johnsom> The tricky part might be that you can't really use PROMETHEUS in the initial create workflow, as it cannot have any pools
16:37:09 <gthiemonge> as we're really close to the feature freeze, I'm not sure we will have it in Zed
16:37:22 <johnsom> It would be a listener detail page only kind of thing.
16:37:23 <gthiemonge> johnsom: now we can select to not create pools
16:37:31 <johnsom> Ok
16:37:35 <gthiemonge> johnsom: so maybe we can automate it when selecting prometheus
16:38:20 <johnsom> QG I'm interested in feedback on that feature and the dashboard. It was a "for fun" feature
16:39:35 <johnsom> #link https://review.opendev.org/c/openstack/octavia-tempest-plugin/+/812260
16:39:50 <johnsom> The tests need some review action as well.
16:40:29 <QG> @jonhsom We love it ! on our side we use it for benchmark ( hardware, haproxy version ...) and it works well
16:43:27 <johnsom> The one thing with benchmarks is with the really high traffic levels, the Prometheus stats scrape can get blocked. I.e. if the NIC port runs out of bandwidth. I hit that playing around with it.
16:46:54 <johnsom> Thanks for the feedback. I am glad someone is finding value in it.
16:47:12 <gthiemonge> glad to hear that too!
16:48:56 <QG> we didn't experience such issue, but on the other hand we had the rsyslog which took a good part of the cpu
16:48:56 <gthiemonge> ok Folks, anything else?
16:49:32 <tweining> not from me
16:49:33 <gthiemonge> oh yeah I noticed that rsyslog consumes a lot during some perf tests
16:49:49 <johnsom> Yeah, I recommend turning off local log storage. The IO can really impact performance.
16:50:07 <QG> I wanted to ask you if you had already thought of integrating let's encrypt for the generation of certificates, that it be managed by Octavia ?
16:50:08 <johnsom> It's a log record per request, so adds up quickly
16:51:02 <QG> johnsom yep very quickly, thanks for the tips on local storage will try it
16:52:06 <johnsom> We have tried to stay away from being a CA for TLS terminated load balancers. We integrate with Barbican and Castellan as a source for the certs. It might be interesting to consider extending one of those to integrate with let's encrypt.
16:52:07 <gthiemonge> no idea on how to integrate let's encrypt... as a new driver for cert management?
16:54:01 <gthiemonge> johnsom: do you mean "integrating let's encrypt in barbican" and not in octavia?
16:54:26 <johnsom> gthiemonge Correct
16:55:29 <gthiemonge> ok
16:55:41 <johnsom> In a way, it's almost it's own service that would store the certs in Barbican and update the references in Octavia. Whenever let's encrypt updates the cert
16:56:47 <dmendiza[m]> 👀
16:56:53 <dmendiza[m]> someone said the magic word
16:56:58 <pyjou> But with Let's encrypt. The ACME challenge need to be behind the server and in this case is Octavia.
16:57:17 <johnsom> Hi Doug
16:57:26 <dmendiza[m]> 👋
16:57:47 <johnsom> The topic of let's encrypt integration for TLS terminated load balancers came up
16:57:48 <gthiemonge> pyjou: oh yes, right
16:58:06 * dmendiza[m] catches up on scrollback
16:58:29 <tweining> wouldn't that be a good topic for PTG?
16:59:41 <johnsom> Yes, I think it would be a good topic for the PTG
17:00:27 <gthiemonge> +1
17:01:08 <gthiemonge> and it's time
17:02:02 <johnsom> Yep, that is the meeting time limit. Thanks everyone!
17:02:16 <QG> Thanks !
17:02:18 <oschwart> Thanks folks!
17:02:19 <gthiemonge> Ok Folks, we are overtime!
17:02:25 <pyjou> Thanks!
17:02:30 <gthiemonge> thank you all!
17:02:36 <gthiemonge> #endmeeting