Monday, 2024-02-05

*** jph0 is now known as jph08:25
tkajinamwondering if anyone has idea about this ... based on https://review.opendev.org/c/openstack/neutron/+/823637 now I'm setting rpc_worker=0 in ml2 ovn tests but I noticed there are still two RpcWorkers in ps08:46
tkajinamhttps://zuul.opendev.org/t/openstack/build/719a7ec5ca4b40b4a91bb88501233cc908:46
tkajinamneutron.conf is found in logs/etc/neutron and this contains rpc_workers=0, but ps result in logs/ps.txt shows two RpcWorker08:47
tkajinamneutron    70440   70395   70440  0.2  1.8 140796 150192 neutron-server: rpc worker ...08:48
tkajinamneutron    70441   70395   70441  0.0  1.7 134208 143024 neutron-server: rpc worker  ...08:48
tkajinamI wonder if there are any other factors enabling rpc workers ? I can open a bug but would like to get some feedback in case this is an expected behavior08:49
tkajinamI roughly guess this is an issue caused by https://github.com/openstack/neutron/blob/master/neutron/service.py#L17808:51
tkajinamhmm one might be RpcReportsWorker08:53
opendevreviewRodolfo Alonso proposed openstack/neutron stable/2023.1: dhcp: fix usage of helper function to retrieve process name  https://review.opendev.org/c/openstack/neutron/+/90771108:54
*** ralonsoh_ is now known as ralonsoh08:56
ralonsohtkajinam, hi, is the rpc_worker value explicitly defined in the job?08:57
ralonsohas you commented, if nothing is defined, this calculation will be done08:57
ralonsohthis is not a bug, RPC could be used in ML2/OVN if DHCP agents are needed08:57
tkajinamralonsoh, that's the result from one of the puppet jobs and I set 0 explicitly. it seems one of these two is RpcReportsWorker but I'm unsure we still need the other RpcWorker08:58
tkajinamwe don't have dhcp agent deployed in that scenario08:58
ralonsohah ok, you also have "rpc_state_report_workers" variable08:59
tkajinam #rpc_state_report_workers = 109:00
tkajinamthe option is not set (it's commented out) so I assume it's effectively 109:00
ralonsohyes, is 1 vy default09:01
ralonsohby*09:01
sahido/ guys do you have any idea of what is happening from a given agent in an az, when it has to handle a network with subnet on different AZs?09:05
opendevreviewTakashi Kajinami proposed openstack/neutron master: Use different process title for RpcReportsWorker and RpcWorker  https://review.opendev.org/c/openstack/neutron/+/90771209:05
tkajinam^^^ so this should change the proc title for RpcReportsWorker09:06
sahids/subnet/subnets09:06
ralonsohtkajinam, checking that right now09:06
tkajinamso my current question is... do we still need the other RpcWorker when ml2-ovn is used without any other agents such as dhcp or vpnaas ?09:06
ralonsohtkajinam, no that I'm aware09:09
ralonsohand if you disable it but is needed, nothing will work, so it will be easy to detect09:10
ralonsohsahid, sorry, I don't understand the question09:10
ralonsohsubnet on different AZs?09:10
tkajinamralonsoh, ah, ok. let me try removing that max function to actually pass worker 0 to RpcWorker and I'll check how it works.09:11
opendevreviewTakashi Kajinami proposed openstack/neutron master: DNM: Allow real 0 rpc workers  https://review.opendev.org/c/openstack/neutron/+/90771309:16
houtknotsHello everyone, could I kindly request someone to review my recent merge request? 900212: Change exception messages to error log messages for DNS integration. | https://review.opendev.org/c/openstack/neutron/+/90021209:19
sahidralonsoh: yes it's a bit confuse, let's say you have a netowk with 2 subnets, each of the subnet are attached to physnet on different AZs09:20
opendevreviewTakashi Kajinami proposed openstack/neutron master: Use different process title for RpcReportsWorker and RpcWorker  https://review.opendev.org/c/openstack/neutron/+/90771209:27
opendevreviewTakashi Kajinami proposed openstack/neutron master: DNM: Allow real 0 rpc workers  https://review.opendev.org/c/openstack/neutron/+/90771309:27
opendevreviewTakashi Kajinami proposed openstack/neutron master: Use different process title for RpcReportsWorker and RpcWorker  https://review.opendev.org/c/openstack/neutron/+/90771209:27
opendevreviewTakashi Kajinami proposed openstack/neutron master: DNM: Allow real 0 rpc workers  https://review.opendev.org/c/openstack/neutron/+/90771309:27
sahidso the real question, is more like how the dhcp agent handle the case when it has to handle a network with subnets attached to different physnet09:27
tkajinamphysnet and availability zone are both associated with networks, instead of subnets iirc or do I misunderstand something ?09:34
tkajinamif you deploy networks across az but your underlying networks are disconnected between az then probably something like;09:36
tkajinamuse AZAwareWeightScheduler, deploy dhcp agents in all az, and set dhcp_agents_per_network >= (number of az) ?09:36
tkajinamthis assumes you have ml2-ovs(or linux bridge) + dpch agent, though. I'm not very familiar with multi AZ deployment with ml2-ovn09:36
sahidtkajinam: yes, in that case, physnet is associated to segment and segment to subnet, it's case of routed provider network09:44
sahidif you have physnet per az09:45
sahidso you have a network with subnets on different az09:45
opendevreviewMerged openstack/ovsdbapp master: tox: Drop envdir  https://review.opendev.org/c/openstack/ovsdbapp/+/90760810:44
opendevreviewTakashi Kajinami proposed openstack/neutron master: Use different process title for RpcReportsWorker and RpcWorker  https://review.opendev.org/c/openstack/neutron/+/90771210:49
opendevreviewTakashi Kajinami proposed openstack/neutron master: DNM: Allow real 0 rpc workers  https://review.opendev.org/c/openstack/neutron/+/90771310:50
sahidralonsoh: ok I understans know, (in case you may be interested too), https://github.com/openstack/neutron/blob/master/neutron/api/rpc/handlers/dhcp_rpc.py#L17711:05
sahidbasically we return to the dhcp agent only subnets that is attached to11:06
opendevreviewMerged openstack/os-ken master: tox: Drop envdir  https://review.opendev.org/c/openstack/os-ken/+/90760511:07
sahidthere are so many factors :-)11:07
opendevreviewyatin proposed openstack/neutron master: [DNM][functional] ovs-vswitchd debug log  https://review.opendev.org/c/openstack/neutron/+/90703711:08
sahids/know/now11:12
opendevreviewRodolfo Alonso proposed openstack/neutron master: WIP - Add the external network "filter_hook" to the subnet object  https://review.opendev.org/c/openstack/neutron/+/90731312:13
opendevreviewMerged openstack/neutron stable/2023.2: [Fullstack] Consolidate segmentation_id update tests into single test  https://review.opendev.org/c/openstack/neutron/+/90722612:49
opendevreviewMerged openstack/neutron master: tox: Drop envdir  https://review.opendev.org/c/openstack/neutron/+/90760612:53
opendevreviewMerged openstack/neutron stable/2023.2: dhcp: fix usage of helper function to retrieve process name  https://review.opendev.org/c/openstack/neutron/+/90727012:53
opendevreviewMerged openstack/neutron-lib master: [sqlalchemy-20] Use sqlalchemy.orm.DeclarativeBase  https://review.opendev.org/c/openstack/neutron-lib/+/90662713:02
sahidthere is an interesting point which does not look to be documented, in routed provider network, for a given network with subnets attached to different segment. A given agent attached to a physnet will handle only one subnet of that agent14:01
sahidif you configure dhcp_agents_per_network = 1 the other subnet will never be addressed by the agent on the other physnet14:02
sahidright?14:02
sahidthat also means, if you want HA you need 4 DHCP Agents, 2 for each subnet/phynet/segment14:03
opendevreviewTakashi Kajinami proposed openstack/neutron master: Use different process title for RpcReportsWorker and RpcWorker  https://review.opendev.org/c/openstack/neutron/+/90771215:56
*** ravlew is now known as Guest171516:29
opendevreviewOpenStack Release Bot proposed openstack/networking-bagpipe master: reno: Update master for unmaintained/yoga  https://review.opendev.org/c/openstack/networking-bagpipe/+/90785116:45
opendevreviewOpenStack Release Bot proposed openstack/networking-bgpvpn master: reno: Update master for unmaintained/yoga  https://review.opendev.org/c/openstack/networking-bgpvpn/+/90785316:45
opendevreviewOpenStack Release Bot proposed openstack/networking-sfc master: reno: Update master for unmaintained/yoga  https://review.opendev.org/c/openstack/networking-sfc/+/90785616:45
opendevreviewOpenStack Release Bot proposed openstack/neutron-dynamic-routing master: reno: Update master for unmaintained/yoga  https://review.opendev.org/c/openstack/neutron-dynamic-routing/+/90785816:45
opendevreviewOpenStack Release Bot proposed openstack/neutron-lib master: reno: Update master for unmaintained/yoga  https://review.opendev.org/c/openstack/neutron-lib/+/90786016:45
opendevreviewOpenStack Release Bot proposed openstack/neutron-vpnaas-dashboard master: reno: Update master for unmaintained/yoga  https://review.opendev.org/c/openstack/neutron-vpnaas-dashboard/+/90786216:46
opendevreviewOpenStack Release Bot proposed openstack/neutron-vpnaas master: reno: Update master for unmaintained/yoga  https://review.opendev.org/c/openstack/neutron-vpnaas/+/90786416:46
opendevreviewOpenStack Release Bot proposed openstack/neutron master: reno: Update master for unmaintained/yoga  https://review.opendev.org/c/openstack/neutron/+/90786616:46
opendevreviewOpenStack Release Bot proposed openstack/os-ken master: reno: Update master for unmaintained/yoga  https://review.opendev.org/c/openstack/os-ken/+/90786816:46
opendevreviewOpenStack Release Bot proposed openstack/ovn-octavia-provider master: reno: Update master for unmaintained/yoga  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/90787016:47
opendevreviewOpenStack Release Bot proposed openstack/ovsdbapp master: reno: Update master for unmaintained/yoga  https://review.opendev.org/c/openstack/ovsdbapp/+/90787216:47
opendevreviewOpenStack Release Bot proposed openstack/python-neutronclient master: reno: Update master for unmaintained/yoga  https://review.opendev.org/c/openstack/python-neutronclient/+/90787416:47
opendevreviewOpenStack Release Bot proposed openstack/tap-as-a-service master: reno: Update master for unmaintained/yoga  https://review.opendev.org/c/openstack/tap-as-a-service/+/90787616:47
opendevreviewMerged openstack/neutron-lib master: tox: Drop envdir  https://review.opendev.org/c/openstack/neutron-lib/+/90760717:56
JayFHey, we're getting some reports of Ironic+NGS+OVN users being impacted by https://review.opendev.org/c/openstack/neutron/+/872033 -- it looks like progress has stalled on it.18:17
JayFI'm not super knowledgable on neutron to offer help to fix, but if there's anything specific I can do to unblock it, please let me know.18:17
mlavallehaleyb: is Launchpad also down for you?18:25
haleybmlavalle: it was up and just went back down according to my sources. i don't know the reason for the current outage :(18:34
*** dasm is now known as Guest173920:33
haleybmlavalle: it's back, so hurry up and login :)20:37
*** Guest1739 is now known as dasm20:38

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