Wednesday, 2023-09-13

opendevreviewMerged openstack/neutron master: Fix wrong indentation in release note  https://review.opendev.org/c/openstack/neutron/+/89480801:03
opendevreviewlikui proposed openstack/neutron-fwaas-dashboard master: Use py3 as the default runtime for tox  https://review.opendev.org/c/openstack/neutron-fwaas-dashboard/+/89486102:26
opendevreviewlikui proposed openstack/neutron-fwaas-dashboard master: Add python3.10 support in testing runtime  https://review.opendev.org/c/openstack/neutron-fwaas-dashboard/+/89486202:28
opendevreviewlikui proposed openstack/networking-bgpvpn master: Add python3.10 support in testing runtime  https://review.opendev.org/c/openstack/networking-bgpvpn/+/89486506:21
opendevreviewliuxie proposed openstack/neutron-fwaas master: Support l3 firewall for ovn driver  https://review.opendev.org/c/openstack/neutron-fwaas/+/84575606:40
*** ozzzo1 is now known as ozzzo07:02
opendevreviewliuxie proposed openstack/neutron-fwaas master: Support l3 firewall for ovn driver  https://review.opendev.org/c/openstack/neutron-fwaas/+/84575607:40
opendevreviewLuis Tomas Bolivar proposed openstack/neutron master: Add support for FDB aging  https://review.opendev.org/c/openstack/neutron/+/89333308:04
opendevreviewMerged openstack/ovn-bgp-agent master: Fix spelling errors  https://review.opendev.org/c/openstack/ovn-bgp-agent/+/89333908:18
opendevreviewLuis Tomas Bolivar proposed openstack/neutron master: Add support for FDB aging  https://review.opendev.org/c/openstack/neutron/+/89333308:27
opendevreviewliuxie proposed openstack/neutron-fwaas master: Support l3 firewall for ovn driver  https://review.opendev.org/c/openstack/neutron-fwaas/+/84575608:37
opendevreviewElvira García Ruiz proposed openstack/neutron stable/2023.1: [OVN] Fix rate and burst for stateless security groups  https://review.opendev.org/c/openstack/neutron/+/89346010:24
opendevreviewElvira García Ruiz proposed openstack/neutron stable/zed: [OVN] Fix rate and burst for stateless security groups  https://review.opendev.org/c/openstack/neutron/+/89484610:25
sahido/10:25
sahidWe are suffering a strange behavior with rpc10:26
sahidwe are execeding the default message_size limit of 128mega10:26
sahidany idea of what could be so big?10:27
sahidlooks like it's between ovs agent and neutron server10:27
sahidwe have about 250 segements10:28
ralonsohand how many ports, security groups and SG rules do you have?10:52
ralonsohin any case, the ovs agent rpc messages are batched, if I'm not wrong10:52
opendevreviewBence Romsics proposed openstack/neutron master: contributor docs: Architectural overview for metadata  https://review.opendev.org/c/openstack/neutron/+/89491112:21
opendevreviewBence Romsics proposed openstack/neutron master: contributor docs: Architectural overview for metadata  https://review.opendev.org/c/openstack/neutron/+/89491112:25
sahidall of those resources are passed via rpc message?12:29
sahidI just feel like this looks quite big12:29
opendevreviewBence Romsics proposed openstack/neutron master: contributor docs: Architectural overview for metadata  https://review.opendev.org/c/openstack/neutron/+/89491112:31
sahidwe are about to think increasing the max_message_size12:34
sahidralonsoh: what do you mean by batched, i'm remember of something like that for the dhcp agent12:40
ralonsohsahid, yes, everything is sent via RPC12:52
ralonsohhowever that should not be a problem in the OVS agent because it uses a local cache12:53
ralonsohis it listening to the resource updates12:53
ralonsohthat issue could be present when the agent is restarted, for example12:53
ralonsohhaleyb, hello! I have a question about IPv6+isolated metadata13:06
ralonsohI deployed an environment and I really don't understand how this is actually working13:07
ralonsohlet me explain: in the VM I have a LLA fe80::f816:3eff:fe5f:dffd/6413:07
ralonsohwhen I curl the /128 bit prefix metadata IP, how this is routed? I mean, the /128 traffic should be routed, right?13:08
haleybralonsoh: i'm in a meeting marathon, but will try and answer between them13:08
ralonsohfor example, inside the VM I delete the "ip neigh" entry13:08
ralonsohsure, no problem and thanks!13:08
haleybi think it should just resolve it with an NS13:09
ralonsoh(just to finish) then I curl and I see, inside the DHCP namespace the NS for a9fe:a9fe13:10
ralonsohbut how is that? how can we have a NS from a /128 address?13:10
haleybi don't remember exactly, but does the NS have a prefix length?13:11
ralonsohlet me check13:11
* haleyb hopes he didn't mess that code up13:11
opendevreviewBence Romsics proposed openstack/neutron master: contributor docs: Architectural overview for metadata  https://review.opendev.org/c/openstack/neutron/+/89491113:12
opendevreviewMerged openstack/ovn-octavia-provider master: Cover the use case of a member non existing  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/89383913:28
opendevreviewMerged openstack/neutron master: Prevent internal IP change for floating IP  https://review.opendev.org/c/openstack/neutron/+/88979114:09
opendevreviewMerged openstack/neutron stable/xena: [neutron-api] remove leader_only for sb connection  https://review.opendev.org/c/openstack/neutron/+/89478314:28
opendevreviewFernando Royo proposed openstack/ovn-octavia-provider stable/2023.1: Cover the use case of a member non existing  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/89492514:34
opendevreviewFernando Royo proposed openstack/ovn-octavia-provider stable/zed: Cover the use case of a member non existing  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/89492614:35
opendevreviewFernando Royo proposed openstack/ovn-octavia-provider stable/yoga: Cover the use case of a member non existing  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/89492714:36
opendevreviewFernando Royo proposed openstack/ovn-octavia-provider stable/xena: Cover the use case of a member non existing  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/89492814:38
opendevreviewFernando Royo proposed openstack/ovn-octavia-provider stable/wallaby: Cover the use case of a member non existing  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/89492914:39
opendevreviewFernando Royo proposed openstack/ovn-octavia-provider stable/zed: Cover the use case of a member non existing  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/89492614:42
opendevreviewTerry Wilson proposed openstack/neutron master: Add support for OVN MAC_Binding aging  https://review.opendev.org/c/openstack/neutron/+/89357514:46
opendevreviewLajos Katona proposed openstack/ovsdbapp master: TAAS: Add commands for creating Mirrors  https://review.opendev.org/c/openstack/ovsdbapp/+/89032814:55
opendevreviewDaniel Alvarez proposed openstack/neutron master: [ovn] Add support for IPv6 metadata  https://review.opendev.org/c/openstack/neutron/+/89402615:37
haleybralonsoh: i'm back, and i'll start up an OVS devstack to see how it works15:39
ralonsohhaleyb, I think we found how it is working15:39
ralonsohthe dhcp interface has a LLA address15:40
ralonsohthat is used to route the packets back15:40
ralonsohthat was NOT in the ovn metadata namespace interface15:40
ralonsoh^^^^ this last PS includes it15:40
ralonsohand, btw, it is now using the metadata IP/128 (same as in the OVS case)15:40
haleyback, will take a look. the ipv4 one uses a /32 as well, so i was assuming the /128 was fine15:41
opendevreviewDaniel Alvarez proposed openstack/neutron master: [ovn] Add support for IPv6 metadata  https://review.opendev.org/c/openstack/neutron/+/89402615:58
opendevreviewMerged openstack/neutron stable/wallaby: [OVN] Prevent Trunk creation/deletion with parent port bound  https://review.opendev.org/c/openstack/neutron/+/88760616:13
opendevreviewyatin proposed openstack/neutron stable/2023.1: Switch fullstack/functional fips jobs to 9-stream  https://review.opendev.org/c/openstack/neutron/+/89485716:19
aprats-Hi ! My patch https://review.opendev.org/c/openstack/neutron/+/890459 has finally passed Zuul \o/ What are the next steps ? What should I do to get this patch approved :) 18:18
opendevreviewMiro Tomaska proposed openstack/neutron master: OVN Metadata handle process exceptions  https://review.opendev.org/c/openstack/neutron/+/89098618:32
frickleraprats-: usually you don't need to do anything at this point, just wait for reviews on the patch, this can take a couple of days depending on people's workload. if nothing has happened in say a week, you could try mentioning it here once more, preferrably during the team meeting on tuesdays18:53
opendevreviewElod Illes proposed openstack/neutron-fwaas-dashboard master: DNM: gate health test  https://review.opendev.org/c/openstack/neutron-fwaas-dashboard/+/89497919:21
opendevreviewElod Illes proposed openstack/neutron-vpnaas-dashboard master: DNM: gate health test  https://review.opendev.org/c/openstack/neutron-vpnaas-dashboard/+/89498019:22
opendevreviewElod Illes proposed openstack/neutron-vpnaas master: DNM: gate health test  https://review.opendev.org/c/openstack/neutron-vpnaas/+/89498119:22

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