16:00:26 #startmeeting Octavia 16:00:26 Meeting started Wed Oct 18 16:00:26 2023 UTC and is due to finish in 60 minutes. The chair is gthiemonge. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:26 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:00:26 The meeting name has been set to 'octavia' 16:00:31 o/ 16:00:34 Hi Folks 16:00:38 o/ 16:00:38 o/ 16:00:42 o/ 16:01:34 #topic Announcements 16:01:39 * 2024.1 Caracal vPTG 16:01:49 the PTG is next week! 16:02:01 on Tuesday 14:00 UTC - 18:00 UTC 16:02:07 (I don't think we really need 4 hours) 16:03:03 and of course, the etherpad: 16:03:08 https://etherpad.opendev.org/p/caracal-ptg-octavia 16:03:20 thanks ! 16:03:49 QG: will you attend the PTG? 16:04:03 oh yeah I see your name now 16:04:04 i think so 16:04:05 cool 16:04:46 so Folks, if you have some time before the PTG, maybe you can read the specs proposals 16:04:55 LB resize 16:04:57 https://review.opendev.org/c/openstack/octavia/+/885490 16:05:01 SRIOV 16:05:03 https://review.opendev.org/c/openstack/octavia/+/891244 16:05:13 Active-Active BGP 16:05:15 https://review.opendev.org/c/openstack/octavia/+/888020 16:05:25 ACMEv2 Cert management 16:05:28 https://review.opendev.org/c/openstack/octavia/+/877281 16:06:43 do we have any other announcements? 16:07:28 not from my side 16:07:39 I don't 16:07:50 ack 16:07:58 #topic CI Status 16:08:18 FYI we need to update the zuul config on stable branches 16:08:23 there are still some centos-8-stream jobs (non-voting) 16:08:48 they fail and one job had been stuck in the CI for 24h 16:09:06 (I just rebased the commit so it killed the stuck job) 16:09:54 if we find a volunteer, it's cool 16:09:57 or I'll do it 16:11:10 if it's not urgent I can do it 16:11:15 +1 16:12:26 #topic Brief progress reports / bugs needing review 16:13:00 FYI we fixed an important bug on master, the amphora configure API call didn't work 16:13:05 https://review.opendev.org/c/openstack/octavia/+/898232 16:13:26 it needs to be backported to 2023.2 (and we will propose a bugfix release) 16:13:42 (the changes required by sqlaclhemy2 introduced the bug) 16:15:53 i have started working on https://bugs.launchpad.net/octavia/+bug/2039430 but i'm stuck on the functionnal tests in test_load_balancer.py 16:16:28 it broke 78 functional tests :-D 16:16:59 QG: if you need help, maybe you can upload the patch and we can take a look 16:17:09 but 78 is not bad 16:17:13 :D 16:17:19 gthiemonge: cool will do 16:17:58 Yeah, sometimes those come down to changing one thing fixes them all 16:19:31 I am making good progress on SRIOV. I have ports attaching to the amphora now. Most of my work over the last week was dealing with failure cases and nova bugs 16:19:54 I have opened a nova bug about some "API unexpected error" 500s I get 16:20:08 In the mean time, I am parsing the exception text to get something useful out of it. 16:21:07 My plan is to get the VIP path working, then do a push, then work on tests, then work on the nftables stuff in a different patch. Following that will be looking at the member path. 16:22:14 cool 16:22:46 you're used to splitting patches when they're too big ? 16:23:28 I am trying to break it down on logical boundaries. But, small patches is a skill I have yet to master. Grin 16:23:54 it is good practice and make patches a lot easier to review 16:24:42 ah ok cool ! was thinking it is harder to test it before all are merged but if they are link by a relation chain then you can tests them all 16:25:09 Right 16:25:12 you need to have at least unit tests for all the small parts 16:25:29 Right, the patch must have unit tests to merge 16:26:18 For this one, tempest may not be fully possible as the distros don't have the virtual SR-IOV driver in qemu yet 16:28:51 ack 16:30:41 I have not check 23.10 yet to see if it's there. 16:32:02 Ah, it is in 23.10, cool 16:32:19 but will it work in the CI? 16:32:57 ... maybe .... I don't know. I have a cookbook to get it working, but I have not tried it yet. I'm developing on real hardware 16:33:20 In theory it's a pure virtual driver that will allow allocating VFs 16:33:45 So, should work if the distro devstack is running on has qemu/libvirt support for it. 16:34:01 I don't know if devstack will support 23.10 or not, it's a short term release 16:36:52 ok 16:38:43 #topic Open Discussion 16:38:50 any other topics folks? 16:39:25 Is this meeting cancelled next week? Since we will have the PTG 16:40:15 right, I think we don't need a meeting 16:40:19 I'll send an email 16:40:29 on another subject, about the python-octaviaclient i have some questions : do you know why the python-octaviaclient is not integrated as a dependency in python-openstackclient, like neutron of swift ( the fact that we need to install it in addition to openstackclient ) 16:40:48 hmm good question 16:40:50 I don't know 16:41:09 +1 for that suggestion from me 16:41:36 Yeah, so OpenStack is (was?) moving to a plugin model for all of the clients. Neutron and swift were "legacy" in repo before the plugin model was created. 16:42:00 In theory, all of the projects were supposed to go to the plugin model. 16:42:27 It also makes getting patches merged easier as the core team can be Octavia people, as opposed to openstackclient folks, etc. 16:42:59 I think you're talking about adding octaviaclient to this list https://opendev.org/openstack/python-openstackclient/src/branch/master/requirements.txt 16:42:59 Now, the movement to plugins (many projects are plugins, not just Octavia) has slowed 16:43:03 right? 16:43:37 Ah, I thought i was just the plugin model issue since QG mentioned neutron and swift 16:43:42 neutron is a core service of openstack (not sure about swift) so it makes sense to require that to be installed 16:44:30 I think the key is to not have to install it manually 16:44:38 #link https://opendev.org/openstack/python-openstackclient/src/branch/master/openstackclient/network 16:45:02 Well, not all clouds have all services, so installing everything may not make sense. 16:45:29 ok make sens thanks ! 16:45:44 I would not be opposed to adding Octavia to the requirements.txt there, like keystone, etc. 16:46:02 someone can propose it 16:46:32 I mean, cinder (an optional service) is there, so... 16:48:00 i can do it if you want, no issue 16:48:37 QG: if you propose a patch, send the link here, I'll +1 16:49:08 gthiemonge: ok sure ! 16:50:09 and do know if now that the new openstack release is out we can release https://review.opendev.org/c/openstack/python-octaviaclient/+/896255 on pypi ? 16:50:38 oops, I should have done that 16:50:53 I'll propose a bugfix release for python-octaviaclient 16:51:20 gthiemonge: cool thanks ! 16:52:55 anything else Folks? 16:53:46 Nothing from me 16:54:23 Nothing from me 16:55:10 Nope, looking forward to the PTG! 16:55:14 ok 16:55:14 yeah 16:55:22 see you at the PTG! 16:55:30 #endmeeting