Tuesday, 2024-11-05

opendevreviewBrian Haley proposed openstack/neutron-lib master: pyupgrade changes for Python3.9+  https://review.opendev.org/c/openstack/neutron-lib/+/93409502:20
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN] Check LSP.up status before setting the port host info  https://review.opendev.org/c/openstack/neutron/+/93383606:40
opendevreviewliuyulong proposed openstack/neutron master: Add basical functionalities for metadata path extension  https://review.opendev.org/c/openstack/neutron/+/88153506:53
opendevreviewliuyulong proposed openstack/neutron master: Add metadata path extension openflows  https://review.opendev.org/c/openstack/neutron/+/88809706:53
opendevreviewliuyulong proposed openstack/neutron master: Fullstack case for metadata path  https://review.opendev.org/c/openstack/neutron/+/88809806:53
opendevreviewliuyulong proposed openstack/neutron master: Add devstack plugin to enable ovs metadata_path  https://review.opendev.org/c/openstack/neutron/+/92858606:53
opendevreviewRodolfo Alonso proposed openstack/neutron stable/2023.1: [OVN] Fix the revision number retrieval method  https://review.opendev.org/c/openstack/neutron/+/93402606:54
ralonsohslaweq, hello! no rush, if you have time (once approved, I'll backport both patches)06:57
ralonsoh* https://review.opendev.org/c/openstack/neutron/+/93396906:57
ralonsoh* https://review.opendev.org/c/openstack/neutron/+/93387706:58
ralonsohthanks!06:58
opendevreviewliuyulong proposed openstack/neutron master: WIP: Fullstack case for metadata path with real curl  https://review.opendev.org/c/openstack/neutron/+/93410207:07
opendevreviewLiushy proposed openstack/neutron-fwaas master: [OVN] Fix the provider error in devstack settings  https://review.opendev.org/c/openstack/neutron-fwaas/+/93410307:10
slaweqralonsoh: done08:29
ralonsohslaweq, thanks!08:29
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN] The Port_Group deletion implies the ACLs deletion  https://review.opendev.org/c/openstack/neutron/+/93387708:48
yosefHi everybody, I wanna know why we cant just use openvswitch metering agent for ovn? Doesn't ovn use ovs? https://bugs.launchpad.net/neutron/+bug/204877309:33
slaweqyosef it is explained in the linked bug and in https://docs.openstack.org/neutron/latest/ovn/gaps.html as well - this agent base on what neutron-l3-agent is doing and this agent don't works with ovn backend at all10:14
opendevreviewMerged openstack/neutron master: [OVN] Fix the revision number retrieval method  https://review.opendev.org/c/openstack/neutron/+/93375210:42
opendevreviewRodolfo Alonso proposed openstack/neutron master: DNM - Test "neutron-ovn-tempest-*" for OVN with WSGI  https://review.opendev.org/c/openstack/neutron/+/93184210:46
ralonsohbcafarel, hello! if you have some minutes: https://review.opendev.org/q/I12079de78773f7409503392d4791848aea90cb7b11:07
ralonsohthanks in advance!11:07
opendevreviewSahid Orentino Ferdjaoui proposed openstack/neutron master: rpc/dhcp: avoid get_network_info to return segments if not needed  https://review.opendev.org/c/openstack/neutron/+/88013111:22
opendevreviewRodolfo Alonso proposed openstack/neutron master: Allow net owner reader to get subnets  https://review.opendev.org/c/openstack/neutron/+/90023612:06
opendevreviewMerged openstack/ovn-octavia-provider master: Remove Python 3.8 support  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/93328612:58
bcafarelralonsoh: done, thanks for putting the RevisionNumberNotDefined class in neutron first before n-lib for easy backports :) 13:50
ralonsohbcafarel, thanks!13:50
* haleyb is making sure it's meeting time, always confused with clock change14:00
mlavallehaleyb: it is14:01
haleyb#startmeeting networking14:01
opendevmeetMeeting started Tue Nov  5 14:01:15 2024 UTC and is due to finish in 60 minutes.  The chair is haleyb. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
opendevmeetThe meeting name has been set to 'networking'14:01
ralonsohhello14:01
elvirao/14:01
haleybmlavalle: thanks for confirming :)14:01
ykarelo/14:01
haleybPing list: bcafarel, elvira, frickler, mlavalle, mtomaska, obondarev, slaweq, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, amotoki, haleyb, ralonsoh14:01
obondarevo/14:01
mlavalle\o14:01
lajoskatonao/14:01
frickler\o14:01
bcafarelo/14:02
slaweqo/14:02
haleyb#announcements14:02
rubasovo/14:02
cbuggyo/14:02
haleyb#link https://releases.openstack.org/epoxy/schedule.html14:02
haleybhope everyone had a good week last week, and thanks ralonsoh for running the meeting14:03
ralonsohyw14:03
haleybi am working on my write-up from PTG, travel and meetings kept me from it14:04
haleyb2023.1 is transitioning to unmaintained, think we are all set just waiting for release patches14:04
haleybReminder: If you have a topic for the drivers meeting on Friday, please add it to the wiki @ https://wiki.openstack.org/wiki/Meetings/NeutronDrivers14:05
haleybalthough saying that i might be out on friday, will see what topics we have beforehand14:06
haleybLet's continue to use the priorities dashboard for patches in the "ready to merge" state, it has worked well so far - see wiki for link (wiki does not allow url shorteners)14:07
lajoskatona+114:07
haleybany other announcements?14:07
haleyb#topic bugs14:08
haleybbcafarel was deputy last week, his report is at14:08
haleyb#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/ONVMDOUQ4RDL7GVE2YRJ4AWCPUZCNFKO/14:08
haleybthanks bcafarel!14:08
bcafarelnp, it was a quiet week overall!14:08
haleyband it looks like most everything has a patch proposed14:09
haleybthe only one that doesn't was for vpnaas14:10
haleyb#link https://bugs.launchpad.net/neutron/+bug/208618914:10
haleybnot sure if anyone from vpnaas is present and can take a look?14:11
bcafarelit would need some vpnaas eyes, the idea is nice but probably not a one-liner fix14:12
lajoskatonaI can send a mail out to the ones added OVN driver for vpnaas end of week if nobody checks it14:12
lajoskatonaagree with bcafarel14:12
haleybbcafarel: right, and nothing is propbably seamless with a reboot, but should know limitations14:13
haleyblajoskatona: thanks, that would work14:13
haleybi did not have any other bugs to discuss, does anyone else?14:14
haleybthis week elvira is the bug deputy, next week is slaweq - ok with both?14:14
ralonsoh(both are OK)14:15
slaweqyeap14:16
haleybok, moving on14:16
haleyb#topic community goals14:16
elvirayes, it's ok :) 14:16
haleyblooks like i need to update the wiki a little for this cycle, anyways...14:16
haleyblajoskatona: any progress on client deprecation?14:17
lajoskatonano 14:17
haleyblajoskatona: ack, thanks14:18
haleybralonsoh: and i noticed in last week's notes you were still creating LP bugs for eventlet deprecation?14:18
ralonsohyes, the main one is the WSGI migration14:19
ralonsohnot what we have done but the ASGI migration14:19
ralonsohI'm still reading the documentation and checking what is agreed in the community14:19
ralonsohbut there is no opinion on this and I'm afraid of implementing a solution in Neutron that won't be supported by the community14:20
ralonsohin any case, I'll add this info in the related LP bug14:20
haleybi will have to catch-up with that thread14:20
ralonsohthat's crazy, IMO14:20
ralonsohwe should agree on a server and a FW14:20
lajoskatonaok, so it inost just my lack of knowledge that I can't see the agreed solution and way forward :-)14:20
ralonsohin any case, at least for Neutron, WSGI works fine14:21
ralonsohwe don't have the problems that, for example, Nova has with multiple threads during the API call14:21
ralonsohanyway, I'll document that in a LP bug14:21
ralonsohthe rest of the bugs will be created too, to make work the rest of the agents14:21
haleybhas there been any direction from the TC on the way forward in their meetings?14:21
ralonsohno14:22
slaweqnothing I would be aware of14:22
ralonsohbut so far, as commented, we work fine with WSGI14:22
ralonsohwe need to "clean" the agents code and make them work without eventlet14:22
haleyback, and yes we are fine with WSGI for now14:23
ralonsohthat's all I have14:23
haleybthanks ralonsoh 14:23
haleyb#topic on-demand14:24
ralonsohone item14:24
ralonsohplease check https://review.opendev.org/c/openstack/neutron/+/93383614:24
ralonsohthis is fixing a recurrent issue in the CI14:24
ralonsohthanks!14:24
haleybralonsoh: ack, thanks. and is your comment in the wiki old? regarding postgresql jobs, etc? i think it is14:25
ralonsohah yes14:25
ralonsohso should we start deleting the jobs?14:25
haleybi usually clean before meeting but this is one hour earlier than normal14:25
ralonsohor removing the code in Neutron (tests, for example)14:25
ralonsohno no, the comment is for this meeting14:26
haleybah14:26
slaweqI think we can remove periodic jobs14:26
slaweqand maybe keep tests in the functional tests for now14:26
ihrachyswhy would we keep them?14:26
ralonsohok to both suggestions14:26
slaweqand add documentation warning that this backend is not tested by us14:27
ralonsohihrachys, because FTs don't have such CI impact14:27
slaweqihrachys I think it would be similar to what e.g. nova is doing14:27
ihrachysI don't know why nova is doing it, but I think in general, if we decide that something is not supported, then it's fair game to clean up code relevant to it (psql, linuxbridge or whatever else)14:28
ralonsohthat's a fair suggestion, we tend to leave leftovers in the code...14:30
ihrachysand if it's a capacity issue, I am happy to help with some of the cleanups (or take them over if you are busy)14:30
slaweqI'm fine either way, we can also remove everything related to postgresql if that's the way team wants to go :)14:31
haleybi was going to ask if someone was interested in doing this cleanup? and if we should do in a single change if possible14:31
haleybi would +1 removing it all, instead of leaving some cruft behind we will all forget about until it fails CI14:32
ihrachysimho whatever is most expedient; one piece is preferrable but if splitting simplifies life, also fine14:32
ralonsoh+1 to this then14:32
lajoskatona+1 to clean postgres things14:32
ihrachysralonsoh: I read you are going to clean up but if not, let us know14:32
ihrachysand thank you14:33
ralonsohno no, +1 to the idea of removing all14:33
ralonsohthis week I have no time14:33
ihrachysah ok I will look into it then14:33
ralonsohthanks!14:33
haleybihrachys: thanks! ping for reviews14:33
haleybany other topics?14:34
haleybif not it's coffee time14:35
mlavallee\o/14:35
slaweqo/14:35
haleybthanks for attending everyone and have a good week14:35
obondarev\o14:35
haleyb#endmeeting14:35
opendevmeetMeeting ended Tue Nov  5 14:35:30 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:35
opendevmeetMinutes:        https://meetings.opendev.org/meetings/networking/2024/networking.2024-11-05-14.01.html14:35
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/networking/2024/networking.2024-11-05-14.01.txt14:35
opendevmeetLog:            https://meetings.opendev.org/meetings/networking/2024/networking.2024-11-05-14.01.log.html14:35
lajoskatonao/14:35
ralonsohbye14:35
bcafarelo/14:35
ihrachysralonsoh: the patch is in gate, could you please check my comment before it perhaps hits the tree? https://review.opendev.org/c/openstack/neutron/+/933836/comments/5e9340c4_0d1499c1 thank you.14:59
ralonsohihrachys, sure, right now15:02
ralonsohihrachys, I'll update the patch15:03
ralonsohihrachys, replied to the question15:07
kevkoHi, I'm really desperate at this point ,  I'm using Neutron with OVN, and OVS starts spinning at 100% CPU, with the log showing entries  https://paste.openstack.org/show/bnleYUdDaH5W7Ohk1LiS/  and the time just keeps increasing. The ovs-appctl command hangs, so I can’t use coverage. While ovs-vsctl show works, any attempt to change anything15:07
kevkocauses it to freeze. If I delete OVS (including the volume) and restart the server, when I reconfigure OVS (re-create it), everything is initially fine because there are no rules in OVS. At this stage, if I remove the interface from br-ex and call reconfigure on OVN (which sets the metadata), everything is still OK. However, as soon as I put the15:07
kevkointerface back into br-ex, it crashes again15:07
kevkoKolla-ansible, kolla, images ubuntu 22.04, ovs 3.3.0 , 24.03.215:07
kevkofor me it looks like kind a bug in ovs or something ..anybody to help me ? :( 15:08
ihrachysralonsoh: question - is the order of ovsdb events guaranteed? namely, that the "another update_lsp_host_info call will be done *later*" is always true? (I mean, is it ever possible that the "another call" was already processed?15:13
ralonsohkevko, I think you'll have more feedback in the OVS mail threads. But you should also provide more info than 3 log lines. Maybe you can also increase the log level and try to debug this exact moment when OVS hangs15:13
ralonsohihrachys, no, the order is not guaranteed15:14
ralonsohihrachys, the UP and DOWN events can be treated by different workers or nodes15:14
ralonsohwe must sync both calls using the only info that is global, that is the Neutron DB15:15
ihrachysI can be totally confused, but here's my line of reasoning: your set_up handler fires. it sets neutron port=UP, but leaves lsp:host-id unset because nb lsp is down; and 2) your "set_down" handler is already complete, so there won't be another chance to clean host-id up. Now you seem to have neutron port UP with no host-id set.15:20
kevkoralonsoh: The problem is that I'm in serious trouble, I'm running out of time, and I really don’t know what else to do. I just thought I’d give it a try here. :(15:22
ralonsohihrachys, if we receive a single event (UP or DOWN), everything is handled correctly15:23
ralonsohihrachys, the problem is when we receive two events too close. The Neutron DB update is done synchronously with the API call, but the OVN event method is handled in other thread15:24
ralonsohso, in the example of two events, UP and DOWN (in this order): if we start treating the lsp host info for UP but at this time the port is already down, the call of "update_lsp_host_info" for UP won't do anything but it will the call for "update_lsp_host_info" for DOWN15:25
ralonsohthe same for the inverse order15:26
ihrachysralonsoh: if update_lsp_host_info is doing nothing, then shouldn't the set_port_status_down that called it also "do nothing" (namely, not set neutron port to DOWN)?15:28
ihrachysAFAIU it will first call self._plugin.update_port_status, then call update_lsp_host_info (which will do nothing).15:29
ralonsohihrachys, we need the transition and to inform about this to Nova15:29
ralonsohwe need to UP->DOWN and DOWN->UP15:29
ralonsohbut the problem when updating the LSP host info is that we not longer have the host info (in the UP event that is processed late)15:30
ihrachysI am not sure in this case we should tell Nova anything; hasn't "another call" already (or about to) set it to DOWN? if so, it should stay DOWN.15:31
ralonsohnova can handle the "unneeded" vif-events15:31
ralonsohwe also handle the provisioning blocks in the up/down calls15:32
ihrachysI still don't see how this patch addresses the scenario I described above where neutron port may be left UP because "another down call" is already complete (by another worker).15:34
ralonsohihrachys, the port is not left up, this is done outside this method15:35
ralonsohihrachys, the problem we also had in this method "update_lsp_host_info" is that the port binding get method has a retry decorator15:37
ihrachysthe update_lsp_host_info method called from 2 places: set_port_status_up and set_port_status_down. these two will change neutron port status (UP/DOWN) while - in the scenario you are trying to address - leaving host info untouched - and, depending on the order of ovsdb handlers - permanently inconsistent.15:37
ralonsohand we can wait too much time for this when is not actually needed15:37
ralonsohihrachys, the method does the same if "_wait_for_port_bindings_host" fails, it returns15:39
ralonsohwe are doing that but earlier15:39
ihrachysthis is true15:40
opendevreviewRodolfo Alonso proposed openstack/neutron-lib master: Define physical and tunnelled network types  https://review.opendev.org/c/openstack/neutron-lib/+/93414616:04
opendevreviewMerged openstack/neutron master: [OVN] Delete duplicated OVN resource type constants  https://review.opendev.org/c/openstack/neutron/+/93375416:05
opendevreviewLajos Katona proposed openstack/neutron-dynamic-routing master: pyupgrade changes for Python3.9+  https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/93414816:19
opendevreviewLajos Katona proposed openstack/neutron-dynamic-routing master: pyupgrade changes for Python3.9+  https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/93414816:28
opendevreviewLajos Katona proposed openstack/networking-bagpipe master: pyupgrade changes for Python3.9+  https://review.opendev.org/c/openstack/networking-bagpipe/+/93372516:31
opendevreviewMerged openstack/neutron master: [OVN] Check LSP.up status before setting the port host info  https://review.opendev.org/c/openstack/neutron/+/93383617:01
opendevreviewIhar Hrachyshka proposed openstack/neutron master: tests: always raise an explanation when status_int is wrong  https://review.opendev.org/c/openstack/neutron/+/93416217:43
ihrachysslaweq: ^ using your _check_http_response for all requests in the test module17:44
opendevreviewIhar Hrachyshka proposed openstack/neutron master: Remove postgresql code  https://review.opendev.org/c/openstack/neutron/+/93417118:40
opendevreviewIhar Hrachyshka proposed openstack/neutron-lib master: nit: Drop mentions of postgresql  https://review.opendev.org/c/openstack/neutron-lib/+/93417318:42
opendevreviewIhar Hrachyshka proposed openstack/neutron master: Remove postgresql code  https://review.opendev.org/c/openstack/neutron/+/93417118:49
opendevreviewIhar Hrachyshka proposed openstack/neutron-tempest-plugin master: nit: Drop mention of postgresql  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/93417418:51
opendevreviewIhar Hrachyshka proposed openstack/neutron master: Remove postgresql code  https://review.opendev.org/c/openstack/neutron/+/93417119:01
opendevreviewJakub Libosvar proposed openstack/neutron master: OVN metadata agent additional_chassis detection  https://review.opendev.org/c/openstack/neutron/+/93418821:59
opendevreviewIhar Hrachyshka proposed openstack/neutron master: Remove postgresql code  https://review.opendev.org/c/openstack/neutron/+/93417122:12
opendevreviewMerged openstack/neutron master: refactor: split out code to verify a lb member into a function  https://review.opendev.org/c/openstack/neutron/+/92979522:26
opendevreviewIhar Hrachyshka proposed openstack/neutron master: tests: move test_db_base_plugin_v2.py to common  https://review.opendev.org/c/openstack/neutron/+/93419022:33
opendevreviewMerged openstack/neutron master: refactor: construct member dict in one go  https://review.opendev.org/c/openstack/neutron/+/92979622:34
opendevreviewIhar Hrachyshka proposed openstack/neutron master: mypy: enable for most modules  https://review.opendev.org/c/openstack/neutron/+/92986622:57
opendevreviewIhar Hrachyshka proposed openstack/neutron master: gate: squash mypy into pep8 job  https://review.opendev.org/c/openstack/neutron/+/93419123:01
opendevreviewIhar Hrachyshka proposed openstack/neutron master: style: Clarify a check for mixed stateful/stateless SGs  https://review.opendev.org/c/openstack/neutron/+/92408723:07
opendevreviewBrian Haley proposed openstack/neutron master: Enable pylint useless-super-delegation check  https://review.opendev.org/c/openstack/neutron/+/93419223:11
opendevreviewBrian Haley proposed openstack/neutron master: Start enforcing additional pylint checks  https://review.opendev.org/c/openstack/neutron/+/93419323:11
opendevreviewIhar Hrachyshka proposed openstack/neutron master: DNM: run all ovs connections as leader-only=false  https://review.opendev.org/c/openstack/neutron/+/92146123:12
opendevreviewBrian Haley proposed openstack/neutron master: Start enforcing additional pylint checks  https://review.opendev.org/c/openstack/neutron/+/93419323:58

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