Wednesday, 2024-03-13

opendevreviewTakashi Kajinami proposed openstack/octavia master: dib: Remove remaining logic for CentOS/RHEL 8  https://review.opendev.org/c/openstack/octavia/+/91270003:14
opendevreviewTakashi Kajinami proposed openstack/octavia master: dib: Remove remaining logic for CentOS/RHEL 8  https://review.opendev.org/c/openstack/octavia/+/91270003:14
opendevreviewTakashi Kajinami proposed openstack/octavia master: dib: Remove Ubuntu Forcal support  https://review.opendev.org/c/openstack/octavia/+/91270103:17
opendevreviewGregory Thiemonge proposed openstack/octavia master: Fix fully-populated API with allowed_cidrs  https://review.opendev.org/c/openstack/octavia/+/91272108:53
gthiemonge#startmeeting Octavia16:00
opendevmeetMeeting started Wed Mar 13 16:00:33 2024 UTC and is due to finish in 60 minutes.  The chair is gthiemonge. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
opendevmeetThe meeting name has been set to 'octavia'16:00
tweiningo/16:00
gthiemongehi16:00
johnsomo/16:00
oschwarto/16:01
gthiemonge#topic Announcements16:02
gthiemonge* 2024.1 Caracal Release Schedule: RC116:02
gthiemongeThis is the RC1 milestone this week16:02
gthiemongewe don't expect to have another RC unless we find a critical bug16:03
gthiemongeso Octavia RC1 should be the version for Caracal16:03
gthiemongeright now we are only waiting for https://review.opendev.org/c/openstack/octavia/+/912599 to pass the CI (patch already approved)16:03
gthiemongethen I'll update the hash in the release patch16:03
johnsomSounds good. Did your reload patch land? I saw that was holding up the above bug16:04
gthiemongenop16:04
gthiemongehttps://review.opendev.org/c/openstack/octavia/+/90984916:04
johnsomOk, I will be looking at that16:05
gthiemongethanks16:05
gthiemonge* Dalmatian PTG16:06
gthiemongereminder: the PTG is next month16:06
gthiemongeI created an etherpad16:06
gthiemongehttps://etherpad.opendev.org/p/apr2024-ptg-octavia16:07
gthiemongeyou can add your topics there16:07
gthiemongeI haven't yet scheduled our session, IIRC the previous one was on Tuesday at 1400 UTC, maybe I'll book the same timeslot16:07
gthiemongeWDYT?16:08
oschwartsounds good to me16:08
johnsomYeah, that works for me16:08
tweiningfor me too16:09
gthiemongecool16:09
gthiemongethat's all I have for the announcements, did I miss something?16:10
tweiningisn't now ptl election period?16:12
johnsomIt is over:16:12
johnsom#link https://governance.openstack.org/election/16:12
johnsomCongrats to gthiemonge!16:12
tweiningah, thanks. congrats btw16:13
gthiemonge\o/16:13
oschwartcongratulations gthiemonge!16:13
johnsomThere were no contested projects, so the PTL election is over16:13
gthiemongemaybe in 6 months16:15
johnsomWe could also mention there is going to be an OpenStack Summit Asia in South Korea in September.16:15
johnsomIn case anyone is interested, the call for presentations is open16:16
johnsom#link https://openinfra.dev/summit/16:16
gthiemongeOpenInfra Days in Europe too16:16
gthiemonge#link https://oideurope2024.openinfra.dev/#registration=116:16
gthiemonge#topic CI Status16:19
gthiemongeso, on the CI, there are still some issue with haproxy, but it looks a bit better than the past week16:19
gthiemongeas mentioned earlier, https://review.opendev.org/c/openstack/octavia/+/909849 is a workaround for this issue16:19
johnsomYeah, it is still crashing for some reason16:19
gthiemongeif I can find some time, I'll investigate but it looks like an ubuntu-only bug16:20
johnsomYeah, I am pretty convinced it is a bug in the ubuntu version of haproxy16:21
gthiemonge+116:23
gthiemonge#topic Brief progress reports / bugs needing review16:25
gthiemongeI found and fixed a bug with the fully-populated LB API when using allowed_cidrs in the listener16:26
gthiemongehttps://review.opendev.org/c/openstack/octavia/+/91272116:26
johnsomI fixed one open issue with the SR-IOV patch that gthiemonge noticed, where the failover flow was not honoring the Amphora api timeouts, so failover could be longer than desired. That is in the testing gates now16:26
gthiemongehttps://bugs.launchpad.net/octavia/+bug/205775116:26
johnsomOtherwise, I am starting work on SR-IOV for members next16:27
oschwartI have this very WIP fix from the past:16:29
oschwarthttps://review.opendev.org/c/openstack/octavia/+/88759316:29
oschwartI wanted to consult with you guys about the idea behind it16:30
gthiemongeyeah I looked at it16:30
oschwart(assuming that a little more effort will make the implementation much better)16:30
gthiemongeI think we need to split the _graph_create function of each controller into 2 functions: _graph_validate & _graph_creates16:30
gthiemongeand _graph_validate would be called before the creation of the port in neutron16:31
oschwartsounds good to me. (or any way of validating the parameters of the LB before starting to create resources)16:32
oschwarts/LB/listeners+pools16:32
gthiemongewe need to check that it's possible with the validation functions, it depednds on the type of the params they receive16:32
johnsomI wonder if that is related to: https://review.opendev.org/c/openstack/octavia/+/91044916:32
gthiemongeno the issue happens in the API only, the VIP port is created before the subresources are validated16:33
johnsomDoes the LB go to provisioning state of ERROR?16:34
gthiemongeso if the validation of a port/listener/etc... fails, an exception is raised, the API returns an error, but the port is still there16:34
gthiemongenop, no LB in the DB, only a dangling port16:34
johnsomAh, so it doesn't go into the flow yet. Got it16:34
gthiemongeyeah only in the API16:35
gthiemongeanother solution would be to delete the port when an exception is raised, but there's no direct access to the neutron API, we need to update and pass through the provider driver, so it would be an unbackportable change16:35
johnsom Yeah, that is a bit nasty as it could lock up a requested fixed IP.16:36
oschwartI prefer calling the validation functions, we already have them implemented, at least almost fully16:37
gthiemonge+116:38
johnsomWe should think about how to cleanup as well, i.e. if the DB commit fails due to the DB going down, would we end up in the same situation.16:40
gthiemongeright16:41
tweiningI think we didn't discuss our policy about backporting to the new unmaintained/* branches in the future. Will we stop backporting fixes to those branches upstream?16:42
tweining(I just remember we did not discuss that yet, I think)16:42
gthiemongemaybe a good topic for the PTG, I'm a bit annoyed because all the backports I created for stable/* were abandonned when the branches were renamed16:43
tweiningok. i'll add it to the epad16:43
johnsomYeah, that is a good PTG topic16:44
gthiemonge#topic Open Discussion16:45
gthiemongeI think we're already there16:45
tweiningnothing else from me16:45
johnsomYeah, I don't think I have anything else16:46
oschwartme neither16:46
gthiemongeokay16:47
gthiemongethank you guys! good discussions!16:47
gthiemonge#endmeeting16:47
opendevmeetMeeting ended Wed Mar 13 16:47:17 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:47
opendevmeetMinutes:        https://meetings.opendev.org/meetings/octavia/2024/octavia.2024-03-13-16.00.html16:47
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/octavia/2024/octavia.2024-03-13-16.00.txt16:47
opendevmeetLog:            https://meetings.opendev.org/meetings/octavia/2024/octavia.2024-03-13-16.00.log.html16:47
opendevreviewPierre-Yves Jourel proposed openstack/octavia master: Add specs to resize a load balancer  https://review.opendev.org/c/openstack/octavia/+/88549017:21
opendevreviewPierre-Yves Jourel proposed openstack/octavia master: Add specs to resize a load balancer  https://review.opendev.org/c/openstack/octavia/+/88549017:41
opendevreviewMerged openstack/octavia master: Check Amphora status on SR-IOV failover flows  https://review.opendev.org/c/openstack/octavia/+/91259918:58

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!