| slaweq | ralonsoh: lajoskatona: hi | 07:51 |
|---|---|---|
| slaweq | I just reopened https://bugs.launchpad.net/neutron/+bug/1944201 | 07:51 |
| lajoskatona | slaweq: Hi | 07:51 |
| ralonsoh | let me check | 07:51 |
| slaweq | it seems it still happens even with os-ken 2.2.0 | 07:51 |
| slaweq | :/ | 07:51 |
| lajoskatona | so the ryu cherry-picks are not enough.... | 07:52 |
| slaweq | lajoskatona: at least not those 2 which we were thinking that will help | 07:54 |
| slaweq | maybe something else is also needed | 07:54 |
| slaweq | we merged many of them recently and we didn't made new version of os-ken yet | 07:54 |
| bcafarel | slaweq: was it seen with periodic neutron-ovs-tempest-with-os-ken-master job? if yes we could add it to experimental to check with these recent patches | 08:11 |
| bcafarel | (unless we can trigger periodic from gerrit, but I don't think we can) | 08:11 |
| slaweq | bcafarel: I didn't check periodic jobs today | 08:11 |
| lajoskatona | bcafarel: I haven't seen in periodic jobs | 08:12 |
| lajoskatona | at least in latest runs | 08:13 |
| bcafarel | hmm it looks green overall indeed | 08:13 |
| eugenmayer | when deploying neutron, it is for the l3 agent and the LB. Are those responsible to span networks across compute nodes and LB is for exposing internal services to floating IPs? | 08:15 |
| slaweq | bcafarel: I saw it maybe twice during this week in the check queue | 08:16 |
| slaweq | so it's not as often and it's likely that we will not hit it in the periodic job often | 08:16 |
| slaweq | eugenmayer: I'm not sure if I understand Your question | 08:17 |
| slaweq | generally L3 agent is responsible for configuration of the neutron routers for tenants | 08:17 |
| slaweq | and LB agent is providing L2 connectivity for ports (vms but also router ports) | 08:18 |
| slaweq | floating IPs are configured inside routers by L3 agent | 08:18 |
| eugenmayer | i'am new to openstack, so i could imagine my questions are just not precise enough / use the wrong terms. Please bear with me on that, i try to adopt | 08:19 |
| eugenmayer | Currently i try to understand adopt how the distributed features for storage (cinder) and networking are integrated and where / how those service run. | 08:20 |
| eugenmayer | In terms of networks, i have 2 questions in common, the one asked before was about something like 'considering that i need to expose floating IPs and have LANs for my VMs', i do not understand why i get asked 'where to deploy neutron to' - for my idea (naive) it must be on each compute node | 08:21 |
| slaweq | eugenmayer: for neutron You can start with https://docs.openstack.org/neutron/latest/admin/intro-os-networking.html | 08:22 |
| eugenmayer | sure, will read that and ask if anything is unclear - maybe / hopefully more specific then! | 08:22 |
| slaweq | neutron l2 agent (ovs or lb) needs to be on each compute and networker node | 08:22 |
| slaweq | dhcp and l3 agent can be only on networker nodes | 08:23 |
| slaweq | if You want to use dvr with ovs agent, You will need to have l3 agents on all computes as well | 08:23 |
| eugenmayer | dvr / ovs are yet not known to me | 08:23 |
| eugenmayer | maybe part of the docs | 08:24 |
| slaweq | if You want to plug Your vms directly into the provider network (like vlan) You may have only neutron-ovs-agent (or lb-agent) on compute and networker nodes and dhcp-agent on networker nodes | 08:24 |
| slaweq | you need to read about it in docs | 08:24 |
| slaweq | there are also some good talks available on yt for example | 08:24 |
| eugenmayer | that is an open question for me. I have the following situation - each controller and all nodes have a common network (an vswitch i get from my dc, spanning across all barebones). I have 2 of those vswitches plannes: one for cluster/management and one for the VM's lan, so vlan 4000 and 4001 | 08:25 |
| eugenmayer | for proxmox, i just did the following: added the interface for 4000/4001, added a bridge to that interfaces and the i could spawn vms on that bridge, being part of that network - that is something i will need to do with OpenStack too | 08:26 |
| eugenmayer | (beside that, i will have an addition vlan 4003 which offers all the floating ips). That all said, my barebone has 1 nic, multi vlans | 08:27 |
| eugenmayer | but i guess, i read those docs first and ask questions later (to hopefully not waste any of your time) | 08:30 |
| ralonsoh | slaweq, lajoskatona I think the problem is in the OF controller | 09:05 |
| ralonsoh | https://paste.opendev.org/show/810068/ | 09:05 |
| ralonsoh | when the of controller is restarting (because we have changed the configuration) | 09:05 |
| ralonsoh | we can receive a "unknown dpid" message, and the controller will throw a InvalidDatapath exception | 09:06 |
| lajoskatona | ralonsoh: it looks like there's already a msg with some xid | 09:06 |
| ralonsoh | that's ok because we handle it properlu | 09:06 |
| ralonsoh | yes | 09:06 |
| ralonsoh | that's the second case | 09:06 |
| ralonsoh | the of controller does not return anything | 09:06 |
| ralonsoh | and we timeout | 09:06 |
| ralonsoh | so, IMO, we should have a timeout context, smaller than the OF controller timeout | 09:06 |
| ralonsoh | holding the send message stuff | 09:07 |
| ralonsoh | if the message is not received, we can retry again | 09:07 |
| slaweq | of controller timeout is configured somewhere in neutron? | 09:07 |
| ralonsoh | yes | 09:07 |
| ralonsoh | one sec... | 09:07 |
| slaweq | and it's probably 300 seconds or more, right? | 09:07 |
| ralonsoh | yes | 09:08 |
| ralonsoh | 500 secs | 09:08 |
| ralonsoh | 300 secs | 09:08 |
| slaweq | ok | 09:08 |
| slaweq | so we should have this context timeout smaller, like e.g. 60 seconds maybe, right? | 09:08 |
| ralonsoh | so let me propose a patch, that will describe better what I'm saying | 09:08 |
| slaweq | ralonsoh++ | 09:08 |
| opendevreview | Slawek Kaplonski proposed openstack/neutron master: Add functional and fullstack jobs with FIPS enabled https://review.opendev.org/c/openstack/neutron/+/814009 | 09:10 |
| lajoskatona | ralonsoh: thanks | 09:11 |
| opendevreview | Slawek Kaplonski proposed openstack/neutron master: Add functional and fullstack jobs with FIPS enabled https://review.opendev.org/c/openstack/neutron/+/814009 | 09:13 |
| blmt | morning all | 10:11 |
| blmt | I have an OVN issue that's driving me insane: random packet loss on floating IP (using OVN DVR) | 10:12 |
| blmt | that started either out of the blue or as a consequence of a network disruption (not sure things are linked) | 10:14 |
| blmt | anyone has any hint on how to do some OVN specific debug ? | 10:15 |
| opendevreview | Merged openstack/neutron stable/ussuri: Implement namespace creation method https://review.opendev.org/c/openstack/neutron/+/801882 | 10:32 |
| opendevreview | Merged openstack/neutron stable/train: Implement namespace creation method https://review.opendev.org/c/openstack/neutron/+/801988 | 10:32 |
| eugenmayer | blmt, are your barebones hosted on hetzner? | 10:48 |
| blmt | hi eugenmayer, no we have everything in house. | 10:48 |
| eugenmayer | ok, because i had a weired, similar issue on their when using snat outbound rules on the additional (floating) ips | 10:50 |
| eugenmayer | which was heavily impacting traffic/network responses | 10:51 |
| blmt | snat outbound rules from openstack? | 10:55 |
| ralonsoh | slaweq, lajoskatona https://github.com/faucetsdn/ryu/issues/159 | 10:55 |
| ralonsoh | I think the problem is in the os-ken library | 10:55 |
| ralonsoh | I've opened a issue in ryu, just to ask for expert advise on this | 10:56 |
| slaweq | ralonsoh: thx, let's see what ryu devs will say about it :) | 10:57 |
| lajoskatona | ralonsoh: good aproach, let's see if there will be be any action on it | 11:08 |
| *** dkehn_ is now known as dkehn | 11:44 | |
| opendevreview | Balazs Gibizer proposed openstack/neutron-specs master: Move and extend qos-minimum-guaranteed-packet-rate spec https://review.opendev.org/c/openstack/neutron-specs/+/809202 | 12:29 |
| gibi | lajoskatona: ^^ this is ready for yoga now | 12:30 |
| lajoskatona | gibi: thanks | 12:30 |
| opendevreview | Federico Ressi proposed openstack/neutron master: Change tobiko CI job in the periodic queue https://review.opendev.org/c/openstack/neutron/+/813977 | 12:57 |
| opendevreview | Federico Ressi proposed openstack/neutron master: Change tobiko CI job in the periodic queue https://review.opendev.org/c/openstack/neutron/+/813977 | 12:57 |
| opendevreview | Oleg Bondarev proposed openstack/neutron master: Add Local IP Extension and DB https://review.opendev.org/c/openstack/neutron/+/804523 | 13:16 |
| lajoskatona | The room for edge session: https://www.openstack.org/ptg/rooms/ocata | 13:49 |
| opendevreview | Pedro Henrique Pereira Martins proposed openstack/neutron master: Extend database to support portforwardings with port range https://review.opendev.org/c/openstack/neutron/+/798961 | 13:50 |
| lajoskatona | The RBAC session room: https://www.openstack.org/ptg/rooms/newton (from 1500 UTC) | 14:09 |
| *** lbragstad_ is now known as lbragstad | 14:15 | |
| opendevreview | Oleg Bondarev proposed openstack/neutron master: Add Local IP Extension and DB https://review.opendev.org/c/openstack/neutron/+/804523 | 14:18 |
| opendevreview | Oleg Bondarev proposed openstack/neutron master: Add Local IP Extension and DB https://review.opendev.org/c/openstack/neutron/+/804523 | 15:30 |
| opendevreview | Oleg Bondarev proposed openstack/neutron master: Local IP RPC server-agent interface https://review.opendev.org/c/openstack/neutron/+/807116 | 16:02 |
| opendevreview | Pedro Henrique Pereira Martins proposed openstack/neutron master: Extend database to support portforwardings with port range https://review.opendev.org/c/openstack/neutron/+/798961 | 16:37 |
| -opendevstatus- NOTICE: Both Gerrit and Zuul services are being restarted briefly for minor updates, and should return to service momentarily; all previously running builds will be reenqueued once Zuul is fully started again | 17:01 | |
| opendevreview | Elvira García Ruiz proposed openstack/neutron stable/wallaby: [OVN] Change ControllerAgent type dinamically https://review.opendev.org/c/openstack/neutron/+/814654 | 20:02 |
| opendevreview | Merged openstack/neutron stable/victoria: [OVN] Update the DHCP options when the metadata port is modified https://review.opendev.org/c/openstack/neutron/+/813410 | 20:23 |
| opendevreview | Pedro Henrique Pereira Martins proposed openstack/neutron master: Extend database to support portforwardings with port range https://review.opendev.org/c/openstack/neutron/+/798961 | 20:24 |
| opendevreview | Merged openstack/networking-ovn stable/train: [OVN] Tune OVN routers to reduce the mem footprint for ML2/OVN https://review.opendev.org/c/openstack/networking-ovn/+/814423 | 22:26 |
| opendevreview | Merged openstack/neutron-tempest-plugin master: Use an older version of neutron-tempest-plugin for stein jobs https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/813840 | 23:42 |
| opendevreview | Merged openstack/neutron stable/xena: [OVN] Tune OVN routers to reduce the mem footprint for ML2/OVN https://review.opendev.org/c/openstack/neutron/+/814422 | 23:42 |
| opendevreview | Merged openstack/neutron stable/wallaby: [OVN] Tune OVN routers to reduce the mem footprint for ML2/OVN https://review.opendev.org/c/openstack/neutron/+/814421 | 23:42 |
| opendevreview | Merged openstack/neutron stable/victoria: [OVN] Tune OVN routers to reduce the mem footprint for ML2/OVN https://review.opendev.org/c/openstack/neutron/+/814420 | 23:42 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!